NTPsec

Kong

Report generated: Sun Oct 11 13:59:00 2026 UTC
Start Time: Sun Oct 4 13:59:00 2026 UTC
End Time: Sun Oct 11 13: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 -0.759 -0.158 -0.066 -0.001 0.069 0.301 49.772 0.135 0.459 1.039 0.028 ms 41.41 1789
Local Clock Frequency Offset 11.400 11.518 11.925 13.370 14.471 15.249 15.327 2.546 3.731 0.629 13.335 ppm -0.1567 6.395

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.009 0.011 0.015 0.031 0.069 1.211 17.597 0.054 1.200 0.863 0.107 ms 15.29 259.3

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 5.275 7.413 16.935 74.376 151.162 343.092 66.963 145.887 28.248 24.216 ppb 4.903 35.35

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 -0.759 -0.158 -0.066 -0.001 0.069 0.301 49.772 0.135 0.459 1.039 0.028 ms 41.41 1789

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.400 11.518 11.925 13.370 14.471 15.249 15.327 2.546 3.731 0.629 13.335 ppm -0.1567 6.395
Temp /dev/nvme0n1 61.000 61.000 65.000 71.000 73.000 74.000 74.000 8.000 13.000 2.570 70.442 °C
Temp /dev/nvme1n1 47.000 49.000 51.000 55.000 56.000 60.000 64.000 5.000 11.000 1.915 54.124 °C
Temp /dev/sda 46.000 46.000 48.000 51.000 52.000 53.000 53.000 4.000 7.000 1.517 50.260 °C
Temp /dev/sdb 35.000 35.000 37.000 39.000 41.000 42.000 43.000 4.000 7.000 1.408 38.766 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 62.000 63.000 8.000 13.000 2.616 54.031 °C
Temp LM1 40.500 40.875 41.625 43.625 70.250 79.250 85.500 28.625 38.375 7.798 45.657 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.419 25.226 °C
Temp LM11 73.000 75.000 78.000 81.000 83.000 83.000 84.000 5.000 8.000 1.558 81.146 °C
Temp LM12 4.000 9.000 10.000 23.000 32.000 37.000 48.000 22.000 28.000 5.425 22.769 °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 40.000 40.000 42.000 44.000 46.000 48.000 48.000 4.000 8.000 1.442 44.183 °C
Temp LM15 35.000 36.000 37.000 38.000 59.000 68.000 73.000 22.000 32.000 6.284 39.913 °C
Temp LM16 81.000 83.500 86.000 92.500 93.500 93.500 94.000 7.500 10.000 2.166 91.771 °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 40.000 40.750 41.750 43.500 68.750 78.250 87.000 27.000 37.500 7.529 45.716 °C
Temp LM20 40.500 40.875 41.625 43.625 70.250 79.250 85.375 28.625 38.375 7.794 45.651 °C
Temp LM21 81.125 83.500 86.250 92.500 93.750 93.750 94.250 7.500 10.250 2.163 91.913 °C
Temp LM22 35.000 35.000 37.000 39.000 41.000 42.000 43.000 4.000 7.000 1.398 38.858 °C
Temp LM23 60.850 60.850 64.850 70.850 72.850 73.850 73.850 8.000 13.000 2.568 70.308 °C
Temp LM3 46.000 46.000 48.000 51.000 52.000 53.000 53.000 4.000 7.000 1.511 50.258 °C
Temp LM4 46.850 47.850 50.850 54.850 55.850 59.850 63.850 5.000 12.000 1.918 53.963 °C
Temp LM5 46.850 48.850 50.850 54.850 55.850 59.850 63.850 5.000 11.000 1.916 53.973 °C
Temp LM6 54.850 55.850 58.850 61.850 64.850 74.850 81.850 6.000 19.000 2.655 62.046 °C
Temp LM7 46.850 48.850 50.850 54.850 56.850 59.850 63.850 6.000 11.000 1.921 53.983 °C
Temp LM8 40.000 40.000 42.000 44.000 46.000 48.000 48.000 4.000 8.000 1.439 44.185 °C
Temp LM9 36.000 36.000 37.000 38.500 49.500 55.000 55.500 12.500 19.000 3.623 39.480 °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) -0.821 -0.161 -0.078 0.014 0.095 0.389 49.839 0.173 0.549 1.683 0.081 ms 27.67 790.6

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) -456.869 -390.022 -151.907 6.036 150.369 194.694 216.782 302.276 584.716 106.456 5.014 µs -1.054 5.551

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.692 -0.658 -0.363 0.049 0.291 0.376 49.610 0.654 1.034 1.665 0.068 ms 27.65 797.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 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 -0.735 -0.141 -0.097 -0.017 0.054 0.233 49.703 0.151 0.374 1.711 0.047 ms 27.14 755.2

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

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

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

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



