NTPsec

ntp03.maillink.ch

Report generated: Fri Apr 4 02:53:00 2025 UTC
Start Time: Thu Apr 3 02:53:00 2025 UTC
End Time: Fri Apr 4 02:53:00 2025 UTC
Report Period: 1.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 -43.775 -35.344 -23.143 0.541 22.890 34.146 46.837 46.033 69.490 13.556 0.263 µs -3.95 10.46
Local Clock Frequency Offset -2.763 -2.760 -2.749 -2.713 -2.670 -2.662 -2.658 0.079 0.098 0.022 -2.716 ppm -1.97e+06 2.47e+08

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 2.181 3.059 4.189 8.648 15.639 17.939 20.733 11.450 14.880 3.541 9.099 µs 9.094 26.82

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.206 0.254 0.354 0.735 1.275 1.523 1.894 0.921 1.269 0.282 0.778 ppb 11.27 35.36

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 -43.775 -35.344 -23.143 0.541 22.890 34.146 46.837 46.033 69.490 13.556 0.263 µs -3.95 10.46

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 -2.763 -2.760 -2.749 -2.713 -2.670 -2.662 -2.658 0.079 0.098 0.022 -2.716 ppm -1.97e+06 2.47e+08
Temp ZONE0 51.800 52.350 52.900 54.000 55.100 56.200 56.200 2.200 3.850 0.763 54.067 °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 7.000 7.000 7.000 9.000 11.000 11.000 12.000 4.000 4.000 1.012 9.251 nSat 563.8 4786
TDOP 0.540 0.550 0.600 0.860 1.300 1.500 1.760 0.700 0.950 0.210 0.885 44.05 186.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 -110.000 -98.666 -85.472 -48.061 -14.603 6.953 15.378 70.869 105.619 22.186 -49.128 µs -42.8 171

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) -2.807 -2.797 -2.770 -2.722 -2.664 -2.640 -2.623 0.106 0.157 0.032 -2.721 ms -6.581e+05 5.726e+07

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) 0.687 0.700 0.738 0.849 1.248 1.272 1.279 0.510 0.571 0.194 0.936 ms 68.17 314.4

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) 0.538 0.541 0.641 0.917 1.170 1.220 1.259 0.529 0.679 0.148 0.930 ms 163.5 948

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) -254.863 -222.189 -189.561 -112.044 -28.507 66.151 122.891 161.054 288.340 54.266 -108.299 µs -35.12 130.4

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:2:44::8 (sth1-ts.nts.netnod.se)

peer offset 2a01:3f7:2:44::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 4.301 4.309 4.323 4.364 4.404 4.432 4.437 0.082 0.123 0.024 4.363 ms 5.848e+06 1.054e+09

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) -53.493 -43.489 -34.856 4.055 45.830 65.261 68.120 80.686 108.750 25.040 5.487 µs -2.651 6.01

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) -53.239 -47.109 -21.131 12.376 49.066 76.596 83.480 70.197 123.705 21.944 12.455 µs -1.279 4.647

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 -735.912 -288.644 -103.179 60.914 147.642 189.906 308.523 250.821 478.550 97.998 44.880 µs -5.242 33.67

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) -55.665 -37.779 -29.032 -0.485 17.956 25.054 32.567 46.988 62.833 14.430 -1.928 µs -5.353 14.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 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) -578.451 -525.116 -481.945 -375.810 -329.384 -311.284 -21.133 152.561 213.832 46.106 -384.519 ms -843.1 8156

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) -52.622 -38.518 -29.699 -1.486 16.646 23.677 27.556 46.345 62.195 14.293 -2.813 µs -5.796 15.78

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.006 0.013 0.019 0.044 0.259 1.028 1.247 0.240 1.015 0.146 0.089 ms 3.917 26.84

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) 15.643 16.933 26.829 60.724 269.845 525.637 565.305 243.016 508.704 88.594 94.054 µs 2.742 11.43

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) 15.054 21.844 26.421 63.748 234.850 264.037 315.967 208.429 242.193 63.461 88.008 µs 2.706 7.72

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) 15.576 23.060 27.631 58.495 492.437 680.639 908.168 464.806 657.579 141.036 113.442 µs 2.252 9.748

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.037 0.076 0.132 1.941 5.782 8.288 16.800 5.650 8.212 1.746 2.161 ms 3.62 23.45

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:2:44::8 (sth1-ts.nts.netnod.se)

