NTPsec

Kong

Report generated: Fri Jan 23 13:49:00 2026 UTC
Start Time: Thu Jan 22 13:49:00 2026 UTC
End Time: Fri Jan 23 13:49:00 2026 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 -6.178 -6.178 -5.729 -0.040 2.740 5.972 5.972 8.469 12.150 2.249 -0.335 ms -0.6184 5.152
Local Clock Frequency Offset 11.623 11.623 11.664 11.916 13.347 13.681 13.681 1.683 2.058 0.523 12.087 ppm 1.969 5.626

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.343 0.343 0.354 0.923 2.245 2.285 2.285 1.891 1.941 0.665 1.100 ms 0.4197 1.658

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 62.177 62.177 66.458 136.242 383.152 437.819 437.819 316.694 375.642 111.928 185.966 ppb 0.6322 1.974

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 -6.178 -6.178 -5.729 -0.040 2.740 5.972 5.972 8.469 12.150 2.249 -0.335 ms -0.6184 5.152

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.623 11.623 11.664 11.916 13.347 13.681 13.681 1.683 2.058 0.523 12.087 ppm 1.969 5.626
Temp /dev/nvme0n1 59.000 60.000 63.000 70.000 71.000 71.000 71.000 8.000 11.000 2.378 68.656 °C
Temp /dev/nvme1n1 45.000 46.000 47.000 51.000 53.000 55.000 57.000 6.000 9.000 1.755 50.323 °C
Temp /dev/sda 43.000 43.000 43.000 46.000 47.000 48.000 48.000 4.000 5.000 1.309 45.885 °C
Temp /dev/sdb 31.000 31.000 31.000 34.000 36.000 37.000 37.000 5.000 6.000 1.410 33.573 °C
Temp LM0 48.000 49.000 50.000 54.000 57.000 58.000 59.000 7.000 9.000 2.457 53.830 °C
Temp LM1 35.250 35.500 36.500 39.000 60.000 75.625 78.125 23.500 40.125 8.022 41.286 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.242 25.062 °C
Temp LM11 72.000 72.000 74.000 77.000 78.000 79.000 79.000 4.000 7.000 1.285 76.691 °C
Temp LM12 3.000 9.000 10.000 23.000 29.000 33.000 37.000 19.000 24.000 4.669 21.990 °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 35.000 36.000 36.000 38.000 40.000 40.000 40.000 4.000 4.000 1.029 37.795 °C
Temp LM15 30.000 31.000 32.000 33.000 49.000 64.000 67.000 17.000 33.000 6.530 35.174 °C
Temp LM16 80.000 80.000 82.500 86.500 88.000 89.000 89.500 5.500 9.000 1.695 86.333 °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 35.250 35.500 36.250 38.750 59.000 76.000 78.000 22.750 40.500 8.033 41.085 °C
Temp LM20 35.250 35.500 36.500 39.125 60.000 75.625 78.125 23.500 40.125 8.020 41.272 °C
Temp LM21 80.000 80.250 82.500 86.875 88.375 89.000 89.500 5.875 8.750 1.687 86.493 °C
Temp LM22 31.000 31.000 31.000 34.000 36.000 37.000 37.000 5.000 6.000 1.409 33.688 °C
Temp LM23 58.850 59.850 62.850 69.850 70.850 70.850 70.850 8.000 11.000 2.379 68.510 °C
Temp LM3 43.000 43.000 43.000 46.000 48.000 48.000 48.000 5.000 5.000 1.332 45.913 °C
Temp LM4 44.850 44.850 46.850 50.850 52.850 54.850 56.850 6.000 10.000 1.806 50.156 °C
Temp LM5 44.850 45.850 46.850 50.850 52.850 54.850 56.850 6.000 9.000 1.772 50.163 °C
Temp LM6 52.850 53.850 55.850 58.850 65.850 66.850 74.850 10.000 13.000 3.245 60.090 °C
Temp LM7 44.850 44.850 46.850 49.850 52.850 54.850 56.850 6.000 10.000 1.772 50.163 °C
Temp LM8 35.000 35.000 36.000 38.000 40.000 40.000 40.000 4.000 5.000 1.027 37.792 °C
Temp LM9 31.000 31.000 32.500 34.000 39.500 50.500 51.000 7.000 19.500 3.667 34.681 °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) -45.618 -23.442 -11.479 -0.139 4.502 7.885 11.093 15.981 31.327 5.532 -1.498 ms -3.103 19.62

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) -8.005 -7.837 -6.815 -0.809 0.853 4.491 4.816 7.667 12.328 2.268 -1.404 ms -0.9296 4.869

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 -7.945 -7.743 -7.193 -1.183 1.605 4.242 4.535 8.798 11.984 2.358 -1.696 ms -0.7788 4.382

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 -6.422 -6.422 -5.748 -0.056 3.242 6.074 6.074 8.990 12.496 2.300 -0.403 ms -0.612 5.102

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) -8.512 -8.512 -4.001 -0.438 2.965 5.567 5.567 6.966 14.080 2.254 -0.350 ms -0.6126 5.34

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) -7.828 -7.828 -5.756 -0.190 3.352 6.018 6.018 9.108 13.846 2.439 -0.416 ms -0.505 4.314

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.495 -4.495 -4.495 0.194 5.322 5.322 5.322 9.817 9.817 2.812 1.319 ms 0.1134 2.207

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.363 -1.363 -0.952 0.095 2.931 2.931 2.931 3.883 4.294 0.997 0.211 ms 0.8822 3.677

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) -417.217 -408.422 -404.693 -400.293 -395.262 -392.912 -387.858 9.431 15.509 2.955 -400.210 ms -0.1208 4.497

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.037 0.085 0.169 5.036 14.556 35.383 63.647 14.387 35.298 6.730 5.968 ms 3.461 23.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) 5.066 7.034 19.458 59.840 279.820 423.284 519.222 260.362 416.250 83.689 89.626 µs 2.169 8.389

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 5.455 8.697 20.078 64.471 265.144 371.306 421.284 245.066 362.609 77.097 91.121 µs 1.671 6.047

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.087 0.087 0.154 0.598 5.934 7.908 7.908 5.780 7.821 1.913 1.472 ms 1.781 5.395

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.665 0.665 0.951 2.125 7.503 8.309 8.309 6.553 7.643 1.690 2.573 ms 1.685 5.828

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.714 0.714 0.917 2.179 6.338 8.611 8.611 5.421 7.898 1.668 2.577 ms 1.713 6.346

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.775 0.775 0.775 2.432 8.313 8.313 8.313 7.538 7.538 2.073 2.736 ms 1.42 4.038

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.694 0.694 0.740 1.106 5.418 5.418 5.418 4.679 4.724 1.125 1.573 ms 2.195 7.368

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.273 0.566 0.811 1.833 4.503 6.976 16.115 3.691 6.410 1.299 2.159 ms 2.457 14.59

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.623 11.623 11.664 11.916 13.347 13.681 13.681 1.683 2.058 0.523 12.087 ppm 1.969 5.626
Local Clock Time Offset -6.178 -6.178 -5.729 -0.040 2.740 5.972 5.972 8.469 12.150 2.249 -0.335 ms -0.6184 5.152
Local RMS Frequency Jitter 62.177 62.177 66.458 136.242 383.152 437.819 437.819 316.694 375.642 111.928 185.966 ppb 0.6322 1.974
Local RMS Time Jitter 0.343 0.343 0.354 0.923 2.245 2.285 2.285 1.891 1.941 0.665 1.100 ms 0.4197 1.658
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.037 0.085 0.169 5.036 14.556 35.383 63.647 14.387 35.298 6.730 5.968 ms 3.461 23.2
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 5.066 7.034 19.458 59.840 279.820 423.284 519.222 260.362 416.250 83.689 89.626 µs 2.169 8.389
Server Jitter 204.17.205.1 5.455 8.697 20.078 64.471 265.144 371.306 421.284 245.066 362.609 77.097 91.121 µs 1.671 6.047
Server Jitter 204.17.205.30 0.087 0.087 0.154 0.598 5.934 7.908 7.908 5.780 7.821 1.913 1.472 ms 1.781 5.395
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.665 0.665 0.951 2.125 7.503 8.309 8.309 6.553 7.643 1.690 2.573 ms 1.685 5.828
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.714 0.714 0.917 2.179 6.338 8.611 8.611 5.421 7.898 1.668 2.577 ms 1.713 6.346
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.775 0.775 0.775 2.432 8.313 8.313 8.313 7.538 7.538 2.073 2.736 ms 1.42 4.038
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.694 0.694 0.740 1.106 5.418 5.418 5.418 4.679 4.724 1.125 1.573 ms 2.195 7.368
Server Jitter SHM(0) 0.273 0.566 0.811 1.833 4.503 6.976 16.115 3.691 6.410 1.299 2.159 ms 2.457 14.59
Server Offset 2001:470:e815::24 (pi4.rellim.com) -45.618 -23.442 -11.479 -0.139 4.502 7.885 11.093 15.981 31.327 5.532 -1.498 ms -3.103 19.62
Server Offset 2001:470:e815::8 (spidey.rellim.com) -8.005 -7.837 -6.815 -0.809 0.853 4.491 4.816 7.667 12.328 2.268 -1.404 ms -0.9296 4.869
Server Offset 204.17.205.1 -7.945 -7.743 -7.193 -1.183 1.605 4.242 4.535 8.798 11.984 2.358 -1.696 ms -0.7788 4.382
Server Offset 204.17.205.30 -6.422 -6.422 -5.748 -0.056 3.242 6.074 6.074 8.990 12.496 2.300 -0.403 ms -0.612 5.102
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -8.512 -8.512 -4.001 -0.438 2.965 5.567 5.567 6.966 14.080 2.254 -0.350 ms -0.6126 5.34
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -7.828 -7.828 -5.756 -0.190 3.352 6.018 6.018 9.108 13.846 2.439 -0.416 ms -0.505 4.314
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -4.495 -4.495 -4.495 0.194 5.322 5.322 5.322 9.817 9.817 2.812 1.319 ms 0.1134 2.207
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -1.363 -1.363 -0.952 0.095 2.931 2.931 2.931 3.883 4.294 0.997 0.211 ms 0.8822 3.677
Server Offset SHM(0) -417.217 -408.422 -404.693 -400.293 -395.262 -392.912 -387.858 9.431 15.509 2.955 -400.210 ms -0.1208 4.497
Temp /dev/nvme0n1 59.000 60.000 63.000 70.000 71.000 71.000 71.000 8.000 11.000 2.378 68.656 °C
Temp /dev/nvme1n1 45.000 46.000 47.000 51.000 53.000 55.000 57.000 6.000 9.000 1.755 50.323 °C
Temp /dev/sda 43.000 43.000 43.000 46.000 47.000 48.000 48.000 4.000 5.000 1.309 45.885 °C
Temp /dev/sdb 31.000 31.000 31.000 34.000 36.000 37.000 37.000 5.000 6.000 1.410 33.573 °C
Temp LM0 48.000 49.000 50.000 54.000 57.000 58.000 59.000 7.000 9.000 2.457 53.830 °C
Temp LM1 35.250 35.500 36.500 39.000 60.000 75.625 78.125 23.500 40.125 8.022 41.286 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.242 25.062 °C
Temp LM11 72.000 72.000 74.000 77.000 78.000 79.000 79.000 4.000 7.000 1.285 76.691 °C
Temp LM12 3.000 9.000 10.000 23.000 29.000 33.000 37.000 19.000 24.000 4.669 21.990 °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 35.000 36.000 36.000 38.000 40.000 40.000 40.000 4.000 4.000 1.029 37.795 °C
Temp LM15 30.000 31.000 32.000 33.000 49.000 64.000 67.000 17.000 33.000 6.530 35.174 °C
Temp LM16 80.000 80.000 82.500 86.500 88.000 89.000 89.500 5.500 9.000 1.695 86.333 °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 35.250 35.500 36.250 38.750 59.000 76.000 78.000 22.750 40.500 8.033 41.085 °C
Temp LM20 35.250 35.500 36.500 39.125 60.000 75.625 78.125 23.500 40.125 8.020 41.272 °C
Temp LM21 80.000 80.250 82.500 86.875 88.375 89.000 89.500 5.875 8.750 1.687 86.493 °C
Temp LM22 31.000 31.000 31.000 34.000 36.000 37.000 37.000 5.000 6.000 1.409 33.688 °C
Temp LM23 58.850 59.850 62.850 69.850 70.850 70.850 70.850 8.000 11.000 2.379 68.510 °C
Temp LM3 43.000 43.000 43.000 46.000 48.000 48.000 48.000 5.000 5.000 1.332 45.913 °C
Temp LM4 44.850 44.850 46.850 50.850 52.850 54.850 56.850 6.000 10.000 1.806 50.156 °C
Temp LM5 44.850 45.850 46.850 50.850 52.850 54.850 56.850 6.000 9.000 1.772 50.163 °C
Temp LM6 52.850 53.850 55.850 58.850 65.850 66.850 74.850 10.000 13.000 3.245 60.090 °C
Temp LM7 44.850 44.850 46.850 49.850 52.850 54.850 56.850 6.000 10.000 1.772 50.163 °C
Temp LM8 35.000 35.000 36.000 38.000 40.000 40.000 40.000 4.000 5.000 1.027 37.792 °C
Temp LM9 31.000 31.000 32.500 34.000 39.500 50.500 51.000 7.000 19.500 3.667 34.681 °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!