NTPsec

ntp03.maillink.ch

Report generated: Tue Jul 15 10:45:03 2025 UTC
Start Time: Tue Jul 8 10:45:01 2025 UTC
End Time: Tue Jul 15 10:45:01 2025 UTC
Report Period: 7.0 days

Top   Daily Stats   Weekly Stats  

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -123.810 -68.125 -47.065 -1.676 53.427 74.539 129.356 100.492 142.664 30.850 -1.158 µs -4.013 10.21
Local Clock Frequency Offset -4.972 -4.940 -4.690 -3.724 -3.054 -2.977 -2.941 1.636 1.962 0.469 -3.814 ppm -791.5 7500

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 1.542 2.416 3.072 5.317 9.136 12.042 20.955 6.064 9.626 1.962 5.603 µs 13.3 49.31

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 0.128 0.281 0.388 1.401 3.620 4.785 6.721 3.232 4.504 1.047 1.566 ppb 2.822 8.837

The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.

Lower is better. An ideal clock would be a horizontal line at 0ppm.

RMS Frequency Jitter is field 6 in the loopstats log file.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -123.810 -68.125 -47.065 -1.676 53.427 74.539 129.356 100.492 142.664 30.850 -1.158 µs -4.013 10.21

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -4.972 -4.940 -4.690 -3.724 -3.054 -2.977 -2.941 1.636 1.962 0.469 -3.814 ppm -791.5 7500
Temp ZONE0 63.350 64.450 66.650 70.500 74.900 76.000 77.650 8.250 11.550 2.531 70.764 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 5.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.145 9.394 nSat 395 3000
TDOP 0.490 0.540 0.600 0.870 1.240 1.440 2.180 0.640 0.900 0.211 0.891 44.24 189.5

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 195.176.26.206

peer offset 195.176.26.206 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 195.176.26.206 -115.452 -73.710 -46.480 16.197 84.596 119.319 198.326 131.076 193.029 40.813 16.747 µs -1.748 4.976

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2001:638:610:be01::103 (ptbtime3.ptb.de)

peer offset 2001:638:610:be01::103 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:638:610:be01::103 (ptbtime3.ptb.de) -131.990 -71.075 -43.911 23.954 103.931 146.260 225.479 147.842 217.335 45.735 26.638 µs -1.025 3.887

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2001:7c0:2800::3:19

peer offset 2001:7c0:2800::3:19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:7c0:2800::3:19 -2.556 -1.590 -1.538 -1.458 -1.380 -1.345 -1.070 0.158 0.245 0.101 -1.467 ms -3749 5.912e+04

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:4700:f1::1 (time.cloudflare.com)

peer offset 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -617.562 -519.091 -449.940 4.438 487.628 571.183 624.103 937.568 1,090.274 268.927 -67.968 µs -5.453 13.08

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:4700:f1::123 (time.cloudflare.com)

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -582.236 -528.586 -493.424 -123.124 260.036 340.347 389.243 753.460 868.933 266.421 -134.958 µs -7.846 19.71

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl)

peer offset 2a00:d78:0:712:94:198:159:11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 83.418 138.069 175.436 267.752 366.778 404.322 467.916 191.342 266.253 57.485 267.880 µs 60.08 263.8

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a01:3f7:4:51::4 (mmo1-ts.nts.netnod.se)

peer offset 2a01:3f7:4:51::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:3f7:4:51::4 (mmo1-ts.nts.netnod.se) -2.745 -1.773 -1.748 -1.678 -1.600 -1.568 -1.508 0.149 0.205 0.055 -1.678 ms -3.168e+04 1.005e+06

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a02:168:420b:4::7b:12 (ntp02.maillink.ch)

peer offset 2a02:168:420b:4::7b:12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) -206.176 -104.956 -70.590 -1.690 67.914 96.983 157.799 138.504 201.939 42.459 -1.517 µs -4.351 11.76

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a02:168:420b:d::7b:12 (ntp01.maillink.ch)