peer jitter 2a01:3f7:2:44::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 10.583 21.250 28.236 68.509 304.012 898.457 925.720 275.776 877.207 127.707 113.500 µs 3.823 23.05

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) 3.201 4.942 6.457 19.079 44.453 65.549 83.438 37.996 60.607 12.401 21.904 µs 4.266 15.26

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.010 0.013 0.017 0.047 0.531 2.161 2.171 0.514 2.148 0.276 0.121 ms 3.457 24.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 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 16.510 18.425 23.900 78.500 267.764 429.964 509.106 243.864 411.539 83.134 102.496 µs 2.48 8.803

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.135 0.538 0.948 1.925 3.448 4.837 20.152 2.500 4.299 0.816 2.019 µs 9.04 37.5

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) 2.070 4.432 6.380 25.727 92.288 146.968 476.245 85.908 142.535 33.935 34.773 ms 4.311 40.53

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.329 0.739 1.363 6.268 18.117 25.822 33.231 16.754 25.083 5.428 7.577 µs 2.483 7.722

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 -2.763 -2.760 -2.749 -2.713 -2.670 -2.662 -2.658 0.079 0.098 0.022 -2.716 ppm -1.97e+06 2.47e+08
Local Clock Time Offset -43.775 -35.344 -23.143 0.541 22.890 34.146 46.837 46.033 69.490 13.556 0.263 µs -3.95 10.46
Local RMS Frequency Jitter 0.206 0.254 0.354 0.735 1.275 1.523 1.894 0.921 1.269 0.282 0.778 ppb 11.27 35.36
Local RMS Time Jitter 2.181 3.059 4.189 8.648 15.639 17.939 20.733 11.450 14.880 3.541 9.099 µs 9.094 26.82
Server Jitter 195.176.26.206 0.006 0.013 0.019 0.044 0.259 1.028 1.247 0.240 1.015 0.146 0.089 ms 3.917 26.84
Server Jitter 2001:638:610:be01::103 (ptbtime3.ptb.de) 15.643 16.933 26.829 60.724 269.845 525.637 565.305 243.016 508.704 88.594 94.054 µs 2.742 11.43
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 15.054 21.844 26.421 63.748 234.850 264.037 315.967 208.429 242.193 63.461 88.008 µs 2.706 7.72
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 15.576 23.060 27.631 58.495 492.437 680.639 908.168 464.806 657.579 141.036 113.442 µs 2.252 9.748
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.037 0.076 0.132 1.941 5.782 8.288 16.800 5.650 8.212 1.746 2.161 ms 3.62 23.45
Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 10.583 21.250 28.236 68.509 304.012 898.457 925.720 275.776 877.207 127.707 113.500 µs 3.823 23.05
Server Jitter 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) 3.201 4.942 6.457 19.079 44.453 65.549 83.438 37.996 60.607 12.401 21.904 µs 4.266 15.26
Server Jitter 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) 0.010 0.013 0.017 0.047 0.531 2.161 2.171 0.514 2.148 0.276 0.121 ms 3.457 24.7
Server Jitter 85.195.224.28 16.510 18.425 23.900 78.500 267.764 429.964 509.106 243.864 411.539 83.134 102.496 µs 2.48 8.803
Server Jitter PPS(0) 0.135 0.538 0.948 1.925 3.448 4.837 20.152 2.500 4.299 0.816 2.019 µs 9.04 37.5
Server Jitter SHM(0) 2.070 4.432 6.380 25.727 92.288 146.968 476.245 85.908 142.535 33.935 34.773 ms 4.311 40.53
Server Jitter SHM(2) 0.329 0.739 1.363 6.268 18.117 25.822 33.231 16.754 25.083 5.428 7.577 µs 2.483 7.722
Server Offset 195.176.26.206 -110.000 -98.666 -85.472 -48.061 -14.603 6.953 15.378 70.869 105.619 22.186 -49.128 µs -42.8 171
Server Offset 2001:638:610:be01::103 (ptbtime3.ptb.de) -2.807 -2.797 -2.770 -2.722 -2.664 -2.640 -2.623 0.106 0.157 0.032 -2.721 ms -6.581e+05 5.726e+07
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 0.687 0.700 0.738 0.849 1.248 1.272 1.279 0.510 0.571 0.194 0.936 ms 68.17 314.4
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 0.538 0.541 0.641 0.917 1.170 1.220 1.259 0.529 0.679 0.148 0.930 ms 163.5 948
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) -254.863 -222.189 -189.561 -112.044 -28.507 66.151 122.891 161.054 288.340 54.266 -108.299 µs -35.12 130.4
Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 4.301 4.309 4.323 4.364 4.404 4.432 4.437 0.082 0.123 0.024 4.363 ms 5.848e+06 1.054e+09
Server Offset 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) -53.493 -43.489 -34.856 4.055 45.830 65.261 68.120 80.686 108.750 25.040 5.487 µs -2.651 6.01
Server Offset 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) -53.239 -47.109 -21.131 12.376 49.066 76.596 83.480 70.197 123.705 21.944 12.455 µs -1.279 4.647
Server Offset 85.195.224.28 -735.912 -288.644 -103.179 60.914 147.642 189.906 308.523 250.821 478.550 97.998 44.880 µs -5.242 33.67
Server Offset PPS(0) -55.665 -37.779 -29.032 -0.485 17.956 25.054 32.567 46.988 62.833 14.430 -1.928 µs -5.353 14.41
Server Offset SHM(0) -578.451 -525.116 -481.945 -375.810 -329.384 -311.284 -21.133 152.561 213.832 46.106 -384.519 ms -843.1 8156
Server Offset SHM(2) -52.622 -38.518 -29.699 -1.486 16.646 23.677 27.556 46.345 62.195 14.293 -2.813 µs -5.796 15.78
TDOP 0.540 0.550 0.600 0.860 1.300 1.500 1.760 0.700 0.950 0.210 0.885 44.05 186.5
Temp ZONE0 51.800 52.350 52.900 54.000 55.100 56.200 56.200 2.200 3.850 0.763 54.067 °C
nSats 7.000 7.000 7.000 9.000 11.000 11.000 12.000 4.000 4.000 1.012 9.251 nSat 563.8 4786
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!