Server Offset 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) 0.153 1.181 1.468 2.204 3.309 3.798 52.241 1.841 2.616 1.886 2.402 ms 21.88 551.6

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) -12.432 -11.481 -11.075 -10.176 -8.977 -7.179 40.862 2.098 4.302 2.031 -10.024 ms 19.62 461.2

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

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

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

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



Server Offset 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) -12.224 -11.651 -11.196 -10.744 -10.349 -9.756 -9.720 0.847 1.895 0.306 -10.767 ms -0.517 7.202

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) -373.431 -362.785 -360.478 -356.391 -131.655 -127.296 -122.873 228.823 235.489 59.505 -339.861 ms 3.226 11.43

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 0.006 0.013 0.104 0.183 0.214 40.704 0.170 0.207 1.189 0.145 ms 29.57 914.9

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 4.597 7.831 59.076 162.518 201.292 231.854 154.687 196.695 48.672 69.519 µs 0.7972 3.019

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 0.008 0.015 0.117 0.205 0.244 40.564 0.190 0.237 1.181 0.153 ms 29.73 922.1

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 0.008 0.015 0.112 0.207 0.260 42.226 0.192 0.252 1.528 0.176 ms 24.3 608.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 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.393 0.586 1.353 4.257 9.122 38.740 3.670 8.728 1.981 1.757 ms 8.34 109.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 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.000 0.404 0.645 1.388 5.094 10.022 40.799 4.449 9.617 2.372 1.892 ms 9.176 122.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 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.369 0.417 0.661 1.382 2.817 8.703 23.485 2.156 8.286 2.019 1.677 ms 8.924 94.25

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.371 0.527 1.340 4.084 7.185 34.350 3.557 6.815 1.358 1.705 ms 3.982 40.65

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.400 11.518 11.925 13.370 14.471 15.249 15.327 2.546 3.731 0.629 13.335 ppm -0.1567 6.395
Local Clock Time Offset -0.759 -0.158 -0.066 -0.001 0.069 0.301 49.772 0.135 0.459 1.039 0.028 ms 41.41 1789
Local RMS Frequency Jitter 0.000 5.275 7.413 16.935 74.376 151.162 343.092 66.963 145.887 28.248 24.216 ppb 4.903 35.35
Local RMS Time Jitter 0.009 0.011 0.015 0.031 0.069 1.211 17.597 0.054 1.200 0.863 0.107 ms 15.29 259.3
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.006 0.013 0.104 0.183 0.214 40.704 0.170 0.207 1.189 0.145 ms 29.57 914.9
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 4.597 7.831 59.076 162.518 201.292 231.854 154.687 196.695 48.672 69.519 µs 0.7972 3.019
Server Jitter 204.17.205.1 0.000 0.008 0.015 0.117 0.205 0.244 40.564 0.190 0.237 1.181 0.153 ms 29.73 922.1
Server Jitter 204.17.205.30 0.000 0.008 0.015 0.112 0.207 0.260 42.226 0.192 0.252 1.528 0.176 ms 24.3 608.2
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.393 0.586 1.353 4.257 9.122 38.740 3.670 8.728 1.981 1.757 ms 8.34 109.3
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.404 0.645 1.388 5.094 10.022 40.799 4.449 9.617 2.372 1.892 ms 9.176 122.2
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.369 0.417 0.661 1.382 2.817 8.703 23.485 2.156 8.286 2.019 1.677 ms 8.924 94.25
Server Jitter SHM(0) 0.000 0.371 0.527 1.340 4.084 7.185 34.350 3.557 6.815 1.358 1.705 ms 3.982 40.65
Server Offset 2001:470:e815::24 (pi4.rellim.com) -0.821 -0.161 -0.078 0.014 0.095 0.389 49.839 0.173 0.549 1.683 0.081 ms 27.67 790.6
Server Offset 2001:470:e815::8 (spidey.rellim.com) -456.869 -390.022 -151.907 6.036 150.369 194.694 216.782 302.276 584.716 106.456 5.014 µs -1.054 5.551
Server Offset 204.17.205.1 -1.692 -0.658 -0.363 0.049 0.291 0.376 49.610 0.654 1.034 1.665 0.068 ms 27.65 797.3
Server Offset 204.17.205.30 -0.735 -0.141 -0.097 -0.017 0.054 0.233 49.703 0.151 0.374 1.711 0.047 ms 27.14 755.2
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.153 1.181 1.468 2.204 3.309 3.798 52.241 1.841 2.616 1.886 2.402 ms 21.88 551.6
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -12.432 -11.481 -11.075 -10.176 -8.977 -7.179 40.862 2.098 4.302 2.031 -10.024 ms 19.62 461.2
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -12.224 -11.651 -11.196 -10.744 -10.349 -9.756 -9.720 0.847 1.895 0.306 -10.767 ms -0.517 7.202
Server Offset SHM(0) -373.431 -362.785 -360.478 -356.391 -131.655 -127.296 -122.873 228.823 235.489 59.505 -339.861 ms 3.226 11.43
Temp /dev/nvme0n1 61.000 61.000 65.000 71.000 73.000 74.000 74.000 8.000 13.000 2.570 70.442 °C
Temp /dev/nvme1n1 47.000 49.000 51.000 55.000 56.000 60.000 64.000 5.000 11.000 1.915 54.124 °C
Temp /dev/sda 46.000 46.000 48.000 51.000 52.000 53.000 53.000 4.000 7.000 1.517 50.260 °C
Temp /dev/sdb 35.000 35.000 37.000 39.000 41.000 42.000 43.000 4.000 7.000 1.408 38.766 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 62.000 63.000 8.000 13.000 2.616 54.031 °C
Temp LM1 40.500 40.875 41.625 43.625 70.250 79.250 85.500 28.625 38.375 7.798 45.657 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.419 25.226 °C
Temp LM11 73.000 75.000 78.000 81.000 83.000 83.000 84.000 5.000 8.000 1.558 81.146 °C
Temp LM12 4.000 9.000 10.000 23.000 32.000 37.000 48.000 22.000 28.000 5.425 22.769 °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 40.000 40.000 42.000 44.000 46.000 48.000 48.000 4.000 8.000 1.442 44.183 °C
Temp LM15 35.000 36.000 37.000 38.000 59.000 68.000 73.000 22.000 32.000 6.284 39.913 °C
Temp LM16 81.000 83.500 86.000 92.500 93.500 93.500 94.000 7.500 10.000 2.166 91.771 °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 40.000 40.750 41.750 43.500 68.750 78.250 87.000 27.000 37.500 7.529 45.716 °C
Temp LM20 40.500 40.875 41.625 43.625 70.250 79.250 85.375 28.625 38.375 7.794 45.651 °C
Temp LM21 81.125 83.500 86.250 92.500 93.750 93.750 94.250 7.500 10.250 2.163 91.913 °C
Temp LM22 35.000 35.000 37.000 39.000 41.000 42.000 43.000 4.000 7.000 1.398 38.858 °C
Temp LM23 60.850 60.850 64.850 70.850 72.850 73.850 73.850 8.000 13.000 2.568 70.308 °C
Temp LM3 46.000 46.000 48.000 51.000 52.000 53.000 53.000 4.000 7.000 1.511 50.258 °C
Temp LM4 46.850 47.850 50.850 54.850 55.850 59.850 63.850 5.000 12.000 1.918 53.963 °C
Temp LM5 46.850 48.850 50.850 54.850 55.850 59.850 63.850 5.000 11.000 1.916 53.973 °C
Temp LM6 54.850 55.850 58.850 61.850 64.850 74.850 81.850 6.000 19.000 2.655 62.046 °C
Temp LM7 46.850 48.850 50.850 54.850 56.850 59.850 63.850 6.000 11.000 1.921 53.983 °C
Temp LM8 40.000 40.000 42.000 44.000 46.000 48.000 48.000 4.000 8.000 1.439 44.185 °C
Temp LM9 36.000 36.000 37.000 38.500 49.500 55.000 55.500 12.500 19.000 3.623 39.480 °C
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!