NTPsec

Kong

Report generated: Thu Apr 3 02:49:00 2025 UTC
Start Time: Wed Apr 2 02:49:00 2025 UTC
End Time: Thu Apr 3 02: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 -1,062.308 -384.332 -78.797 0.073 79.912 479.275 1,106.805 158.709 863.607 118.508 -0.171 µs -0.6771 41.54
Local Clock Frequency Offset 11.322 11.335 11.370 11.448 11.927 13.200 13.705 0.558 1.865 0.302 11.554 ppm 3.916 21.62

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 15.999 20.092 23.554 40.590 191.562 752.172 1,040.757 168.008 732.080 115.093 66.753 µs 5.561 36.75

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 9.756 10.930 12.633 21.985 140.949 311.521 363.407 128.316 300.591 49.774 35.631 ppb 4.305 23.03

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 -1,062.308 -384.332 -78.797 0.073 79.912 479.275 1,106.805 158.709 863.607 118.508 -0.171 µs -0.6771 41.54

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.322 11.335 11.370 11.448 11.927 13.200 13.705 0.558 1.865 0.302 11.554 ppm 3.916 21.62
Temp /dev/sda 45.000 45.000 45.000 47.000 51.000 52.000 52.000 6.000 7.000 1.828 47.736 °C
Temp /dev/sdb 33.000 33.000 34.000 36.000 40.000 40.000 40.000 6.000 7.000 1.881 36.215 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 58.000 59.000 8.000 9.000 2.746 54.205 °C
Temp LM1 37.375 37.500 37.625 39.125 47.375 74.625 77.250 9.750 37.125 6.250 41.552 °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 62.000 62.000 62.000 63.000 64.000 64.000 1.000 2.000 0.488 62.285 °C
Temp LM12 9.000 9.000 15.000 22.000 28.000 32.000 38.000 13.000 23.000 4.682 21.340 °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 43.000 43.000 44.000 44.000 44.000 46.000 46.000 0.000 3.000 0.343 44.014 °C
Temp LM15 33.000 33.000 33.000 34.000 38.000 63.000 66.000 5.000 30.000 4.725 35.733 °C
Temp LM16 66.500 67.000 67.000 67.500 68.000 69.000 69.000 1.000 2.000 0.335 67.616 °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.250 37.250 37.750 40.250 48.250 73.500 78.000 10.500 36.250 5.997 41.552 °C
Temp LM20 37.375 37.500 37.625 39.125 47.500 74.250 77.125 9.875 36.750 6.228 41.528 °C
Temp LM21 66.750 67.000 67.250 67.750 68.250 69.000 69.250 1.000 2.000 0.312 67.779 °C
Temp LM22 33.000 34.000 34.000 36.000 40.000 40.000 40.000 6.000 6.000 1.831 36.295 °C
Temp LM23 62.850 63.850 66.850 69.850 70.850 70.850 73.850 4.000 7.000 1.428 69.451 °C
Temp LM3 45.000 45.000 45.000 48.000 51.000 52.000 52.000 6.000 7.000 1.813 47.760 °C
Temp LM4 47.850 47.850 48.850 50.850 51.850 53.850 55.850 3.000 6.000 0.815 50.631 °C
Temp LM5 47.850 48.850 49.850 50.850 51.850 53.850 55.850 2.000 5.000 0.800 50.659 °C
Temp LM6 55.850 56.850 56.850 58.850 61.850 66.850 73.850 5.000 10.000 1.841 59.076 °C
Temp LM7 47.850 47.850 48.850 50.850 51.850 53.850 55.850 3.000 6.000 0.813 50.649 °C
Temp LM8 43.000 43.000 44.000 44.000 44.000 46.000 46.000 0.000 3.000 0.343 44.014 °C
Temp LM9 33.500 33.500 33.500 34.500 38.500 50.500 51.500 5.000 17.000 2.778 35.580 °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.



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) -1,041.566 -229.336 -87.726 -3.052 82.945 368.303 23,108.836 170.671 597.639 992.262 44.560 µs 21.48 488

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) -1,025.381 -957.148 -810.163 69.167 384.662 458.393 542.637 1,194.825 1,415.541 309.187 -2.937 µs -1.529 5.265

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 -1,214.171 -839.054 -644.721 102.004 635.731 740.772 816.059 1,280.452 1,579.826 351.575 44.126 µs -0.4097 3.452

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 -408.998 -300.414 -89.537 4.211 104.478 279.642 412.626 194.015 580.056 75.190 6.289 µs -0.05685 13.74

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) 1.403 1.441 1.724 2.156 2.608 2.927 2.978 0.884 1.486 0.264 2.157 ms 0.1991 3.782

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) -1.820 -1.290 -0.985 -0.489 0.118 0.292 0.572 1.103 1.582 0.356 -0.438 ms -0.06218 2.963

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:4700:f1::1 (time.cloudflare.com)

