NTPsec

Kong

Report generated: Wed Mar 26 00:49:00 2025 UTC
Start Time: Tue Mar 25 00:49:00 2025 UTC
End Time: Wed Mar 26 00:49:00 2025 UTC
Report Period: 1.0 days
Warning: plots clipped

Daily stats   Weekly stats   Live GNSS Data   24 Hour Scatter Plots: ( )

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 -445.095 -247.545 -79.363 1.815 90.675 350.667 576.563 170.038 598.212 79.966 5.425 µs -2.367 19.16
Local Clock Frequency Offset 11.275 11.329 11.370 11.516 13.826 13.849 13.865 2.456 2.520 0.943 12.142 ppm 1709 2.074e+04

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 0.060 17.137 20.070 43.016 87.260 192.475 224.049 67.190 175.338 27.810 48.550 µs 5.503 27.15

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.000 10.441 13.021 21.840 118.865 181.458 214.267 105.844 171.017 33.735 35.893 ppb 2.722 10.5

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 -445.095 -247.545 -79.363 1.815 90.675 350.667 576.563 170.038 598.212 79.966 5.425 µs -2.367 19.16

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 11.275 11.329 11.370 11.516 13.826 13.849 13.865 2.456 2.520 0.943 12.142 ppm 1709 2.074e+04
Temp /dev/sda 45.000 45.000 45.000 48.000 49.000 49.000 49.000 4.000 4.000 1.293 47.531 °C
Temp /dev/sdb 33.000 34.000 34.000 36.000 37.000 37.000 38.000 3.000 3.000 1.009 35.549 °C
Temp LM0 48.000 49.000 50.000 55.000 58.000 58.000 59.000 8.000 9.000 2.672 54.247 °C
Temp LM1 36.500 36.875 37.625 39.375 75.500 77.000 82.875 37.875 40.125 15.594 49.895 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM11 61.000 61.000 62.000 63.000 64.000 65.000 65.000 2.000 4.000 0.909 62.736 °C
Temp LM12 3.000 4.000 8.000 22.000 27.000 30.000 38.000 19.000 26.000 7.167 18.083 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM14 42.000 43.000 44.000 45.000 46.000 47.000 47.000 2.000 4.000 0.903 44.729 °C
Temp LM15 32.000 33.000 33.000 35.000 64.000 65.000 71.000 31.000 32.000 12.531 42.844 °C
Temp LM16 66.000 66.500 67.000 68.000 69.500 70.000 70.000 2.500 3.500 0.841 68.009 °C
Temp LM17 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM18 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM19 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM2 37.000 37.250 37.750 40.750 74.500 78.250 81.500 36.750 41.000 14.906 49.824 °C
Temp LM20 36.500 36.875 37.625 39.375 75.500 77.000 82.750 37.875 40.125 15.586 49.889 °C
Temp LM21 66.250 66.500 67.250 68.000 69.750 70.000 70.000 2.500 3.500 0.827 68.162 °C
Temp LM22 34.000 34.000 34.000 36.000 37.000 37.000 38.000 3.000 3.000 1.001 35.608 °C
Temp LM23 65.850 65.850 67.850 69.850 71.850 71.850 73.850 4.000 6.000 1.270 69.812 °C
Temp LM3 45.000 45.000 45.000 48.000 49.000 49.000 49.000 4.000 4.000 1.312 47.514 °C
Temp LM4 48.850 49.850 49.850 50.850 52.850 54.850 55.850 3.000 5.000 1.148 51.222 °C
Temp LM5 48.850 48.850 49.850 50.850 52.850 54.850 55.850 3.000 6.000 1.144 51.218 °C
Temp LM6 56.850 56.850 57.850 59.850 64.850 73.850 73.850 7.000 17.000 2.697 60.194 °C
Temp LM7 48.850 49.850 49.850 50.850 53.850 54.850 55.850 4.000 5.000 1.155 51.232 °C
Temp LM8 43.000 43.000 44.000 45.000 46.000 47.000 47.000 2.000 4.000 0.895 44.729 °C
Temp LM9 32.500 33.000 33.500 35.000 52.000 52.000 52.000 18.500 19.000 7.326 39.530 °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 3.000 4.000 6.000 9.000 12.000 14.000 15.000 6.000 10.000 2.048 8.845 nSat 46.81 194.1
TDOP 0.780 0.910 1.030 1.700 4.700 32.400 92.800 3.670 31.490 5.505 2.678 7.354 89.87

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 2001:470:e815::24 (pi4.rellim.com)