peer offset 2a02:168:420b:d::7b:12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) -115.505 -62.152 -36.192 13.067 69.430 94.479 135.519 105.622 156.631 32.109 13.832 µs -1.809 5.453

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 85.195.224.28

peer offset 85.195.224.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 85.195.224.28 -1,562.133 -799.815 -340.658 42.038 336.880 586.203 1,050.648 677.538 1,386.018 229.436 26.234 µs -4.139 16.26

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset PPS(0)

peer offset PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset PPS(0) -153.332 -85.096 -63.412 -14.206 48.694 78.496 131.212 112.106 163.592 35.493 -12.839 µs -6.275 16.22

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -600.648 -436.694 -348.387 -208.569 -149.493 -104.889 170.603 198.894 331.805 70.245 -220.992 ms -83.53 406.2

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset SHM(2)

peer offset SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(2) -152.236 -85.923 -64.439 -15.450 47.257 77.290 125.641 111.696 163.213 35.383 -14.082 µs -6.587 17.13

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 195.176.26.206

peer jitter 195.176.26.206 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 195.176.26.206 11.028 17.067 23.444 51.508 244.242 454.331 1,010.860 220.798 437.264 86.024 83.454 µs 3.288 20.39

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:638:610:be01::103 (ptbtime3.ptb.de)

peer jitter 2001:638:610:be01::103 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:638:610:be01::103 (ptbtime3.ptb.de) 9.983 19.819 25.951 59.377 225.875 428.541 693.932 199.924 408.722 75.886 84.421 µs 3.543 18.96

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:7c0:2800::3:19

peer jitter 2001:7c0:2800::3:19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:7c0:2800::3:19 0.000 0.023 0.034 0.145 0.984 1.089 9.414 0.949 1.066 0.458 0.379 ms 7.163 141.8

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2606:4700:f1::1 (time.cloudflare.com)

peer jitter 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 11.816 21.009 27.566 65.330 247.236 410.893 668.559 219.670 389.884 80.406 90.719 µs 3.496 18.25

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2606:4700:f1::123 (time.cloudflare.com)

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 14.298 20.096 26.476 65.071 313.740 583.375 1,749.460 287.264 563.279 125.507 102.867 µs 5.743 64.09

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl)

peer jitter 2a00:d78:0:712:94:198:159:11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.023 0.035 0.061 0.734 6.402 14.665 25.827 6.341 14.630 2.821 1.811 ms 2.6 17.42

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a01:3f7:4:51::4 (mmo1-ts.nts.netnod.se)

peer jitter 2a01:3f7:4:51::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:3f7:4:51::4 (mmo1-ts.nts.netnod.se) 0.008 0.019 0.027 0.060 0.272 0.622 53.248 0.245 0.603 2.030 0.172 ms 22.51 590.6

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a02:168:420b:4::7b:12 (ntp02.maillink.ch)

peer jitter 2a02:168:420b:4::7b:12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) 1.182 3.522 5.633 20.805 45.108 61.861 115.758 39.475 58.339 12.795 22.376 µs 3.81 13.06

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a02:168:420b:d::7b:12 (ntp01.maillink.ch)

peer jitter 2a02:168:420b:d::7b:12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) 0.007 0.014 0.018 0.048 0.306 0.843 8.447 0.288 0.829 0.291 0.102 ms 20.74 589.2

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 85.195.224.28

peer jitter 85.195.224.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 85.195.224.28 10.165 18.310 26.080 75.137 304.096 556.649 1,086.674 278.016 538.339 107.709 111.704 µs 3.118 16.96

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter PPS(0)

peer jitter PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter PPS(0) 0.059 0.640 1.092 2.028 3.718 4.757 18.877 2.626 4.117 0.792 2.123 µs 11.36 47.7

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 1.439 4.707 8.547 30.651 140.616 257.361 607.329 132.069 252.654 50.170 46.530 ms 3.58 23.85

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(2)

