NTPsec

Kong

Report generated: Mon Feb 9 14:59:01 2026 UTC
Start Time: Mon Feb 2 14:59:00 2026 UTC
End Time: Mon Feb 9 14:59:00 2026 UTC
Report Period: 7.0 days

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 -7.900 -6.955 -2.088 -0.082 1.335 5.964 7.197 3.423 12.919 1.465 -0.130 ms -0.8024 14.38
Local Clock Frequency Offset 11.474 11.486 11.884 12.115 14.316 15.428 15.734 2.432 3.941 0.713 12.343 ppm 2.825 10.79

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.113 0.137 0.161 0.354 1.386 1.680 1.874 1.225 1.544 0.382 0.495 ms 1.585 4.622

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 12.036 12.867 15.835 61.254 451.381 987.110 1,197.124 435.546 974.243 178.206 126.077 ppb 3.102 14.12

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 -7.900 -6.955 -2.088 -0.082 1.335 5.964 7.197 3.423 12.919 1.465 -0.130 ms -0.8024 14.38

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.474 11.486 11.884 12.115 14.316 15.428 15.734 2.432 3.941 0.713 12.343 ppm 2.825 10.79
Temp /dev/nvme0n1 59.000 61.000 67.000 70.000 72.000 72.000 74.000 5.000 11.000 1.942 69.808 °C
Temp /dev/nvme1n1 45.000 49.000 50.000 52.000 57.000 59.000 61.000 7.000 10.000 2.182 52.814 °C
Temp /dev/sda 45.000 45.000 45.000 48.000 50.000 50.000 52.000 5.000 5.000 1.571 47.690 °C
Temp /dev/sdb 33.000 33.000 33.000 36.000 38.000 39.000 40.000 5.000 6.000 1.497 35.768 °C
Temp LM0 48.000 49.000 50.000 54.000 58.000 58.000 60.000 8.000 9.000 2.468 54.037 °C
Temp LM1 36.375 37.125 37.500 40.250 73.875 76.000 78.500 36.375 38.875 9.039 42.981 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.263 25.075 °C
Temp LM11 71.000 74.000 77.000 79.000 81.000 81.000 81.000 4.000 7.000 1.259 78.844 °C
Temp LM12 3.000 9.000 9.000 24.000 36.000 43.000 60.000 27.000 34.000 6.977 24.134 °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 38.000 38.000 38.000 40.000 43.000 44.000 45.000 5.000 6.000 1.373 40.293 °C
Temp LM15 32.000 33.000 33.000 35.000 62.000 65.000 67.000 29.000 32.000 7.236 37.221 °C
Temp LM16 79.000 82.000 86.500 89.500 91.500 92.000 92.500 5.000 10.000 1.704 89.065 °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 36.500 37.250 37.750 40.500 73.000 75.500 78.750 35.250 38.250 8.731 43.002 °C
Temp LM20 36.375 37.250 37.500 40.250 73.875 76.000 78.375 36.375 38.750 9.038 42.977 °C
Temp LM21 79.000 82.000 86.750 89.500 91.500 92.000 92.750 4.750 10.000 1.705 89.208 °C
Temp LM22 33.000 33.000 34.000 36.000 38.000 39.000 40.000 4.000 6.000 1.434 35.834 °C
Temp LM23 58.850 60.850 66.850 69.850 71.850 71.850 73.850 5.000 11.000 1.931 69.662 °C
Temp LM3 45.000 45.000 45.000 48.000 50.000 50.000 52.000 5.000 5.000 1.566 47.697 °C
Temp LM4 44.850 48.850 49.850 51.850 56.850 58.850 60.850 7.000 10.000 2.189 52.659 °C
Temp LM5 44.850 48.850 49.850 51.850 56.850 58.850 60.850 7.000 10.000 2.184 52.667 °C
Temp LM6 52.850 56.850 57.850 60.850 68.850 72.850 78.850 11.000 16.000 3.876 62.470 °C
Temp LM7 44.850 48.850 49.850 51.850 56.850 58.850 60.850 7.000 10.000 2.183 52.662 °C
Temp LM8 38.000 38.000 38.000 40.000 43.000 44.000 45.000 5.000 6.000 1.369 40.293 °C
Temp LM9 32.500 33.500 33.500 35.500 52.500 53.000 53.500 19.000 19.500 4.429 36.627 °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 10.000 12.000 12.000 12.000 12.000 12.000 13.000 0.000 0.000 0.017 12.000 nSat -60.17 1.086e+04
TDOP 0.710 0.780 0.860 1.250 2.510 5.320 8.800 1.650 4.540 0.730 1.433 4.786 34.37

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) -58.679 -34.284 -14.493 -0.061 3.844 8.121 16.645 18.336 42.405 6.810 -1.653 ms -3.485 19.59

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) -10.179 -7.598 -2.449 0.469 2.526 5.833 7.427 4.976 13.431 1.895 0.358 ms -1.523 10.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 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 -6.417 -4.903 -1.655 0.948 2.753 6.445 7.612 4.408 11.348 1.544 0.852 ms -0.6658 9.538

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 -8.017 -7.254 -2.040 -0.173 1.187 5.583 6.927 3.227 12.837 1.452 -0.254 ms -0.9595 14.93

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) -7.475 -4.195 -0.541 1.809 3.845 7.164 10.144 4.387 11.360 1.628 1.760 ms -0.6556 11.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 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) -35.961 -35.545 -30.808 1.001 3.237 6.837 9.374 34.045 42.383 10.972 -4.151 ms -1.634 4.24

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) -4.765 -4.406 -1.271 1.564 3.874 4.674 5.445 5.146 9.080 1.634 1.460 ms -0.9308 5.222

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) -1.799 -1.653 0.226 1.727 5.975 8.429 8.866 5.749 10.083 1.760 2.110 ms 1.664 6.92

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) -182.492 -149.117 -145.635 -131.433 -125.015 -120.848 -115.500 20.620 28.269 6.326 -132.915 ms -0.7873 3.316

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) -318.080 -318.080 -317.141 -308.551 -303.726 -299.964 -299.964 13.415 18.115 3.746 -309.022 ms -0.5573 3.268

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.021 0.073 0.149 5.081 19.991 42.057 258.849 19.842 41.984 11.686 7.020 ms 9.588 151.2

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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) 2.523 6.827 19.080 59.735 189.447 329.004 1,685.476 170.367 322.177 73.011 80.119 µs 6.808 118.6

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 3.175 8.431 19.365 79.382 196.379 314.091 971.256 177.014 305.660 67.471 91.435 µs 2.807 26.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.022 0.036 0.078 0.393 1.926 4.648 5.908 1.848 4.611 0.797 0.607 ms 3.642 19.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.403 0.466 0.633 1.358 3.732 8.049 8.537 3.099 7.583 1.200 1.682 ms 2.825 13.58

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.302 0.385 0.641 1.924 16.626 23.794 32.814 15.985 23.409 5.334 4.330 ms 2.202 7.978

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.535 0.581 0.671 1.420 3.430 4.477 6.077 2.759 3.896 0.900 1.681 ms 1.405 5.973

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.447 0.473 0.593 1.403 3.137 3.964 4.367 2.544 3.491 0.780 1.574 ms 1.258 4.68

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.320 0.502 4.485 10.755 12.965 45.023 10.253 12.646 3.549 4.715 ms 0.5763 3.373

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.000 0.000 0.000 3.941 8.608 9.045 9.045 8.608 9.045 2.040 4.054 ms 0.4148 3.127

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.474 11.486 11.884 12.115 14.316 15.428 15.734 2.432 3.941 0.713 12.343 ppm 2.825 10.79
Local Clock Time Offset -7.900 -6.955 -2.088 -0.082 1.335 5.964 7.197 3.423 12.919 1.465 -0.130 ms -0.8024 14.38
Local RMS Frequency Jitter 12.036 12.867 15.835 61.254 451.381 987.110 1,197.124 435.546 974.243 178.206 126.077 ppb 3.102 14.12
Local RMS Time Jitter 0.113 0.137 0.161 0.354 1.386 1.680 1.874 1.225 1.544 0.382 0.495 ms 1.585 4.622
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.021 0.073 0.149 5.081 19.991 42.057 258.849 19.842 41.984 11.686 7.020 ms 9.588 151.2
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 2.523 6.827 19.080 59.735 189.447 329.004 1,685.476 170.367 322.177 73.011 80.119 µs 6.808 118.6
Server Jitter 204.17.205.1 3.175 8.431 19.365 79.382 196.379 314.091 971.256 177.014 305.660 67.471 91.435 µs 2.807 26.3
Server Jitter 204.17.205.30 0.022 0.036 0.078 0.393 1.926 4.648 5.908 1.848 4.611 0.797 0.607 ms 3.642 19.3
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.403 0.466 0.633 1.358 3.732 8.049 8.537 3.099 7.583 1.200 1.682 ms 2.825 13.58
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.302 0.385 0.641 1.924 16.626 23.794 32.814 15.985 23.409 5.334 4.330 ms 2.202 7.978
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.535 0.581 0.671 1.420 3.430 4.477 6.077 2.759 3.896 0.900 1.681 ms 1.405 5.973
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.447 0.473 0.593 1.403 3.137 3.964 4.367 2.544 3.491 0.780 1.574 ms 1.258 4.68
Server Jitter SHM(0) 0.000 0.320 0.502 4.485 10.755 12.965 45.023 10.253 12.646 3.549 4.715 ms 0.5763 3.373
Server Jitter SHM(2) 0.000 0.000 0.000 3.941 8.608 9.045 9.045 8.608 9.045 2.040 4.054 ms 0.4148 3.127
Server Offset 2001:470:e815::24 (pi4.rellim.com) -58.679 -34.284 -14.493 -0.061 3.844 8.121 16.645 18.336 42.405 6.810 -1.653 ms -3.485 19.59
Server Offset 2001:470:e815::8 (spidey.rellim.com) -10.179 -7.598 -2.449 0.469 2.526 5.833 7.427 4.976 13.431 1.895 0.358 ms -1.523 10.29
Server Offset 204.17.205.1 -6.417 -4.903 -1.655 0.948 2.753 6.445 7.612 4.408 11.348 1.544 0.852 ms -0.6658 9.538
Server Offset 204.17.205.30 -8.017 -7.254 -2.040 -0.173 1.187 5.583 6.927 3.227 12.837 1.452 -0.254 ms -0.9595 14.93
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -7.475 -4.195 -0.541 1.809 3.845 7.164 10.144 4.387 11.360 1.628 1.760 ms -0.6556 11.3
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -35.961 -35.545 -30.808 1.001 3.237 6.837 9.374 34.045 42.383 10.972 -4.151 ms -1.634 4.24
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -4.765 -4.406 -1.271 1.564 3.874 4.674 5.445 5.146 9.080 1.634 1.460 ms -0.9308 5.222
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -1.799 -1.653 0.226 1.727 5.975 8.429 8.866 5.749 10.083 1.760 2.110 ms 1.664 6.92
Server Offset SHM(0) -182.492 -149.117 -145.635 -131.433 -125.015 -120.848 -115.500 20.620 28.269 6.326 -132.915 ms -0.7873 3.316
Server Offset SHM(2) -318.080 -318.080 -317.141 -308.551 -303.726 -299.964 -299.964 13.415 18.115 3.746 -309.022 ms -0.5573 3.268
TDOP 0.710 0.780 0.860 1.250 2.510 5.320 8.800 1.650 4.540 0.730 1.433 4.786 34.37
Temp /dev/nvme0n1 59.000 61.000 67.000 70.000 72.000 72.000 74.000 5.000 11.000 1.942 69.808 °C
Temp /dev/nvme1n1 45.000 49.000 50.000 52.000 57.000 59.000 61.000 7.000 10.000 2.182 52.814 °C
Temp /dev/sda 45.000 45.000 45.000 48.000 50.000 50.000 52.000 5.000 5.000 1.571 47.690 °C
Temp /dev/sdb 33.000 33.000 33.000 36.000 38.000 39.000 40.000 5.000 6.000 1.497 35.768 °C
Temp LM0 48.000 49.000 50.000 54.000 58.000 58.000 60.000 8.000 9.000 2.468 54.037 °C
Temp LM1 36.375 37.125 37.500 40.250 73.875 76.000 78.500 36.375 38.875 9.039 42.981 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.263 25.075 °C
Temp LM11 71.000 74.000 77.000 79.000 81.000 81.000 81.000 4.000 7.000 1.259 78.844 °C
Temp LM12 3.000 9.000 9.000 24.000 36.000 43.000 60.000 27.000 34.000 6.977 24.134 °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 38.000 38.000 38.000 40.000 43.000 44.000 45.000 5.000 6.000 1.373 40.293 °C
Temp LM15 32.000 33.000 33.000 35.000 62.000 65.000 67.000 29.000 32.000 7.236 37.221 °C
Temp LM16 79.000 82.000 86.500 89.500 91.500 92.000 92.500 5.000 10.000 1.704 89.065 °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 36.500 37.250 37.750 40.500 73.000 75.500 78.750 35.250 38.250 8.731 43.002 °C
Temp LM20 36.375 37.250 37.500 40.250 73.875 76.000 78.375 36.375 38.750 9.038 42.977 °C
Temp LM21 79.000 82.000 86.750 89.500 91.500 92.000 92.750 4.750 10.000 1.705 89.208 °C
Temp LM22 33.000 33.000 34.000 36.000 38.000 39.000 40.000 4.000 6.000 1.434 35.834 °C
Temp LM23 58.850 60.850 66.850 69.850 71.850 71.850 73.850 5.000 11.000 1.931 69.662 °C
Temp LM3 45.000 45.000 45.000 48.000 50.000 50.000 52.000 5.000 5.000 1.566 47.697 °C
Temp LM4 44.850 48.850 49.850 51.850 56.850 58.850 60.850 7.000 10.000 2.189 52.659 °C
Temp LM5 44.850 48.850 49.850 51.850 56.850 58.850 60.850 7.000 10.000 2.184 52.667 °C
Temp LM6 52.850 56.850 57.850 60.850 68.850 72.850 78.850 11.000 16.000 3.876 62.470 °C
Temp LM7 44.850 48.850 49.850 51.850 56.850 58.850 60.850 7.000 10.000 2.183 52.662 °C
Temp LM8 38.000 38.000 38.000 40.000 43.000 44.000 45.000 5.000 6.000 1.369 40.293 °C
Temp LM9 32.500 33.500 33.500 35.500 52.500 53.000 53.500 19.000 19.500 4.429 36.627 °C
nSats 10.000 12.000 12.000 12.000 12.000 12.000 13.000 0.000 0.000 0.017 12.000 nSat -60.17 1.086e+04
Summary as CSV file


This server:

Motherboard:
OS: Gentoo unstable
GPS:
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.
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 FIsher-Pearson moment of skewness. There are other different ways to calculate Skewness Wikipedia describes Skewness best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
Kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses standard Kurtosis. There are other different ways to calculate 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".
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!