NTPsec

Kong

Report generated: Sat Apr 1 13:49:01 2023 UTC
Start Time: Fri Mar 31 13:49:01 2023 UTC
End Time: Sat Apr 1 13:49:01 2023 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 -135.445 -81.555 -52.316 -1.451 51.359 76.911 154.837 103.675 158.466 32.845 -1.287 µs -4.102 11.94
Local Clock Frequency Offset 10.768 10.791 10.836 11.024 11.217 11.268 11.325 0.381 0.477 0.117 11.021 ppm 8.159e+05 7.625e+07

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 16.009 17.419 21.687 33.363 51.791 60.704 67.871 30.104 43.285 9.190 34.728 µs 30.42 116.2

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 6.954 8.034 10.488 17.694 34.818 51.864 60.521 24.330 43.830 8.077 19.532 ppb 9.027 35.1

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 -135.445 -81.555 -52.316 -1.451 51.359 76.911 154.837 103.675 158.466 32.845 -1.287 µs -4.102 11.94

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 10.768 10.791 10.836 11.024 11.217 11.268 11.325 0.381 0.477 0.117 11.021 ppm 8.159e+05 7.625e+07
Temp /dev/sda 43.000 43.000 44.000 45.000 48.000 49.000 49.000 4.000 6.000 1.317 45.208 °C
Temp /dev/sdb 32.000 32.000 32.000 33.000 37.000 37.000 37.000 5.000 5.000 1.307 33.486 °C
Temp LM0 49.000 49.000 49.000 54.000 58.000 59.000 59.000 9.000 10.000 2.841 54.139 °C
Temp LM1 72.250 72.250 72.375 72.500 73.375 73.875 81.125 1.000 1.625 0.596 72.701 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM11 57.000 57.000 57.000 58.000 59.000 59.000 59.000 2.000 2.000 0.573 58.240 °C
Temp LM12 7.000 7.000 7.000 8.000 8.000 8.000 9.000 1.000 1.000 0.492 7.622 °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 61.000 61.000 61.000 61.500 62.000 62.500 70.000 1.000 1.500 0.614 61.542 °C
Temp LM15 62.500 62.500 63.000 63.500 64.000 64.000 64.000 1.000 1.500 0.365 63.451 °C
Temp LM16 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °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 72.250 72.250 72.375 72.625 73.375 73.875 81.125 1.000 1.625 0.596 72.701 °C
Temp LM19 62.875 62.875 63.000 63.750 64.250 64.250 64.375 1.250 1.375 0.366 63.604 °C
Temp LM2 69.250 70.750 71.750 72.500 73.250 73.750 80.250 1.500 3.000 0.717 72.454 °C
Temp LM20 32.000 32.000 32.000 33.000 37.000 37.000 37.000 5.000 5.000 1.308 33.559 °C
Temp LM21 62.850 62.850 63.850 65.850 66.850 67.850 67.850 3.000 5.000 1.011 65.649 °C
Temp LM3 43.000 43.000 44.000 45.000 48.000 49.000 49.000 4.000 6.000 1.302 45.226 °C
Temp LM4 44.850 44.850 45.850 46.850 46.850 48.850 50.850 1.000 4.000 0.672 46.430 °C
Temp LM5 44.850 44.850 45.850 46.850 46.850 48.850 50.850 1.000 4.000 0.637 46.454 °C
Temp LM6 52.850 52.850 52.850 54.850 55.850 61.850 66.850 3.000 9.000 1.381 54.718 °C
Temp LM7 44.850 44.850 45.850 46.850 46.850 48.850 50.850 1.000 4.000 0.640 46.468 °C
Temp LM8 40.000 40.000 40.000 41.000 42.000 42.000 42.000 2.000 2.000 0.576 41.108 °C
Temp LM9 38.500 38.500 39.000 39.500 40.500 41.500 44.500 1.500 3.000 0.669 39.528 °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) -178.990 -112.098 -65.431 -1.657 56.434 101.503 182.759 121.865 213.601 39.285 -1.747 µs -4.312 13.46

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) -584.294 -572.715 -535.966 131.684 415.572 484.205 510.565 951.538 1,056.920 284.732 48.432 µs -3.688 9.105

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 -965.304 -872.174 -660.280 84.353 437.348 509.264 555.320 1,097.628 1,381.438 314.898 46.207 µs -4.162 11.95

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 -86.889 -61.962 -44.430 14.895 72.019 90.654 95.641 116.449 152.616 34.240 14.982 µs -1.954 4.894

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:0:1::123 (ntpmon.dcs1.biz)