peer jitter SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(2) 0.129 0.647 1.163 5.278 15.334 23.458 41.117 14.171 22.811 4.859 6.427 µs 2.967 12.96

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -4.972 -4.940 -4.690 -3.724 -3.054 -2.977 -2.941 1.636 1.962 0.469 -3.814 ppm -791.5 7500
Local Clock Time Offset -123.810 -68.125 -47.065 -1.676 53.427 74.539 129.356 100.492 142.664 30.850 -1.158 µs -4.013 10.21
Local RMS Frequency Jitter 0.128 0.281 0.388 1.401 3.620 4.785 6.721 3.232 4.504 1.047 1.566 ppb 2.822 8.837
Local RMS Time Jitter 1.542 2.416 3.072 5.317 9.136 12.042 20.955 6.064 9.626 1.962 5.603 µs 13.3 49.31
Server Jitter 195.176.26.206 11.028 17.067 23.444 51.508 244.242 454.331 1,010.860 220.798 437.264 86.024 83.454 µs 3.288 20.39
Server Jitter 2001:638:610:be01::103 (ptbtime3.ptb.de) 9.983 19.819 25.951 59.377 225.875 428.541 693.932 199.924 408.722 75.886 84.421 µs 3.543 18.96
Server Jitter 2001:7c0:2800::3:19 0.000 0.023 0.034 0.145 0.984 1.089 9.414 0.949 1.066 0.458 0.379 ms 7.163 141.8
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 11.816 21.009 27.566 65.330 247.236 410.893 668.559 219.670 389.884 80.406 90.719 µs 3.496 18.25
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 14.298 20.096 26.476 65.071 313.740 583.375 1,749.460 287.264 563.279 125.507 102.867 µs 5.743 64.09
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.023 0.035 0.061 0.734 6.402 14.665 25.827 6.341 14.630 2.821 1.811 ms 2.6 17.42
Server Jitter 2a01:3f7:4:51::4 (mmo1-ts.nts.netnod.se) 0.008 0.019 0.027 0.060 0.272 0.622 53.248 0.245 0.603 2.030 0.172 ms 22.51 590.6
Server Jitter 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) 1.182 3.522 5.633 20.805 45.108 61.861 115.758 39.475 58.339 12.795 22.376 µs 3.81 13.06
Server Jitter 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) 0.007 0.014 0.018 0.048 0.306 0.843 8.447 0.288 0.829 0.291 0.102 ms 20.74 589.2
Server Jitter 85.195.224.28 10.165 18.310 26.080 75.137 304.096 556.649 1,086.674 278.016 538.339 107.709 111.704 µs 3.118 16.96
Server Jitter PPS(0) 0.059 0.640 1.092 2.028 3.718 4.757 18.877 2.626 4.117 0.792 2.123 µs 11.36 47.7
Server Jitter SHM(0) 1.439 4.707 8.547 30.651 140.616 257.361 607.329 132.069 252.654 50.170 46.530 ms 3.58 23.85
Server Jitter SHM(2) 0.129 0.647 1.163 5.278 15.334 23.458 41.117 14.171 22.811 4.859 6.427 µs 2.967 12.96
Server Offset 195.176.26.206 -115.452 -73.710 -46.480 16.197 84.596 119.319 198.326 131.076 193.029 40.813 16.747 µs -1.748 4.976
Server Offset 2001:638:610:be01::103 (ptbtime3.ptb.de) -131.990 -71.075 -43.911 23.954 103.931 146.260 225.479 147.842 217.335 45.735 26.638 µs -1.025 3.887
Server Offset 2001:7c0:2800::3:19 -2.556 -1.590 -1.538 -1.458 -1.380 -1.345 -1.070 0.158 0.245 0.101 -1.467 ms -3749 5.912e+04
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -617.562 -519.091 -449.940 4.438 487.628 571.183 624.103 937.568 1,090.274 268.927 -67.968 µs -5.453 13.08
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -582.236 -528.586 -493.424 -123.124 260.036 340.347 389.243 753.460 868.933 266.421 -134.958 µs -7.846 19.71
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 83.418 138.069 175.436 267.752 366.778 404.322 467.916 191.342 266.253 57.485 267.880 µs 60.08 263.8
Server Offset 2a01:3f7:4:51::4 (mmo1-ts.nts.netnod.se) -2.745 -1.773 -1.748 -1.678 -1.600 -1.568 -1.508 0.149 0.205 0.055 -1.678 ms -3.168e+04 1.005e+06
Server Offset 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) -206.176 -104.956 -70.590 -1.690 67.914 96.983 157.799 138.504 201.939 42.459 -1.517 µs -4.351 11.76
Server Offset 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) -115.505 -62.152 -36.192 13.067 69.430 94.479 135.519 105.622 156.631 32.109 13.832 µs -1.809 5.453
Server Offset 85.195.224.28 -1,562.133 -799.815 -340.658 42.038 336.880 586.203 1,050.648 677.538 1,386.018 229.436 26.234 µs -4.139 16.26
Server Offset PPS(0) -153.332 -85.096 -63.412 -14.206 48.694 78.496 131.212 112.106 163.592 35.493 -12.839 µs -6.275 16.22
Server Offset SHM(0) -600.648 -436.694 -348.387 -208.569 -149.493 -104.889 170.603 198.894 331.805 70.245 -220.992 ms -83.53 406.2
Server Offset SHM(2) -152.236 -85.923 -64.439 -15.450 47.257 77.290 125.641 111.696 163.213 35.383 -14.082 µs -6.587 17.13
TDOP 0.490 0.540 0.600 0.870 1.240 1.440 2.180 0.640 0.900 0.211 0.891 44.24 189.5
Temp ZONE0 63.350 64.450 66.650 70.500 74.900 76.000 77.650 8.250 11.550 2.531 70.764 °C
nSats 5.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.145 9.394 nSat 395 3000
Summary as CSV file


