NTP statistics for iwasno.net

We have started to run the network time protocol daemon ntpd some time ago, here are the daily plots of the statistics. It seems that the time offset stays in the interval [-10 10] ms, but there are some disturbances which are probably due to congestion on the link between iwasno.net and the NTP peer.

Most recent plot

The following plot has been created locally (last night) using a gnuplot with PNG support (hence the nicer text font, I also increased the size to 800x600). Note that delay, jitter and offset values outside [-50 150] ms are not plotted to reduce the overlap between the curves.

Older plots

The following plot shows the frequency offset of the old server (box7842).

There seems to some correlation between frequency error and temperature although it is not as strong as in this example.

Temperature data courtesy of the University of Duisburg-Essen ALBERT-KRATZER-KLIMASTATION (Stadtstation) refers to outside, whereas the machine is in a temperature-controlled data center.

The NTP peer changed 36 days after the beginning of recorded history, this can be clearly seen as a jump in the delay and a reduction in the noise on the time offset, frequency offset curves. This is due to a shorter link between us and the new NTP peer which introduces less disturbance into the time measurements.

The second NTP peer is eu.ntp.your.org (204.9.53.11), the first one is eth0-0.yuffie.projectdream.org (194.88.212.200). On 2006-11-26, ping reported round-trip delays of 4.9/4.9/5.1 ms (eu.ntp.your.org) and 20.3/20.9/21.3 ms, respectively. These values are similar to the delay values seen in the plot above.

Since 2007-01-18, another peer mail01.tjgroup.no (80.239.2.146) is used. On 2007-01-21, ping reported a delay of 29.3/29.9/31.6 ms (min/avg/max). The following table summarises the history:

According to IP2location, the second NTP peer is located in Illinois (US), the first one in Switzerland and the third (used since 2007-01-18) in Norway. The delay to the second peer is too small for that to be correct. See also the traceroute results below.

$ traceroute 204.9.53.11
traceroute to 204.9.53.11 (204.9.53.11), 30 hops max, 38 byte packets
 1  f22-5.elkhouse.de (213.9.78.41)  0.295 ms  0.178 ms  0.119 ms
 2  f2-15.cr1.hkn.net (213.9.99.77)  0.485 ms  0.190 ms  0.219 ms
 3  g3-1.cr3.dui.de.ncore.net (212.46.96.153)  0.391 ms  0.231 ms  0.221 ms
 4  pos2-2.br2.dus.de.ncore.net (212.46.96.34)  1.357 ms  1.310 ms  1.299 ms
 5  g1-1.br1.dus.de.ncore.net (212.46.96.1)  1.324 ms  1.300 ms  1.298 ms
 6  g1-2.br3.dus.de.ncore.net (212.46.96.14)  1.403 ms  1.312 ms  1.308 ms
 7  ge-0.3.0.core1.ams.bb.your.org (195.69.145.49)  132.633 ms  62.675 ms  59.977 ms
 8  eu.ntp.your.org (204.9.53.11)  5.151 ms  4.999 ms  4.784 ms

$ traceroute 194.88.212.200
traceroute to 194.88.212.200 (194.88.212.200), 30 hops max, 38 byte packets
 1  f22-5.elkhouse.de (213.9.78.41)  0.295 ms  0.157 ms  0.120 ms
 2  f2-15.cr1.hkn.net (213.9.99.77)  0.633 ms  0.222 ms  0.182 ms
 3  g3-1.cr3.dui.de.ncore.net (212.46.96.153)  0.390 ms  0.230 ms  0.223 ms
 4  pos2-2.br2.dus.de.ncore.net (212.46.96.34)  1.367 ms  1.306 ms  1.299 ms
 5  g1-1.br1.dus.de.ncore.net (212.46.96.1)  1.367 ms  1.312 ms  1.299 ms
 6  g1-2.br3.dus.de.ncore.net (212.46.96.14)  1.406 ms  1.495 ms  1.548 ms
 7  r1.amsix.init7.net (195.69.144.210)  5.499 ms  4.939 ms  5.350 ms
 8  r5.core.init7.net (82.197.168.100)  19.288 ms  20.107 ms  19.337 ms
 9  r4.core.init7.net (213.144.128.4)  19.878 ms  19.778 ms  20.453 ms
