NTPsec

ntp03.maillink.ch

Report generated: Sat Apr 26 03:53:01 2025 UTC
Start Time: Fri Apr 25 03:53:01 2025 UTC
End Time: Sat Apr 26 03:53:01 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 -40.369 -26.421 -19.524 -0.750 22.952 30.934 61.128 42.476 57.355 12.895 0.135 µs -3.588 8.88
Local Clock Frequency Offset -2.583 -2.580 -2.578 -2.572 -2.564 -2.562 -2.560 0.0133 0.0174 0.0040 -2.572 ppm -2.624e+08 1.68e+11

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 3.417 4.098 4.841 8.892 18.502 23.184 29.455 13.661 19.086 4.273 9.924 µs 7.474 24.35

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.226 0.312 0.381 0.706 1.219 1.567 2.129 0.838 1.255 0.267 0.741 ppb 11.93 41.24

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 -40.369 -26.421 -19.524 -0.750 22.952 30.934 61.128 42.476 57.355 12.895 0.135 µs -3.588 8.88

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.583 -2.580 -2.578 -2.572 -2.564 -2.562 -2.560 0.0133 0.0174 0.0040 -2.572 ppm -2.624e+08 1.68e+11
Temp ZONE0 55.100 55.650 56.750 57.850 59.500 60.050 61.150 2.750 4.400 0.999 58.083 °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 6.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.043 9.219 nSat 505.2 4143
TDOP 0.510 0.520 0.590 0.870 1.210 1.340 2.710 0.620 0.820 0.222 0.883 37.82 177.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 -120.823 -104.698 -84.874 -48.254 -2.463 6.246 37.748 82.411 110.944 24.162 -46.174 µs -33.25 124

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.784 -2.777 -2.760 -2.713 -2.666 -2.622 -2.608 0.094 0.155 0.029 -2.713 ms -8.219e+05 7.701e+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 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) -2.655 -2.550 -1.640 -1.572 -1.500 -1.451 -1.137 0.140 1.099 0.132 -1.583 ms -2232 2.977e+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) 667.815 667.815 676.306 774.327 845.678 874.231 874.231 169.372 206.416 47.763 769.600 µs 3497 5.352e+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::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) 586.795 604.914 643.959 732.917 862.782 892.120 901.427 218.823 287.206 59.102 739.890 µs 1563 1.842e+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 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) -204.543 -195.430 -161.860 -80.553 -2.281 27.148 46.045 159.579 222.578 46.152 -80.983 µs -29.27 107.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 2a01:3f7:6:51::4 (lul1-ts.nts.netnod.se)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:3f7:6:51::4 (lul1-ts.nts.netnod.se) 3.125 3.152 3.194 3.768 3.829 3.842 3.850 0.635 0.690 0.215 3.681 ms 4242 6.911e+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 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) -83.033 -60.746 -37.956 -0.564 47.125 63.312 72.863 85.081 124.058 25.761 1.181 µs -3.621 8.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) -54.715 -45.562 -25.018 11.402 53.104 75.188 91.428 78.122 120.750 24.118 12.391 µs -1.28 4.386

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 -311.753 -286.948 -198.223 59.458 143.820 167.141 191.718 342.043 454.089 99.555 30.136 µs -3.876 12.03

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) -47.940 -32.722 -26.070 0.481 18.912 26.473 36.601 44.982 59.195 13.483 -1.386 µs -5.036 13.29

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) -440.376 -369.277 -321.958 -207.282 -153.573 138.845 165.379 168.385 508.122 72.154 -209.563 ms -69.1 304.7

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) -45.645 -33.159 -27.056 -0.358 17.650 24.868 30.446 44.706 58.027 13.382 -2.317 µs -5.532 14.83

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 21.225 22.186 28.582 87.120 366.737 498.616 699.441 338.155 476.430 109.440 123.568 µs 2.478 9.642

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) 11.124 14.147 24.901 63.081 281.492 432.040 477.555 256.591 417.893 83.150 96.985 µs 2.479 8.813

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.044 0.363 0.504 0.807 1.540 1.697 1.865 1.036 1.334 0.276 0.843 ms 16.09 59.02

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.619 15.619 21.238 75.308 795.065 940.501 940.501 773.827 924.882 217.681 163.774 µs 1.742 6.356

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.460 17.653 24.797 76.716 325.906 444.265 688.236 301.109 426.612 102.670 118.533 µs 2.342 9.018

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.039 0.052 0.107 1.089 5.100 11.644 18.849 4.993 11.591 2.121 1.740 ms 3.136 22.1

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:6:51::4 (lul1-ts.nts.netnod.se)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:3f7:6:51::4 (lul1-ts.nts.netnod.se) 0.013 0.016 0.026 0.086 0.689 2.778 4.348 0.663 2.763 0.455 0.225 ms 3.729 27.63

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.298 4.475 7.284 20.949 48.140 63.050 68.701 40.856 58.575 12.571 24.069 µs 4.371 12.29

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) 8.131 16.581 20.281 65.668 252.386 431.368 734.079 232.105 414.787 95.479 96.897 µs 2.767 14.22

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 11.669 15.584 25.995 87.306 267.966 414.748 649.836 241.971 399.164 89.830 113.250 µs 2.605 10.52

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.066 0.307 0.866 1.879 3.275 4.791 16.895 2.409 4.484 0.815 1.942 µs 8.206 34.34

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) 3.006 4.481 8.296 31.454 174.210 388.421 526.967 165.914 383.940 70.533 58.831 ms 2.405 11.77

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.754 1.235 2.046 6.821 19.254 24.091 36.793 17.208 22.856 5.407 8.193 µs 2.974 9.282

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.583 -2.580 -2.578 -2.572 -2.564 -2.562 -2.560 0.0133 0.0174 0.0040 -2.572 ppm -2.624e+08 1.68e+11
Local Clock Time Offset -40.369 -26.421 -19.524 -0.750 22.952 30.934 61.128 42.476 57.355 12.895 0.135 µs -3.588 8.88
Local RMS Frequency Jitter 0.226 0.312 0.381 0.706 1.219 1.567 2.129 0.838 1.255 0.267 0.741 ppb 11.93 41.24
Local RMS Time Jitter 3.417 4.098 4.841 8.892 18.502 23.184 29.455 13.661 19.086 4.273 9.924 µs 7.474 24.35
Server Jitter 195.176.26.206 21.225 22.186 28.582 87.120 366.737 498.616 699.441 338.155 476.430 109.440 123.568 µs 2.478 9.642
Server Jitter 2001:638:610:be01::103 (ptbtime3.ptb.de) 11.124 14.147 24.901 63.081 281.492 432.040 477.555 256.591 417.893 83.150 96.985 µs 2.479 8.813
Server Jitter 2001:7c0:2800::3:19 (time2.uni-konstanz.de) 0.044 0.363 0.504 0.807 1.540 1.697 1.865 1.036 1.334 0.276 0.843 ms 16.09 59.02
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 15.619 15.619 21.238 75.308 795.065 940.501 940.501 773.827 924.882 217.681 163.774 µs 1.742 6.356
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 14.460 17.653 24.797 76.716 325.906 444.265 688.236 301.109 426.612 102.670 118.533 µs 2.342 9.018
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.039 0.052 0.107 1.089 5.100 11.644 18.849 4.993 11.591 2.121 1.740 ms 3.136 22.1
Server Jitter 2a01:3f7:6:51::4 (lul1-ts.nts.netnod.se) 0.013 0.016 0.026 0.086 0.689 2.778 4.348 0.663 2.763 0.455 0.225 ms 3.729 27.63
Server Jitter 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) 3.298 4.475 7.284 20.949 48.140 63.050 68.701 40.856 58.575 12.571 24.069 µs 4.371 12.29
Server Jitter 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) 8.131 16.581 20.281 65.668 252.386 431.368 734.079 232.105 414.787 95.479 96.897 µs 2.767 14.22
Server Jitter 85.195.224.28 11.669 15.584 25.995 87.306 267.966 414.748 649.836 241.971 399.164 89.830 113.250 µs 2.605 10.52
Server Jitter PPS(0) 0.066 0.307 0.866 1.879 3.275 4.791 16.895 2.409 4.484 0.815 1.942 µs 8.206 34.34
Server Jitter SHM(0) 3.006 4.481 8.296 31.454 174.210 388.421 526.967 165.914 383.940 70.533 58.831 ms 2.405 11.77
Server Jitter SHM(2) 0.754 1.235 2.046 6.821 19.254 24.091 36.793 17.208 22.856 5.407 8.193 µs 2.974 9.282
Server Offset 195.176.26.206 -120.823 -104.698 -84.874 -48.254 -2.463 6.246 37.748 82.411 110.944 24.162 -46.174 µs -33.25 124
Server Offset 2001:638:610:be01::103 (ptbtime3.ptb.de) -2.784 -2.777 -2.760 -2.713 -2.666 -2.622 -2.608 0.094 0.155 0.029 -2.713 ms -8.219e+05 7.701e+07
Server Offset 2001:7c0:2800::3:19 (time2.uni-konstanz.de) -2.655 -2.550 -1.640 -1.572 -1.500 -1.451 -1.137 0.140 1.099 0.132 -1.583 ms -2232 2.977e+04
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 667.815 667.815 676.306 774.327 845.678 874.231 874.231 169.372 206.416 47.763 769.600 µs 3497 5.352e+04
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 586.795 604.914 643.959 732.917 862.782 892.120 901.427 218.823 287.206 59.102 739.890 µs 1563 1.842e+04
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) -204.543 -195.430 -161.860 -80.553 -2.281 27.148 46.045 159.579 222.578 46.152 -80.983 µs -29.27 107.2
Server Offset 2a01:3f7:6:51::4 (lul1-ts.nts.netnod.se) 3.125 3.152 3.194 3.768 3.829 3.842 3.850 0.635 0.690 0.215 3.681 ms 4242 6.911e+04
Server Offset 2a02:168:420b:4::7b:12 (ntp02.maillink.ch) -83.033 -60.746 -37.956 -0.564 47.125 63.312 72.863 85.081 124.058 25.761 1.181 µs -3.621 8.964
Server Offset 2a02:168:420b:d::7b:12 (ntp01.maillink.ch) -54.715 -45.562 -25.018 11.402 53.104 75.188 91.428 78.122 120.750 24.118 12.391 µs -1.28 4.386
Server Offset 85.195.224.28 -311.753 -286.948 -198.223 59.458 143.820 167.141 191.718 342.043 454.089 99.555 30.136 µs -3.876 12.03
Server Offset PPS(0) -47.940 -32.722 -26.070 0.481 18.912 26.473 36.601 44.982 59.195 13.483 -1.386 µs -5.036 13.29
Server Offset SHM(0) -440.376 -369.277 -321.958 -207.282 -153.573 138.845 165.379 168.385 508.122 72.154 -209.563 ms -69.1 304.7
Server Offset SHM(2) -45.645 -33.159 -27.056 -0.358 17.650 24.868 30.446 44.706 58.027 13.382 -2.317 µs -5.532 14.83
TDOP 0.510 0.520 0.590 0.870 1.210 1.340 2.710 0.620 0.820 0.222 0.883 37.82 177.5
Temp ZONE0 55.100 55.650 56.750 57.850 59.500 60.050 61.150 2.750 4.400 0.999 58.083 °C
nSats 6.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.043 9.219 nSat 505.2 4143
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!