Glossary:

frequency offset:
The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
jitter, dispersion:
The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Server Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of kurtosis. A normal distribution has a kurtosis of three. NIST describes a kurtosis over three as "heavy tailed" and one under three as "light tailed".
ms, millisecond:
One thousandth of a second = 0.001 seconds, 1e-3 seconds
mu, mean:
The arithmetic mean: the sum of all the values divided by the number of values. The formula for mu is: "mu = (∑xi) / N". Where xi denotes the data points and N is the number of data points.
ns, nanosecond:
One billionth of a second, also one thousandth of a microsecond, 0.000000001 seconds and 1e-9 seconds.
percentile:
The value below which a given percentage of values fall.
ppb, parts per billion:
Ratio between two values. These following are all the same: 1 ppb, one in one billion, 1/1,000,000,000, 0.000,000,001, 1e-9 and 0.000,000,1%
ppm, parts per million:
Ratio between two values. These following are all the same: 1 ppm, one in one million, 1/1,000,000, 0.000,001, and 0.000,1%
‰, parts per thousand:
Ratio between two values. These following are all the same: 1 ‰. one in one thousand, 1/1,000, 0.001, and 0.1%
refclock:
Reference clock, a local GPS module or other local source of time.
remote clock:
Any clock reached over the network, LAN or WAN. Also called a peer or server.
time offset:
The difference between the ntpd calculated time and the local system clock's time. Also called phase offset.
σ, sigma:
Sigma denotes the standard deviation (SD) and is centered on the arithmetic mean of the data set. The SD is simply the square root of the variance of the data set. Two sigma is simply twice the standard deviation. Three sigma is three times sigma. Smaller is better.
The formula for sigma is: "σ = √[ ∑(xi-mu)^2 / N ]". Where xi denotes the data points and N is the number of data points.
skewness, Skew:
The skewness of a random variable X is the third standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
upstream clock:
Any server or reference clock used as a source of time.
µs, us, microsecond:
One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.



This page autogenerated by ntpviz, part of the NTPsec project
html 5    Valid CSS!