NTPsec

ntp03.maillink.ch

Report generated: Wed Jul 9 10:45:03 2025 UTC
Start Time: Wed Jul 2 10:45:01 2025 UTC
End Time: Wed Jul 9 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 -209.035 -96.352 -71.091 -0.136 83.962 123.518 516.019 155.053 219.870 47.461 3.032 µs -3.342 9.606
Local Clock Frequency Offset -6.758 -6.550 -5.765 -4.358 -3.061 -2.977 -2.941 2.704 3.573 0.848 -4.406 ppm -256.5 1712

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.769 2.401 2.906 4.894 8.905 12.277 264.383 5.999 9.876 7.855 5.632 µs 20.7 524.7

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.218 0.327 0.426 1.983 5.651 7.816 11.137 5.225 7.489 1.706 2.350 ppb 2.306 6.929

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 -209.035 -96.352 -71.091 -0.136 83.962 123.518 516.019 155.053 219.870 47.461 3.032 µs -3.342 9.606

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 -6.758 -6.550 -5.765 -4.358 -3.061 -2.977 -2.941 2.704 3.573 0.848 -4.406 ppm -256.5 1712
Temp ZONE0 63.350 64.450 66.650 72.700 78.200 79.850 82.050 11.550 15.400 3.496 72.682 °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 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.105 9.396 nSat 445 3510
TDOP 0.520 0.540 0.600 0.870 1.220 1.430 2.150 0.620 0.890 0.205 0.890 48.58 211.6

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 -196.426 -103.446 -75.181 16.200 121.251 166.657 221.428 196.432 270.103 60.070 19.541 µs -2.146 5.437

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) -0.201 -0.100 -0.070 0.028 0.237 3.905 4.005 0.307 4.005 0.834 0.216 ms 1.491 9.489

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 (time2.uni-konstanz.de)

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 (time2.uni-konstanz.de) -5.436 -5.348 -5.145 -1.458 -1.346 -1.273 -0.494 3.799 4.075 0.848 -1.655 ms -38.57 192.5

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) -1.076 -0.685 -0.499 -0.085 0.887 1.208 1.294 1.386 1.893 0.401 -0.019 ms -3.231 7.565

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) -557.366 -493.571 -431.898 -73.280 171.194 233.921 278.302 603.092 727.492 201.886 -122.628 µs -9.167 25.21

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) -0.054 0.093 0.143 0.260 0.463 3.781 3.871 0.321 3.688 0.747 0.425 ms 2.778 12.41

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) -1.874 -1.825 -1.782 -1.682 -1.571 -1.533 -1.468 0.211 0.292 0.064 -1.681 ms -2.079e+04 5.733e+05

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) -217.381 -123.106 -71.413 4.510 99.205 255.383 413.875 170.618 378.489 61.116 8.414 µs -1.864 9.964

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) -183.396 -74.374 -47.460 13.730 86.882 124.826 186.935 134.342 199.200 40.972 15.703 µs -1.873 6.1

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.882 -1.803 -1.016 0.107 3.144 3.908 4.184 4.160 5.711 1.045 0.263 ms -0.9518 5.613

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) -232.845 -123.665 -94.931 -12.697 86.448 133.463 178.613 181.379 257.128 55.874 -9.180 µs -4.827 11.89

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 -453.420 -358.251 -207.491 -149.690 93.441 169.726 208.561 546.861 75.920 -222.220 ms -72.38 340.5

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) -230.544 -124.723 -95.922 -13.867 84.741 131.715 172.780 180.663 256.438 55.746 -10.449 µs -4.989 12.32

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 0.011 0.016 0.022 0.048 0.253 0.457 5.299 0.231 0.441 0.223 0.086 ms 16.65 360.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 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) 13.603 19.279 25.913 58.191 237.561 461.990 3,806.442 211.648 442.711 193.956 94.764 µs 12.09 205.9

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 (time2.uni-konstanz.de)

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 (time2.uni-konstanz.de) 0.029 0.063 0.516 0.797 1.025 1.129 4.071 0.509 1.066 0.238 0.787 ms 24.07 175.3

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.439 21.144 27.561 65.000 288.157 488.257 3,111.719 260.596 467.113 122.656 100.307 µs 11.6 267.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 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) 12.386 19.102 24.983 62.685 220.749 352.079 425.698 195.766 332.977 62.339 81.566 µs 3.253 12.97

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.021 0.046 0.071 1.447 7.783 15.411 87.873 7.713 15.365 3.593 2.236 ms 7.745 158.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 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.010 0.018 0.027 0.062 0.309 0.699 53.248 0.282 0.681 2.029 0.177 ms 22.53 591.4

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.646 3.475 5.627 20.991 44.267 65.122 151.065 38.640 61.647 13.506 22.514 µs 4.526 24.62

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) 6.745 12.218 17.335 41.296 215.869 462.345 722.933 198.534 450.127 82.311 70.571 µs 3.165 18.28

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.376 18.184 26.007 72.163 259.390 517.359 3,644.719 233.383 499.175 147.701 106.515 µs 11.6 227.3

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.041 0.662 1.097 2.036 3.747 4.766 18.681 2.650 4.104 0.806 2.135 µs 11.31 54.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 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.463 4.915 8.536 31.387 145.870 326.765 546.548 137.334 321.851 55.546 49.645 ms 3.195 19.24

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.614 1.207 5.408 17.127 29.337 99.948 15.920 28.723 5.984 6.864 µs 3.713 27.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -6.758 -6.550 -5.765 -4.358 -3.061 -2.977 -2.941 2.704 3.573 0.848 -4.406 ppm -256.5 1712
Local Clock Time Offset -209.035 -96.352 -71.091 -0.136 83.962 123.518 516.019 155.053 219.870 47.461 3.032 µs -3.342 9.606
Local RMS Frequency Jitter 0.218 0.327 0.426 1.983 5.651 7.816 11.137 5.225 7.489 1.706 2.350 ppb 2.306 6.929
Local RMS Time Jitter 1.769 2.401 2.906 4.894 8.905 12.277 264.383 5.999 9.876 7.855 5.632 µs 20.7 524.7
Server Jitter 195.176.26.206 0.011 0.016 0.022 0.048 0.253 0.457 5.299 0.231 0.441 0.223 0.086 ms 16.65 360.8
Server Jitter 2001:638:610:be01::103 (ptbtime3.ptb.de) 13.603 19.279 25.913 58.191 237.561 461.990 3,806.442 211.648 442.711 193.956 94.764 µs 12.09 205.9
Server Jitter 2001:7c0:2800::3:19 (time2.uni-konstanz.de) 0.029 0.063 0.516 0.797 1.025 1.129 4.071 0.509 1.066 0.238 0.787 ms 24.07 175.3
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 11.439 21.144 27.561 65.000 288.157 488.257 3,111.719 260.596 467.113 122.656 100.307 µs 11.6 267.7
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 12.386 19.102 24.983 62.685 220.749 352.079 425.698 195.766 332.977 62.339 81.566 µs 3.253 12.97
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.021 0.046 0.071 1.447 7.783 15.411 87.873 7.713 15.365 3.593 2.236 ms 7.745 158.6
Server Jitter 2a01:3f7:4:51::4 (mmo1-ts.nts.netnod.se) 0.010 0.018 0.027 0.062 0.309 0.699 53.248 0.282 0.681 2.029 0.177 ms 22.53 591.4
Server Jitter 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) 1.646 3.475 5.627 20.991 44.267 65.122 151.065 38.640 61.647 13.506 22.514 µs 4.526 24.62
Server Jitter 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) 6.745 12.218 17.335 41.296 215.869 462.345 722.933 198.534 450.127 82.311 70.571 µs 3.165 18.28
Server Jitter 85.195.224.28 10.376 18.184 26.007 72.163 259.390 517.359 3,644.719 233.383 499.175 147.701 106.515 µs 11.6 227.3
Server Jitter PPS(0) 0.041 0.662 1.097 2.036 3.747 4.766 18.681 2.650 4.104 0.806 2.135 µs 11.31 54.2
Server Jitter SHM(0) 1.463 4.915 8.536 31.387 145.870 326.765 546.548 137.334 321.851 55.546 49.645 ms 3.195 19.24
Server Jitter SHM(2) 0.129 0.614 1.207 5.408 17.127 29.337 99.948 15.920 28.723 5.984 6.864 µs 3.713 27.39
Server Offset 195.176.26.206 -196.426 -103.446 -75.181 16.200 121.251 166.657 221.428 196.432 270.103 60.070 19.541 µs -2.146 5.437
Server Offset 2001:638:610:be01::103 (ptbtime3.ptb.de) -0.201 -0.100 -0.070 0.028 0.237 3.905 4.005 0.307 4.005 0.834 0.216 ms 1.491 9.489
Server Offset 2001:7c0:2800::3:19 (time2.uni-konstanz.de) -5.436 -5.348 -5.145 -1.458 -1.346 -1.273 -0.494 3.799 4.075 0.848 -1.655 ms -38.57 192.5
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1.076 -0.685 -0.499 -0.085 0.887 1.208 1.294 1.386 1.893 0.401 -0.019 ms -3.231 7.565
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -557.366 -493.571 -431.898 -73.280 171.194 233.921 278.302 603.092 727.492 201.886 -122.628 µs -9.167 25.21
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) -0.054 0.093 0.143 0.260 0.463 3.781 3.871 0.321 3.688 0.747 0.425 ms 2.778 12.41
Server Offset 2a01:3f7:4:51::4 (mmo1-ts.nts.netnod.se) -1.874 -1.825 -1.782 -1.682 -1.571 -1.533 -1.468 0.211 0.292 0.064 -1.681 ms -2.079e+04 5.733e+05
Server Offset 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) -217.381 -123.106 -71.413 4.510 99.205 255.383 413.875 170.618 378.489 61.116 8.414 µs -1.864 9.964
Server Offset 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) -183.396 -74.374 -47.460 13.730 86.882 124.826 186.935 134.342 199.200 40.972 15.703 µs -1.873 6.1
Server Offset 85.195.224.28 -1.882 -1.803 -1.016 0.107 3.144 3.908 4.184 4.160 5.711 1.045 0.263 ms -0.9518 5.613
Server Offset PPS(0) -232.845 -123.665 -94.931 -12.697 86.448 133.463 178.613 181.379 257.128 55.874 -9.180 µs -4.827 11.89
Server Offset SHM(0) -600.648 -453.420 -358.251 -207.491 -149.690 93.441 169.726 208.561 546.861 75.920 -222.220 ms -72.38 340.5
Server Offset SHM(2) -230.544 -124.723 -95.922 -13.867 84.741 131.715 172.780 180.663 256.438 55.746 -10.449 µs -4.989 12.32
TDOP 0.520 0.540 0.600 0.870 1.220 1.430 2.150 0.620 0.890 0.205 0.890 48.58 211.6
Temp ZONE0 63.350 64.450 66.650 72.700 78.200 79.850 82.050 11.550 15.400 3.496 72.682 °C
nSats 5.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.105 9.396 nSat 445 3510
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!