peer offset 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e815::24 (pi4.rellim.com) -465,110.748 -286.135 -102.169 -2.549 101.622 377.871 546.822 203.791 664.006 18,988.221 -776.841 µs -28.66 706.3

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:470:e815::8 (spidey.rellim.com)

peer offset 2001:470:e815::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e815::8 (spidey.rellim.com) -464,958.742 -369.856 -340.955 67.612 610.491 728.158 1,054.554 951.446 1,098.014 37,140.468 -2,914.351 µs -16.85 215.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 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net)

peer offset 2001:67c:1270:0:dea6:32ff:feaf:803b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) -465.029 -1.040 -0.918 -0.583 -0.234 0.068 0.431 0.684 1.109 41.543 -4.306 ms -15.66 179.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 204.17.205.1

peer offset 204.17.205.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.1 -465,485.034 -475.911 -383.269 14.898 241.801 310.838 580.929 625.070 786.749 19,148.168 -800.198 µs -28.48 696.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 204.17.205.30

peer offset 204.17.205.30 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.30 -465,412.478 -184.584 -74.277 14.025 98.160 378.405 691.174 172.437 562.989 26,606.926 -1,507.132 µs -21.73 384.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 2405:fc00::1 (robusta.dcs1.biz)

peer offset 2405:fc00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -460.453 1.689 1.977 4.238 4.788 4.996 5.263 2.811 3.307 27.430 2.458 ms -20.29 350.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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -464.435 -1.023 -0.917 -0.506 -0.047 0.178 0.414 0.870 1.201 26.698 -2.031 ms -21.73 381.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) -429.541 -353.634 275.237 542.230 808.891 913.114 989.864 533.654 1,266.748 190.143 534.814 µs 9.986 29.44

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) -110.806 173.211 288.318 543.137 826.242 867.336 1,040.679 537.924 694.125 160.586 540.103 µs 20.06 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 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) -591.431 -146.198 -143.386 -128.573 -122.100 -120.063 -117.052 21.286 26.135 9.178 -130.271 ms -3579 5.754e+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 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 2001:470:e815::24 (pi4.rellim.com)

peer jitter 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 3.821 7.033 71.579 162.042 191.953 384.793 155.009 188.132 55.055 75.130 µs 1.833 5.837

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:470:e815::8 (spidey.rellim.com)

peer jitter 2001:470:e815::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 3.651 5.697 60.407 199.608 235.261 351.255 193.911 231.610 66.572 82.942 µs 1.361 3.568

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:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net)

peer jitter 2001:67c:1270:0:dea6:32ff:feaf:803b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) 0.000 0.000 0.269 0.677 2.602 2.818 3.001 2.333 2.818 0.728 0.965 ms 2.128 5.275

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 204.17.205.1

peer jitter 204.17.205.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.1 0.000 4.107 7.150 60.449 200.321 248.078 423.458 193.171 243.971 69.737 86.024 µs 1.488 4.453

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 204.17.205.30

peer jitter 204.17.205.30 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.30 0.000 6.912 11.488 84.622 189.659 219.945 748.395 178.171 213.033 76.941 95.505 µs 4.258 32.19

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 2405:fc00::1 (robusta.dcs1.biz)

