NTPsec

Kong

Report generated: Thu Jan 8 14:59:00 2026 UTC
Start Time: Thu Jan 1 14:59:00 2026 UTC
End Time: Thu Jan 8 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.199 -4.839 -1.056 -0.044 0.985 4.536 6.304 2.041 9.375 1.055 -0.035 ms -0.242 20.19
Local Clock Frequency Offset 11.646 11.696 11.938 12.151 12.575 14.063 14.212 0.637 2.367 0.345 12.207 ppm 3.367 17.82

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.142 0.147 0.171 0.282 1.189 1.568 1.675 1.018 1.421 0.292 0.373 ms 2.834 10.64

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 18.089 20.669 24.060 43.802 270.147 402.768 452.400 246.087 382.099 74.007 66.142 ppb 3.22 13.06

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.199 -4.839 -1.056 -0.044 0.985 4.536 6.304 2.041 9.375 1.055 -0.035 ms -0.242 20.19

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.646 11.696 11.938 12.151 12.575 14.063 14.212 0.637 2.367 0.345 12.207 ppm 3.367 17.82
Temp /dev/nvme0n1 58.000 60.000 66.000 70.000 72.000 72.000 75.000 6.000 12.000 2.338 69.755 °C
Temp /dev/nvme1n1 45.000 47.000 49.000 53.000 56.000 57.000 60.000 7.000 10.000 2.093 52.657 °C
Temp /dev/sda 43.000 44.000 45.000 47.000 50.000 50.000 52.000 5.000 6.000 1.530 47.156 °C
Temp /dev/sdb 31.000 32.000 33.000 35.000 37.000 39.000 39.000 4.000 7.000 1.428 35.257 °C
Temp LM0 46.000 49.000 50.000 54.000 57.000 58.000 59.000 7.000 9.000 2.470 53.520 °C
Temp LM1 36.000 36.750 37.875 41.125 46.875 74.750 85.250 9.000 38.000 5.714 42.140 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.272 25.080 °C
Temp LM11 71.000 72.000 76.000 79.000 80.000 81.000 81.000 4.000 9.000 1.511 78.685 °C
Temp LM12 2.000 9.000 16.000 23.000 29.000 33.000 40.000 13.000 24.000 4.289 22.515 °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 36.000 37.000 38.000 40.000 41.000 42.000 43.000 3.000 5.000 1.120 39.778 °C
Temp LM15 31.000 32.000 33.000 35.000 39.000 63.000 74.000 6.000 31.000 4.541 36.174 °C
Temp LM16 78.500 80.500 85.000 89.500 91.000 91.500 92.000 6.000 11.000 2.020 89.038 °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.500 36.750 38.000 41.000 46.750 74.000 85.250 8.750 37.250 5.596 42.008 °C
Temp LM20 36.000 36.750 37.875 41.125 46.875 74.750 85.250 9.000 38.000 5.704 42.128 °C
Temp LM21 78.750 80.750 85.250 89.500 91.250 91.750 92.375 6.000 11.000 2.024 89.187 °C
Temp LM22 31.000 32.000 33.000 36.000 37.000 39.000 39.000 4.000 7.000 1.368 35.346 °C
Temp LM23 57.850 59.850 65.850 69.850 71.850 71.850 74.850 6.000 12.000 2.346 69.632 °C
Temp LM3 43.000 44.000 45.000 47.000 50.000 50.000 51.000 5.000 6.000 1.526 47.164 °C
Temp LM4 44.850 46.850 48.850 52.850 55.850 56.850 59.850 7.000 10.000 2.093 52.492 °C
Temp LM5 44.850 46.850 48.850 52.850 55.850 56.850 59.850 7.000 10.000 2.104 52.505 °C
Temp LM6 52.850 54.850 57.850 60.850 67.850 71.850 78.850 10.000 17.000 3.782 62.658 °C
Temp LM7 44.850 46.850 48.850 52.850 55.850 56.850 59.850 7.000 10.000 2.100 52.517 °C
Temp LM8 36.000 37.000 38.000 40.000 41.000 42.000 43.000 3.000 5.000 1.116 39.777 °C
Temp LM9 31.500 32.500 33.500 36.000 39.000 51.000 55.500 5.500 18.500 2.591 36.075 °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) -55.013 -27.975 -12.651 -0.101 3.375 7.847 24.341 16.026 35.822 5.862 -1.473 ms -3.242 19.12

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) -6.566 -4.623 -0.677 0.706 2.062 4.223 5.872 2.739 8.847 1.138 0.677 ms -1.37 14.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 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 -4.904 -1.245 1.155 2.442 3.645 7.002 8.333 2.489 8.247 1.102 2.440 ms -0.4647 15.26

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 -7.525 -5.002 -1.299 -0.198 0.811 4.304 5.542 2.110 9.307 1.064 -0.211 ms -0.6792 19.75

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) -4.616 -4.151 0.071 1.487 3.327 6.165 6.892 3.257 10.315 1.273 1.541 ms -0.5032 9.149

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) -6.432 -3.763 0.416 1.930 3.658 6.531 15.905 3.241 10.294 1.432 1.905 ms 1.637 32.9

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) -5.395 -5.384 -1.318 1.510 3.748 4.659 4.685 5.066 10.043 1.641 1.388 ms -1.846 8.956

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.205 -0.461 0.229 1.610 4.546 6.338 6.757 4.317 6.799 1.225 1.832 ms 1.427 6.211

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) -425.789 -410.645 -407.069 -400.514 -395.125 -393.090 -388.283 11.944 17.555 3.734 -400.756 ms -0.5024 3.967

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.024 0.068 0.156 4.766 16.155 31.263 139.605 15.999 31.195 7.766 6.117 ms 6.391 82.15

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.244 6.508 18.341 59.554 185.346 352.746 1,897.026 167.005 346.238 89.620 83.953 µs 7.829 113.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.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 4.117 8.063 18.780 70.509 187.107 239.818 417.665 168.327 231.755 58.182 86.187 µs 0.7883 3.42

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.043 0.061 0.103 0.323 1.618 4.852 5.873 1.515 4.791 0.779 0.545 ms 4.235 23.83

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.305 0.368 0.505 1.276 3.170 7.536 7.740 2.665 7.168 1.076 1.510 ms 3.208 17.09

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.200 0.278 0.446 1.132 3.836 13.592 21.464 3.390 13.314 1.943 1.555 ms 6.125 49

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.335 0.362 0.483 1.420 3.964 7.608 8.191 3.481 7.247 1.292 1.685 ms 3.072 14.43

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.265 0.281 0.372 1.338 3.448 111.228 111.325 3.076 110.947 16.775 4.179 ms 6.004 37.29

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.225 0.521 0.745 1.681 4.283 7.709 21.629 3.538 7.188 1.347 2.013 ms 3.161 20.32

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.646 11.696 11.938 12.151 12.575 14.063 14.212 0.637 2.367 0.345 12.207 ppm 3.367 17.82
Local Clock Time Offset -7.199 -4.839 -1.056 -0.044 0.985 4.536 6.304 2.041 9.375 1.055 -0.035 ms -0.242 20.19
Local RMS Frequency Jitter 18.089 20.669 24.060 43.802 270.147 402.768 452.400 246.087 382.099 74.007 66.142 ppb 3.22 13.06
Local RMS Time Jitter 0.142 0.147 0.171 0.282 1.189 1.568 1.675 1.018 1.421 0.292 0.373 ms 2.834 10.64
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.024 0.068 0.156 4.766 16.155 31.263 139.605 15.999 31.195 7.766 6.117 ms 6.391 82.15
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 2.244 6.508 18.341 59.554 185.346 352.746 1,897.026 167.005 346.238 89.620 83.953 µs 7.829 113.1
Server Jitter 204.17.205.1 4.117 8.063 18.780 70.509 187.107 239.818 417.665 168.327 231.755 58.182 86.187 µs 0.7883 3.42
Server Jitter 204.17.205.30 0.043 0.061 0.103 0.323 1.618 4.852 5.873 1.515 4.791 0.779 0.545 ms 4.235 23.83
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.305 0.368 0.505 1.276 3.170 7.536 7.740 2.665 7.168 1.076 1.510 ms 3.208 17.09
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.200 0.278 0.446 1.132 3.836 13.592 21.464 3.390 13.314 1.943 1.555 ms 6.125 49
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.335 0.362 0.483 1.420 3.964 7.608 8.191 3.481 7.247 1.292 1.685 ms 3.072 14.43
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.265 0.281 0.372 1.338 3.448 111.228 111.325 3.076 110.947 16.775 4.179 ms 6.004 37.29
Server Jitter SHM(0) 0.225 0.521 0.745 1.681 4.283 7.709 21.629 3.538 7.188 1.347 2.013 ms 3.161 20.32
Server Offset 2001:470:e815::24 (pi4.rellim.com) -55.013 -27.975 -12.651 -0.101 3.375 7.847 24.341 16.026 35.822 5.862 -1.473 ms -3.242 19.12
Server Offset 2001:470:e815::8 (spidey.rellim.com) -6.566 -4.623 -0.677 0.706 2.062 4.223 5.872 2.739 8.847 1.138 0.677 ms -1.37 14.43
Server Offset 204.17.205.1 -4.904 -1.245 1.155 2.442 3.645 7.002 8.333 2.489 8.247 1.102 2.440 ms -0.4647 15.26
Server Offset 204.17.205.30 -7.525 -5.002 -1.299 -0.198 0.811 4.304 5.542 2.110 9.307 1.064 -0.211 ms -0.6792 19.75
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -4.616 -4.151 0.071 1.487 3.327 6.165 6.892 3.257 10.315 1.273 1.541 ms -0.5032 9.149
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -6.432 -3.763 0.416 1.930 3.658 6.531 15.905 3.241 10.294 1.432 1.905 ms 1.637 32.9
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -5.395 -5.384 -1.318 1.510 3.748 4.659 4.685 5.066 10.043 1.641 1.388 ms -1.846 8.956
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -1.205 -0.461 0.229 1.610 4.546 6.338 6.757 4.317 6.799 1.225 1.832 ms 1.427 6.211
Server Offset SHM(0) -425.789 -410.645 -407.069 -400.514 -395.125 -393.090 -388.283 11.944 17.555 3.734 -400.756 ms -0.5024 3.967
Temp /dev/nvme0n1 58.000 60.000 66.000 70.000 72.000 72.000 75.000 6.000 12.000 2.338 69.755 °C
Temp /dev/nvme1n1 45.000 47.000 49.000 53.000 56.000 57.000 60.000 7.000 10.000 2.093 52.657 °C
Temp /dev/sda 43.000 44.000 45.000 47.000 50.000 50.000 52.000 5.000 6.000 1.530 47.156 °C
Temp /dev/sdb 31.000 32.000 33.000 35.000 37.000 39.000 39.000 4.000 7.000 1.428 35.257 °C
Temp LM0 46.000 49.000 50.000 54.000 57.000 58.000 59.000 7.000 9.000 2.470 53.520 °C
Temp LM1 36.000 36.750 37.875 41.125 46.875 74.750 85.250 9.000 38.000 5.714 42.140 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.272 25.080 °C
Temp LM11 71.000 72.000 76.000 79.000 80.000 81.000 81.000 4.000 9.000 1.511 78.685 °C
Temp LM12 2.000 9.000 16.000 23.000 29.000 33.000 40.000 13.000 24.000 4.289 22.515 °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 36.000 37.000 38.000 40.000 41.000 42.000 43.000 3.000 5.000 1.120 39.778 °C
Temp LM15 31.000 32.000 33.000 35.000 39.000 63.000 74.000 6.000 31.000 4.541 36.174 °C
Temp LM16 78.500 80.500 85.000 89.500 91.000 91.500 92.000 6.000 11.000 2.020 89.038 °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.500 36.750 38.000 41.000 46.750 74.000 85.250 8.750 37.250 5.596 42.008 °C
Temp LM20 36.000 36.750 37.875 41.125 46.875 74.750 85.250 9.000 38.000 5.704 42.128 °C
Temp LM21 78.750 80.750 85.250 89.500 91.250 91.750 92.375 6.000 11.000 2.024 89.187 °C
Temp LM22 31.000 32.000 33.000 36.000 37.000 39.000 39.000 4.000 7.000 1.368 35.346 °C
Temp LM23 57.850 59.850 65.850 69.850 71.850 71.850 74.850 6.000 12.000 2.346 69.632 °C
Temp LM3 43.000 44.000 45.000 47.000 50.000 50.000 51.000 5.000 6.000 1.526 47.164 °C
Temp LM4 44.850 46.850 48.850 52.850 55.850 56.850 59.850 7.000 10.000 2.093 52.492 °C
Temp LM5 44.850 46.850 48.850 52.850 55.850 56.850 59.850 7.000 10.000 2.104 52.505 °C
Temp LM6 52.850 54.850 57.850 60.850 67.850 71.850 78.850 10.000 17.000 3.782 62.658 °C
Temp LM7 44.850 46.850 48.850 52.850 55.850 56.850 59.850 7.000 10.000 2.100 52.517 °C
Temp LM8 36.000 37.000 38.000 40.000 41.000 42.000 43.000 3.000 5.000 1.116 39.777 °C
Temp LM9 31.500 32.500 33.500 36.000 39.000 51.000 55.500 5.500 18.500 2.591 36.075 °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!