10  eth0-0.yuffie.projectdream.org (194.88.212.200)  21.087 ms  21.517 ms  20.270 ms

$ traceroute 80.239.2.146
traceroute to 80.239.2.146 (80.239.2.146), 30 hops max, 38 byte packets
 1  f22-5.elkhouse.de (213.9.78.41)  0.349 ms  0.217 ms  0.206 ms
 2  f2-15.cr1.hkn.net (213.9.99.77)  0.671 ms  0.313 ms  0.306 ms
 3  g3-1.cr3.dui.de.ncore.net (212.46.96.153)  0.514 ms  0.350 ms  0.340 ms
 4  pos2-2.br2.dus.de.ncore.net (212.46.96.34)  1.492 ms  1.425 ms  1.409 ms
 5  g1-1.br1.dus.de.ncore.net (212.46.96.1)  1.462 ms  1.453 ms  1.424 ms
 6  ddf-b1-link.telia.net (213.248.68.141)  1.808 ms  1.547 ms  1.586 ms
 7  ffm-bb1-link.telia.net (80.91.249.234)  5.494 ms  5.498 ms  5.504 ms
 8  ffm-b1-link.telia.net (213.248.64.138)  5.486 ms  5.409 ms  5.529 ms
 9  tdc-114354-ffm-b1.telia.net (213.248.77.54)  5.678 ms  5.405 ms  5.394 ms
10  pos0-0.2488M.ffm2nxg2.ip.tele.dk (83.88.21.14)  5.732 ms  5.621 ms  5.388 ms
11  pos1-0-0.2488M.albnxg1.ip.tele.dk (83.88.26.154)  20.934 ms  20.608 ms  20.838 ms
12  pos0-0.2488M.oslo1nxg1.ip.tele.dk (83.88.13.90)  28.949 ms  29.214 ms  28.920 ms
13  pos6-0.2488M.prg-p1.osl.no.tdcsong.net (83.88.13.106)  28.965 ms  28.812 ms  28.894 ms
14  pos4-0.2488M.nyd-p2.osl.no.tdcsong.net (80.232.27.250)  28.970 ms  29.327 ms  28.740 ms
15  ge0-1-501.1000M.nyd-pe6.osl.no.tdcsong.net (80.232.27.126)  29.196 ms  28.996 ms  28.850 ms
16  mail01.tjgroup.no (80.239.2.146)  29.993 ms  29.651 ms  29.705 ms

$ traceroute 88.191.17.134
traceroute to 88.191.17.134 (88.191.17.134), 30 hops max, 38 byte packets
 1  f22-5.elkhouse.de (213.9.78.41)  0.483 ms  0.370 ms  0.366 ms
 2  f2-15.cr1.hkn.net (213.9.99.77)  0.451 ms  0.230 ms  0.223 ms
 3  g3-1.cr3.dui.de.ncore.net (212.46.96.153)  0.423 ms  0.274 ms  0.262 ms
 4  p2-2.br2.dus.de.ncore.net (212.46.96.34)  1.465 ms  1.525 ms  1.514 ms
 5  g4-1.br4.dus.de.ncore.net (212.46.96.58)  1.655 ms  1.547 ms  1.513 ms
 6  g3-4.br3.dus.de.ncore.net (212.46.96.49)  1.744 ms  1.553 ms  1.552 ms
 7  amsix-6k-1.routers.proxad.net (195.69.144.251)  4.790 ms  4.959 ms *
 8  londres-6k-1-po100.intf.routers.proxad.net (212.27.56.41)  12.973 ms  13.102 ms *
 9  cbv-6k-2-v828.intf.routers.proxad.net (212.27.51.185)  21.274 ms  20.993 ms  21.073 ms
10  dedibox-2.intf.routers.proxad.net (212.27.50.162)  20.301 ms  20.356 ms *
11  10ge-vl401-49.swr1.bzn.dedibox.fr (88.191.2.10)  20.493 ms  20.550 ms  27.639 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *

back to Roland's start page.