peer offset 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -0.339 -0.339 0.152 0.643 1.126 1.561 1.561 0.974 1.900 0.290 0.626 ms -0.09105 4.949

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:4700:f1::123 (time.cloudflare.com)

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 0.145 0.337 0.455 0.747 1.034 1.208 1.522 0.578 0.872 0.186 0.754 ms 0.3638 4.17

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) -155.898 -142.438 -138.239 -127.349 -122.218 -120.884 -118.724 16.021 21.554 4.483 -127.971 ms -1.321 5.226

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 5.442 10.496 83.413 172.977 236.265 15,516.040 162.481 230.823 917.968 153.707 µs 14.08 209.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.205 4.358 8.483 75.600 195.871 252.695 358.290 187.388 248.337 65.838 89.374 µs 0.637 3.003

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.014 4.869 9.046 90.421 203.971 239.433 449.444 194.925 234.564 68.421 92.183 µs 0.5937 3.118

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 6.579 10.061 15.506 97.045 193.800 243.618 266.854 178.294 233.557 56.524 97.744 µs 0.3801 2.576

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.130 0.136 0.275 0.801 2.803 23.422 23.513 2.528 23.286 2.454 1.257 ms 7.754 68.87

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.131 0.205 0.315 0.719 2.111 63.564 63.726 1.796 63.358 6.409 1.586 ms 9.386 90.71

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.128 0.128 0.264 0.595 1.426 2.732 2.732 1.161 2.603 0.481 0.724 ms 2.493 10.23

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.176 0.234 0.287 0.522 1.560 3.775 4.101 1.273 3.541 0.528 0.679 ms 3.905 22.72

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.117 0.274 0.390 1.070 7.278 9.809 25.206 6.888 9.534 2.330 2.086 ms 2.125 8.849

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.322 11.335 11.370 11.448 11.927 13.200 13.705 0.558 1.865 0.302 11.554 ppm 3.916 21.62
Local Clock Time Offset -1,062.308 -384.332 -78.797 0.073 79.912 479.275 1,106.805 158.709 863.607 118.508 -0.171 µs -0.6771 41.54
Local RMS Frequency Jitter 9.756 10.930 12.633 21.985 140.949 311.521 363.407 128.316 300.591 49.774 35.631 ppb 4.305 23.03
Local RMS Time Jitter 15.999 20.092 23.554 40.590 191.562 752.172 1,040.757 168.008 732.080 115.093 66.753 µs 5.561 36.75
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 5.442 10.496 83.413 172.977 236.265 15,516.040 162.481 230.823 917.968 153.707 µs 14.08 209.7
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 2.205 4.358 8.483 75.600 195.871 252.695 358.290 187.388 248.337 65.838 89.374 µs 0.637 3.003
Server Jitter 204.17.205.1 3.014 4.869 9.046 90.421 203.971 239.433 449.444 194.925 234.564 68.421 92.183 µs 0.5937 3.118
Server Jitter 204.17.205.30 6.579 10.061 15.506 97.045 193.800 243.618 266.854 178.294 233.557 56.524 97.744 µs 0.3801 2.576
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.130 0.136 0.275 0.801 2.803 23.422 23.513 2.528 23.286 2.454 1.257 ms 7.754 68.87
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.131 0.205 0.315 0.719 2.111 63.564 63.726 1.796 63.358 6.409 1.586 ms 9.386 90.71
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.128 0.128 0.264 0.595 1.426 2.732 2.732 1.161 2.603 0.481 0.724 ms 2.493 10.23
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.176 0.234 0.287 0.522 1.560 3.775 4.101 1.273 3.541 0.528 0.679 ms 3.905 22.72
Server Jitter SHM(0) 0.117 0.274 0.390 1.070 7.278 9.809 25.206 6.888 9.534 2.330 2.086 ms 2.125 8.849
Server Offset 2001:470:e815::24 (pi4.rellim.com) -1,041.566 -229.336 -87.726 -3.052 82.945 368.303 23,108.836 170.671 597.639 992.262 44.560 µs 21.48 488
Server Offset 2001:470:e815::8 (spidey.rellim.com) -1,025.381 -957.148 -810.163 69.167 384.662 458.393 542.637 1,194.825 1,415.541 309.187 -2.937 µs -1.529 5.265
Server Offset 204.17.205.1 -1,214.171 -839.054 -644.721 102.004 635.731 740.772 816.059 1,280.452 1,579.826 351.575 44.126 µs -0.4097 3.452
Server Offset 204.17.205.30 -408.998 -300.414 -89.537 4.211 104.478 279.642 412.626 194.015 580.056 75.190 6.289 µs -0.05685 13.74
Server Offset 2405:fc00::1 (robusta.dcs1.biz) 1.403 1.441 1.724 2.156 2.608 2.927 2.978 0.884 1.486 0.264 2.157 ms 0.1991 3.782
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -1.820 -1.290 -0.985 -0.489 0.118 0.292 0.572 1.103 1.582 0.356 -0.438 ms -0.06218 2.963
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -0.339 -0.339 0.152 0.643 1.126 1.561 1.561 0.974 1.900 0.290 0.626 ms -0.09105 4.949
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 0.145 0.337 0.455 0.747 1.034 1.208 1.522 0.578 0.872 0.186 0.754 ms 0.3638 4.17
Server Offset SHM(0) -155.898 -142.438 -138.239 -127.349 -122.218 -120.884 -118.724 16.021 21.554 4.483 -127.971 ms -1.321 5.226
Temp /dev/sda 45.000 45.000 45.000 47.000 51.000 52.000 52.000 6.000 7.000 1.828 47.736 °C
Temp /dev/sdb 33.000 33.000 34.000 36.000 40.000 40.000 40.000 6.000 7.000 1.881 36.215 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 58.000 59.000 8.000 9.000 2.746 54.205 °C
Temp LM1 37.375 37.500 37.625 39.125 47.375 74.625 77.250 9.750 37.125 6.250 41.552 °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 62.000 62.000 62.000 63.000 64.000 64.000 1.000 2.000 0.488 62.285 °C
Temp LM12 9.000 9.000 15.000 22.000 28.000 32.000 38.000 13.000 23.000 4.682 21.340 °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 43.000 43.000 44.000 44.000 44.000 46.000 46.000 0.000 3.000 0.343 44.014 °C
Temp LM15 33.000 33.000 33.000 34.000 38.000 63.000 66.000 5.000 30.000 4.725 35.733 °C
Temp LM16 66.500 67.000 67.000 67.500 68.000 69.000 69.000 1.000 2.000 0.335 67.616 °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.250 37.250 37.750 40.250 48.250 73.500 78.000 10.500 36.250 5.997 41.552 °C
Temp LM20 37.375 37.500 37.625 39.125 47.500 74.250 77.125 9.875 36.750 6.228 41.528 °C
Temp LM21 66.750 67.000 67.250 67.750 68.250 69.000 69.250 1.000 2.000 0.312 67.779 °C
Temp LM22 33.000 34.000 34.000 36.000 40.000 40.000 40.000 6.000 6.000 1.831 36.295 °C
Temp LM23 62.850 63.850 66.850 69.850 70.850 70.850 73.850 4.000 7.000 1.428 69.451 °C
Temp LM3 45.000 45.000 45.000 48.000 51.000 52.000 52.000 6.000 7.000 1.813 47.760 °C
Temp LM4 47.850 47.850 48.850 50.850 51.850 53.850 55.850 3.000 6.000 0.815 50.631 °C
Temp LM5 47.850 48.850 49.850 50.850 51.850 53.850 55.850 2.000 5.000 0.800 50.659 °C
Temp LM6 55.850 56.850 56.850 58.850 61.850 66.850 73.850 5.000 10.000 1.841 59.076 °C
Temp LM7 47.850 47.850 48.850 50.850 51.850 53.850 55.850 3.000 6.000 0.813 50.649 °C
Temp LM8 43.000 43.000 44.000 44.000 44.000 46.000 46.000 0.000 3.000 0.343 44.014 °C
Temp LM9 33.500 33.500 33.500 34.500 38.500 50.500 51.500 5.000 17.000 2.778 35.580 °C
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.
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!