NTPsec

Kong

Report generated: Tue Jun 9 13:59:01 2026 UTC
Start Time: Tue Jun 2 13:59:00 2026 UTC
End Time: Tue Jun 9 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 -42.868 -0.281 -0.077 -0.001 0.070 0.242 3.021 0.147 0.523 1.340 -0.051 ms -29.16 888.6
Local Clock Frequency Offset 11.547 11.845 11.909 12.312 13.260 14.620 16.259 1.351 2.775 0.484 12.393 ppm 2.469 12.93

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.007 0.011 0.015 0.029 0.090 1.735 15.138 0.075 1.724 0.801 0.109 ms 13.52 202.1

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.246 8.019 16.214 80.576 167.318 980.453 72.557 162.072 54.820 27.663 ppb 10.16 132.3

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 -42.868 -0.281 -0.077 -0.001 0.070 0.242 3.021 0.147 0.523 1.340 -0.051 ms -29.16 888.6

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.547 11.845 11.909 12.312 13.260 14.620 16.259 1.351 2.775 0.484 12.393 ppm 2.469 12.93
Temp /dev/nvme0n1 59.000 62.000 67.000 71.000 72.000 73.000 75.000 5.000 11.000 2.067 70.175 °C
Temp /dev/nvme1n1 47.000 49.000 51.000 53.000 57.000 59.000 62.000 6.000 10.000 2.008 53.352 °C
Temp /dev/sda 45.000 45.000 46.000 48.000 50.000 52.000 53.000 4.000 7.000 1.443 48.435 °C
Temp /dev/sdb 34.000 34.000 35.000 36.000 40.000 42.000 42.000 5.000 8.000 1.531 36.439 °C
Temp LM0 48.000 49.000 50.000 54.000 58.000 59.000 61.000 8.000 10.000 2.399 53.886 °C
Temp LM1 37.875 38.375 38.875 40.625 47.875 75.250 78.625 9.000 36.875 4.992 41.921 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.310 25.108 °C
Temp LM11 73.000 75.000 78.000 80.000 81.000 82.000 82.000 3.000 7.000 1.214 79.861 °C
Temp LM12 2.000 9.000 16.000 24.000 35.000 41.000 57.000 19.000 32.000 5.842 24.859 °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 39.000 39.000 40.000 42.000 43.000 44.000 45.000 3.000 5.000 1.000 41.493 °C
Temp LM15 34.000 34.000 34.000 36.000 39.000 64.000 67.000 5.000 30.000 3.722 36.479 °C
Temp LM16 80.500 83.500 88.000 90.500 92.500 93.000 93.500 4.500 9.500 1.686 90.355 °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.750 38.500 39.000 41.000 47.000 73.500 80.750 8.000 35.000 4.737 42.030 °C
Temp LM20 37.875 38.375 38.875 40.625 47.750 75.250 78.375 8.875 36.875 4.952 41.898 °C
Temp LM21 80.750 83.500 88.000 90.750 92.500 93.000 93.750 4.500 9.500 1.683 90.503 °C
Temp LM22 34.000 34.000 35.000 36.000 40.000 42.000 42.000 5.000 8.000 1.511 36.489 °C
Temp LM23 58.850 61.850 66.850 70.850 71.850 72.850 74.850 5.000 11.000 2.051 70.040 °C
Temp LM3 45.000 45.000 46.000 48.000 50.000 52.000 53.000 4.000 7.000 1.445 48.433 °C
Temp LM4 46.850 48.850 50.850 52.850 56.850 58.850 61.850 6.000 10.000 2.003 53.209 °C
Temp LM5 46.850 48.850 50.850 52.850 56.850 58.850 61.850 6.000 10.000 2.015 53.215 °C
Temp LM6 54.850 56.850 58.850 60.850 68.850 73.850 79.850 10.000 17.000 3.427 62.075 °C
Temp LM7 46.850 48.850 50.850 52.850 56.850 58.850 61.850 6.000 10.000 2.019 53.226 °C
Temp LM8 39.000 39.000 40.000 42.000 43.000 44.000 45.000 3.000 5.000 1.002 41.493 °C
Temp LM9 34.000 34.000 34.500 36.000 39.500 51.000 53.500 5.000 17.000 2.191 36.469 °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) -42.682 -0.233 -0.102 0.003 0.088 0.350 40.963 0.189 0.582 1.267 0.008 ms -1.869 806.5

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) -43.139 -0.984 -0.348 0.009 0.164 0.358 3.820 0.513 1.342 1.682 -0.094 ms -24.08 599.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 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 -43.153 -0.828 -0.387 0.028 0.304 0.388 3.541 0.691 1.216 0.865 -0.032 ms -38.98 1770

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 -42.814 -0.295 -0.102 -0.005 0.068 0.213 3.080 0.170 0.508 1.098 -0.040 ms -36.34 1392

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) -42.803 -0.942 -0.572 1.910 15.089 21.648 26.111 15.662 22.590 4.356 2.523 ms 2.425 20.27

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) -42.587 -0.044 1.206 1.622 2.054 2.457 6.386 0.848 2.501 1.242 1.576 ms -28.85 987

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) -441.896 -404.949 -401.819 -396.815 -392.555 -390.733 -385.769 9.263 14.216 2.964 -396.981 ms -0.8123 7.896

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.007 0.021 0.107 0.182 0.267 41.453 0.160 0.260 1.377 0.188 ms 19.94 445.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 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 0.008 0.021 0.083 0.187 0.224 34.772 0.166 0.216 0.999 0.124 ms 31.33 1008

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.011 0.024 0.139 0.223 0.263 26.902 0.199 0.251 0.812 0.162 ms 29.69 909.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.026 0.131 0.214 0.330 30.751 0.188 0.322 1.062 0.170 ms 28.22 807.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 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.269 0.477 1.243 7.790 14.638 29.751 7.313 14.369 2.799 2.092 ms 4.281 27.48

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.239 0.420 1.042 2.673 3.603 27.141 2.253 3.363 1.169 1.215 ms 13.88 288.5

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.465 0.656 1.492 4.033 7.022 25.366 3.377 6.558 1.347 1.833 ms 4.153 35.95

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.547 11.845 11.909 12.312 13.260 14.620 16.259 1.351 2.775 0.484 12.393 ppm 2.469 12.93
Local Clock Time Offset -42.868 -0.281 -0.077 -0.001 0.070 0.242 3.021 0.147 0.523 1.340 -0.051 ms -29.16 888.6
Local RMS Frequency Jitter 0.000 5.246 8.019 16.214 80.576 167.318 980.453 72.557 162.072 54.820 27.663 ppb 10.16 132.3
Local RMS Time Jitter 0.007 0.011 0.015 0.029 0.090 1.735 15.138 0.075 1.724 0.801 0.109 ms 13.52 202.1
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.007 0.021 0.107 0.182 0.267 41.453 0.160 0.260 1.377 0.188 ms 19.94 445.3
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 0.008 0.021 0.083 0.187 0.224 34.772 0.166 0.216 0.999 0.124 ms 31.33 1008
Server Jitter 204.17.205.1 0.000 0.011 0.024 0.139 0.223 0.263 26.902 0.199 0.251 0.812 0.162 ms 29.69 909.1
Server Jitter 204.17.205.30 0.000 0.008 0.026 0.131 0.214 0.330 30.751 0.188 0.322 1.062 0.170 ms 28.22 807.3
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.269 0.477 1.243 7.790 14.638 29.751 7.313 14.369 2.799 2.092 ms 4.281 27.48
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.239 0.420 1.042 2.673 3.603 27.141 2.253 3.363 1.169 1.215 ms 13.88 288.5
Server Jitter SHM(0) 0.000 0.465 0.656 1.492 4.033 7.022 25.366 3.377 6.558 1.347 1.833 ms 4.153 35.95
Server Offset 2001:470:e815::24 (pi4.rellim.com) -42.682 -0.233 -0.102 0.003 0.088 0.350 40.963 0.189 0.582 1.267 0.008 ms -1.869 806.5
Server Offset 2001:470:e815::8 (spidey.rellim.com) -43.139 -0.984 -0.348 0.009 0.164 0.358 3.820 0.513 1.342 1.682 -0.094 ms -24.08 599.2
Server Offset 204.17.205.1 -43.153 -0.828 -0.387 0.028 0.304 0.388 3.541 0.691 1.216 0.865 -0.032 ms -38.98 1770
Server Offset 204.17.205.30 -42.814 -0.295 -0.102 -0.005 0.068 0.213 3.080 0.170 0.508 1.098 -0.040 ms -36.34 1392
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -42.803 -0.942 -0.572 1.910 15.089 21.648 26.111 15.662 22.590 4.356 2.523 ms 2.425 20.27
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -42.587 -0.044 1.206 1.622 2.054 2.457 6.386 0.848 2.501 1.242 1.576 ms -28.85 987
Server Offset SHM(0) -441.896 -404.949 -401.819 -396.815 -392.555 -390.733 -385.769 9.263 14.216 2.964 -396.981 ms -0.8123 7.896
Temp /dev/nvme0n1 59.000 62.000 67.000 71.000 72.000 73.000 75.000 5.000 11.000 2.067 70.175 °C
Temp /dev/nvme1n1 47.000 49.000 51.000 53.000 57.000 59.000 62.000 6.000 10.000 2.008 53.352 °C
Temp /dev/sda 45.000 45.000 46.000 48.000 50.000 52.000 53.000 4.000 7.000 1.443 48.435 °C
Temp /dev/sdb 34.000 34.000 35.000 36.000 40.000 42.000 42.000 5.000 8.000 1.531 36.439 °C
Temp LM0 48.000 49.000 50.000 54.000 58.000 59.000 61.000 8.000 10.000 2.399 53.886 °C
Temp LM1 37.875 38.375 38.875 40.625 47.875 75.250 78.625 9.000 36.875 4.992 41.921 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.310 25.108 °C
Temp LM11 73.000 75.000 78.000 80.000 81.000 82.000 82.000 3.000 7.000 1.214 79.861 °C
Temp LM12 2.000 9.000 16.000 24.000 35.000 41.000 57.000 19.000 32.000 5.842 24.859 °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 39.000 39.000 40.000 42.000 43.000 44.000 45.000 3.000 5.000 1.000 41.493 °C
Temp LM15 34.000 34.000 34.000 36.000 39.000 64.000 67.000 5.000 30.000 3.722 36.479 °C
Temp LM16 80.500 83.500 88.000 90.500 92.500 93.000 93.500 4.500 9.500 1.686 90.355 °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.750 38.500 39.000 41.000 47.000 73.500 80.750 8.000 35.000 4.737 42.030 °C
Temp LM20 37.875 38.375 38.875 40.625 47.750 75.250 78.375 8.875 36.875 4.952 41.898 °C
Temp LM21 80.750 83.500 88.000 90.750 92.500 93.000 93.750 4.500 9.500 1.683 90.503 °C
Temp LM22 34.000 34.000 35.000 36.000 40.000 42.000 42.000 5.000 8.000 1.511 36.489 °C
Temp LM23 58.850 61.850 66.850 70.850 71.850 72.850 74.850 5.000 11.000 2.051 70.040 °C
Temp LM3 45.000 45.000 46.000 48.000 50.000 52.000 53.000 4.000 7.000 1.445 48.433 °C
Temp LM4 46.850 48.850 50.850 52.850 56.850 58.850 61.850 6.000 10.000 2.003 53.209 °C
Temp LM5 46.850 48.850 50.850 52.850 56.850 58.850 61.850 6.000 10.000 2.015 53.215 °C
Temp LM6 54.850 56.850 58.850 60.850 68.850 73.850 79.850 10.000 17.000 3.427 62.075 °C
Temp LM7 46.850 48.850 50.850 52.850 56.850 58.850 61.850 6.000 10.000 2.019 53.226 °C
Temp LM8 39.000 39.000 40.000 42.000 43.000 44.000 45.000 3.000 5.000 1.002 41.493 °C
Temp LM9 34.000 34.000 34.500 36.000 39.500 51.000 53.500 5.000 17.000 2.191 36.469 °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!