peer jitter 2405:fc00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.147 0.249 0.919 2.891 14.981 27.527 2.641 14.835 2.150 1.335 ms 7.112 77.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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer jitter 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.158 0.240 0.610 2.327 7.088 9.007 2.087 6.929 1.076 0.881 ms 4.766 33.07

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) 0.123 0.130 0.226 0.520 1.610 2.097 2.589 1.384 1.966 0.408 0.631 ms 3.898 14.61

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) 0.000 0.083 0.172 0.432 1.740 3.932 4.024 1.568 3.849 0.665 0.609 ms 3.303 15.38

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) 0.000 0.285 0.454 2.095 10.307 13.646 455.057 9.853 13.361 10.861 4.141 ms 24.72 829.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset 11.275 11.329 11.370 11.516 13.826 13.849 13.865 2.456 2.520 0.943 12.142 ppm 1709 2.074e+04
Local Clock Time Offset -445.095 -247.545 -79.363 1.815 90.675 350.667 576.563 170.038 598.212 79.966 5.425 µs -2.367 19.16
Local RMS Frequency Jitter 0.000 10.441 13.021 21.840 118.865 181.458 214.267 105.844 171.017 33.735 35.893 ppb 2.722 10.5
Local RMS Time Jitter 0.060 17.137 20.070 43.016 87.260 192.475 224.049 67.190 175.338 27.810 48.550 µs 5.503 27.15
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 3.821 7.033 71.579 162.042 191.953 384.793 155.009 188.132 55.055 75.130 µs 1.833 5.837
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 3.651 5.697 60.407 199.608 235.261 351.255 193.911 231.610 66.572 82.942 µs 1.361 3.568
Server Jitter 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) 0.000 0.000 0.269 0.677 2.602 2.818 3.001 2.333 2.818 0.728 0.965 ms 2.128 5.275
Server Jitter 204.17.205.1 0.000 4.107 7.150 60.449 200.321 248.078 423.458 193.171 243.971 69.737 86.024 µs 1.488 4.453
Server Jitter 204.17.205.30 0.000 6.912 11.488 84.622 189.659 219.945 748.395 178.171 213.033 76.941 95.505 µs 4.258 32.19
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.147 0.249 0.919 2.891 14.981 27.527 2.641 14.835 2.150 1.335 ms 7.112 77.34
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.158 0.240 0.610 2.327 7.088 9.007 2.087 6.929 1.076 0.881 ms 4.766 33.07
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.123 0.130 0.226 0.520 1.610 2.097 2.589 1.384 1.966 0.408 0.631 ms 3.898 14.61
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.083 0.172 0.432 1.740 3.932 4.024 1.568 3.849 0.665 0.609 ms 3.303 15.38
Server Jitter SHM(0) 0.000 0.285 0.454 2.095 10.307 13.646 455.057 9.853 13.361 10.861 4.141 ms 24.72 829.3
Server Offset 2001:470:e815::24 (pi4.rellim.com) -465,110.748 -286.135 -102.169 -2.549 101.622 377.871 546.822 203.791 664.006 18,988.221 -776.841 µs -28.66 706.3
Server Offset 2001:470:e815::8 (spidey.rellim.com) -464,958.742 -369.856 -340.955 67.612 610.491 728.158 1,054.554 951.446 1,098.014 37,140.468 -2,914.351 µs -16.85 215.4
Server Offset 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) -465.029 -1.040 -0.918 -0.583 -0.234 0.068 0.431 0.684 1.109 41.543 -4.306 ms -15.66 179.4
Server Offset 204.17.205.1 -465,485.034 -475.911 -383.269 14.898 241.801 310.838 580.929 625.070 786.749 19,148.168 -800.198 µs -28.48 696.5
Server Offset 204.17.205.30 -465,412.478 -184.584 -74.277 14.025 98.160 378.405 691.174 172.437 562.989 26,606.926 -1,507.132 µs -21.73 384.4
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -460.453 1.689 1.977 4.238 4.788 4.996 5.263 2.811 3.307 27.430 2.458 ms -20.29 350.5
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -464.435 -1.023 -0.917 -0.506 -0.047 0.178 0.414 0.870 1.201 26.698 -2.031 ms -21.73 381.5
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -429.541 -353.634 275.237 542.230 808.891 913.114 989.864 533.654 1,266.748 190.143 534.814 µs 9.986 29.44
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -110.806 173.211 288.318 543.137 826.242 867.336 1,040.679 537.924 694.125 160.586 540.103 µs 20.06 67
Server Offset SHM(0) -591.431 -146.198 -143.386 -128.573 -122.100 -120.063 -117.052 21.286 26.135 9.178 -130.271 ms -3579 5.754e+04
TDOP 0.780 0.910 1.030 1.700 4.700 32.400 92.800 3.670 31.490 5.505 2.678 7.354 89.87
Temp /dev/sda 45.000 45.000 45.000 48.000 49.000 49.000 49.000 4.000 4.000 1.293 47.531 °C
Temp /dev/sdb 33.000 34.000 34.000 36.000 37.000 37.000 38.000 3.000 3.000 1.009 35.549 °C
Temp LM0 48.000 49.000 50.000 55.000 58.000 58.000 59.000 8.000 9.000 2.672 54.247 °C
Temp LM1 36.500 36.875 37.625 39.375 75.500 77.000 82.875 37.875 40.125 15.594 49.895 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM11 61.000 61.000 62.000 63.000 64.000 65.000 65.000 2.000 4.000 0.909 62.736 °C
Temp LM12 3.000 4.000 8.000 22.000 27.000 30.000 38.000 19.000 26.000 7.167 18.083 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM14 42.000 43.000 44.000 45.000 46.000 47.000 47.000 2.000 4.000 0.903 44.729 °C
Temp LM15 32.000 33.000 33.000 35.000 64.000 65.000 71.000 31.000 32.000 12.531 42.844 °C
Temp LM16 66.000 66.500 67.000 68.000 69.500 70.000 70.000 2.500 3.500 0.841 68.009 °C
Temp LM17 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM18 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM19 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM2 37.000 37.250 37.750 40.750 74.500 78.250 81.500 36.750 41.000 14.906 49.824 °C
Temp LM20 36.500 36.875 37.625 39.375 75.500 77.000 82.750 37.875 40.125 15.586 49.889 °C
Temp LM21 66.250 66.500 67.250 68.000 69.750 70.000 70.000 2.500 3.500 0.827 68.162 °C
Temp LM22 34.000 34.000 34.000 36.000 37.000 37.000 38.000 3.000 3.000 1.001 35.608 °C
Temp LM23 65.850 65.850 67.850 69.850 71.850 71.850 73.850 4.000 6.000 1.270 69.812 °C
Temp LM3 45.000 45.000 45.000 48.000 49.000 49.000 49.000 4.000 4.000 1.312 47.514 °C
Temp LM4 48.850 49.850 49.850 50.850 52.850 54.850 55.850 3.000 5.000 1.148 51.222 °C
Temp LM5 48.850 48.850 49.850 50.850 52.850 54.850 55.850 3.000 6.000 1.144 51.218 °C
Temp LM6 56.850 56.850 57.850 59.850 64.850 73.850 73.850 7.000 17.000 2.697 60.194 °C
Temp LM7 48.850 49.850 49.850 50.850 53.850 54.850 55.850 4.000 5.000 1.155 51.232 °C
Temp LM8 43.000 43.000 44.000 45.000 46.000 47.000 47.000 2.000 4.000 0.895 44.729 °C
Temp LM9 32.500 33.000 33.500 35.000 52.000 52.000 52.000 18.500 19.000 7.326 39.530 °C
nSats 3.000 4.000 6.000 9.000 12.000 14.000 15.000 6.000 10.000 2.048 8.845 nSat 46.81 194.1
Summary as CSV file


This server:

Motherboard:
OS: Gentoo unstable
GPS/PPS server: gpsd
NTP server: NTPsec
../ntp.conf

Notes:

Feb 21 03:28:57 UTC 2019: New install

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!