peer offset 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 2.379 2.426 2.606 2.938 3.504 3.966 4.115 0.898 1.540 0.282 2.969 ms 895.6 8854

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

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

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

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



Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -1.431 -1.211 -0.963 -0.307 0.087 0.281 0.532 1.050 1.492 0.337 -0.370 ms -16.11 53.86

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

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

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

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



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

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 0.838 0.900 1.018 1.477 2.593 2.781 3.029 1.575 1.881 0.527 1.691 ms 17.87 59.01

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) 2.433 4.172 6.770 21.442 84.593 113.113 129.711 77.823 108.941 25.847 32.272 µs 1.97 5.366

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) 3.139 5.054 8.103 23.263 81.531 176.323 219.135 73.428 171.269 28.889 31.745 µs 3.262 16

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 2.550 4.003 6.389 22.116 94.859 138.941 180.493 88.470 134.938 28.703 32.400 µs 2.196 7.669

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 4.761 7.037 10.298 27.742 69.951 135.915 156.001 59.653 128.878 21.582 33.137 µs 3.948 17.24

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:0:1::123 (ntpmon.dcs1.biz)

peer jitter 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 0.000 0.260 0.374 0.831 5.538 6.566 10.595 5.165 6.306 1.661 1.587 ms 2.273 9.748

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.198 0.222 0.283 0.678 1.893 3.112 5.425 1.609 2.890 0.619 0.831 ms 4.577 27.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.



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.159 0.167 0.211 0.573 1.330 2.873 3.452 1.119 2.705 0.440 0.667 ms 4.755 23.98

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 10.768 10.791 10.836 11.024 11.217 11.268 11.325 0.381 0.477 0.117 11.021 ppm 8.159e+05 7.625e+07
Local Clock Time Offset -135.445 -81.555 -52.316 -1.451 51.359 76.911 154.837 103.675 158.466 32.845 -1.287 µs -4.102 11.94
Local RMS Frequency Jitter 6.954 8.034 10.488 17.694 34.818 51.864 60.521 24.330 43.830 8.077 19.532 ppb 9.027 35.1
Local RMS Time Jitter 16.009 17.419 21.687 33.363 51.791 60.704 67.871 30.104 43.285 9.190 34.728 µs 30.42 116.2
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 2.433 4.172 6.770 21.442 84.593 113.113 129.711 77.823 108.941 25.847 32.272 µs 1.97 5.366
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 3.139 5.054 8.103 23.263 81.531 176.323 219.135 73.428 171.269 28.889 31.745 µs 3.262 16
Server Jitter 204.17.205.1 2.550 4.003 6.389 22.116 94.859 138.941 180.493 88.470 134.938 28.703 32.400 µs 2.196 7.669
Server Jitter 204.17.205.30 4.761 7.037 10.298 27.742 69.951 135.915 156.001 59.653 128.878 21.582 33.137 µs 3.948 17.24
Server Jitter 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 0.000 0.260 0.374 0.831 5.538 6.566 10.595 5.165 6.306 1.661 1.587 ms 2.273 9.748
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.198 0.222 0.283 0.678 1.893 3.112 5.425 1.609 2.890 0.619 0.831 ms 4.577 27.65
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.159 0.167 0.211 0.573 1.330 2.873 3.452 1.119 2.705 0.440 0.667 ms 4.755 23.98
Server Offset 2001:470:e815::24 (pi4.rellim.com) -178.990 -112.098 -65.431 -1.657 56.434 101.503 182.759 121.865 213.601 39.285 -1.747 µs -4.312 13.46
Server Offset 2001:470:e815::8 (spidey.rellim.com) -584.294 -572.715 -535.966 131.684 415.572 484.205 510.565 951.538 1,056.920 284.732 48.432 µs -3.688 9.105
Server Offset 204.17.205.1 -965.304 -872.174 -660.280 84.353 437.348 509.264 555.320 1,097.628 1,381.438 314.898 46.207 µs -4.162 11.95
Server Offset 204.17.205.30 -86.889 -61.962 -44.430 14.895 72.019 90.654 95.641 116.449 152.616 34.240 14.982 µs -1.954 4.894
Server Offset 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 2.379 2.426 2.606 2.938 3.504 3.966 4.115 0.898 1.540 0.282 2.969 ms 895.6 8854
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -1.431 -1.211 -0.963 -0.307 0.087 0.281 0.532 1.050 1.492 0.337 -0.370 ms -16.11 53.86
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 0.838 0.900 1.018 1.477 2.593 2.781 3.029 1.575 1.881 0.527 1.691 ms 17.87 59.01
Temp /dev/sda 43.000 43.000 44.000 45.000 48.000 49.000 49.000 4.000 6.000 1.317 45.208 °C
Temp /dev/sdb 32.000 32.000 32.000 33.000 37.000 37.000 37.000 5.000 5.000 1.307 33.486 °C
Temp LM0 49.000 49.000 49.000 54.000 58.000 59.000 59.000 9.000 10.000 2.841 54.139 °C
Temp LM1 72.250 72.250 72.375 72.500 73.375 73.875 81.125 1.000 1.625 0.596 72.701 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM11 57.000 57.000 57.000 58.000 59.000 59.000 59.000 2.000 2.000 0.573 58.240 °C
Temp LM12 7.000 7.000 7.000 8.000 8.000 8.000 9.000 1.000 1.000 0.492 7.622 °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 61.000 61.000 61.000 61.500 62.000 62.500 70.000 1.000 1.500 0.614 61.542 °C
Temp LM15 62.500 62.500 63.000 63.500 64.000 64.000 64.000 1.000 1.500 0.365 63.451 °C
Temp LM16 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °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 72.250 72.250 72.375 72.625 73.375 73.875 81.125 1.000 1.625 0.596 72.701 °C
Temp LM19 62.875 62.875 63.000 63.750 64.250 64.250 64.375 1.250 1.375 0.366 63.604 °C
Temp LM2 69.250 70.750 71.750 72.500 73.250 73.750 80.250 1.500 3.000 0.717 72.454 °C
Temp LM20 32.000 32.000 32.000 33.000 37.000 37.000 37.000 5.000 5.000 1.308 33.559 °C
Temp LM21 62.850 62.850 63.850 65.850 66.850 67.850 67.850 3.000 5.000 1.011 65.649 °C
Temp LM3 43.000 43.000 44.000 45.000 48.000 49.000 49.000 4.000 6.000 1.302 45.226 °C
Temp LM4 44.850 44.850 45.850 46.850 46.850 48.850 50.850 1.000 4.000 0.672 46.430 °C
Temp LM5 44.850 44.850 45.850 46.850 46.850 48.850 50.850 1.000 4.000 0.637 46.454 °C
Temp LM6 52.850 52.850 52.850 54.850 55.850 61.850 66.850 3.000 9.000 1.381 54.718 °C
Temp LM7 44.850 44.850 45.850 46.850 46.850 48.850 50.850 1.000 4.000 0.640 46.468 °C
Temp LM8 40.000 40.000 40.000 41.000 42.000 42.000 42.000 2.000 2.000 0.576 41.108 °C
Temp LM9 38.500 38.500 39.000 39.500 40.500 41.500 44.500 1.500 3.000 0.669 39.528 °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.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of 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".
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 Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
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!