NTPsec

Kong

Report generated: Sat Apr 1 13:59:02 2023 UTC
Start Time: Sat Mar 25 13:59:01 2023 UTC
End Time: Sat Apr 1 13:59:01 2023 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 -234.708 -105.640 -61.518 -1.942 57.384 105.735 261.343 118.902 211.375 39.599 -1.544 µs -3.986 14.12
Local Clock Frequency Offset 10.599 10.665 10.820 11.138 11.466 12.208 12.364 0.647 1.543 0.266 11.159 ppm 6.884e+04 2.825e+06

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 15.243 18.888 22.442 38.066 63.845 79.881 105.872 41.403 60.993 12.739 39.786 µs 16.97 60.95

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.375 8.617 11.022 19.717 44.542 71.704 110.450 33.520 63.087 11.713 22.479 ppb 6.099 27.93

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 -234.708 -105.640 -61.518 -1.942 57.384 105.735 261.343 118.902 211.375 39.599 -1.544 µs -3.986 14.12

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.599 10.665 10.820 11.138 11.466 12.208 12.364 0.647 1.543 0.266 11.159 ppm 6.884e+04 2.825e+06
Temp /dev/sda 43.000 43.000 44.000 45.000 48.000 49.000 51.000 4.000 6.000 1.234 45.491 °C
Temp /dev/sdb 31.000 32.000 32.000 34.000 36.000 37.000 38.000 4.000 5.000 1.116 33.673 °C
Temp LM0 48.000 49.000 49.000 54.000 58.000 59.000 59.000 9.000 10.000 2.860 53.931 °C
Temp LM1 72.125 72.250 72.375 73.000 74.375 84.375 86.250 2.000 12.125 2.123 73.481 °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 59.000 60.000 60.000 60.000 3.000 3.000 0.796 58.738 °C
Temp LM12 5.000 7.000 7.000 8.000 8.000 9.000 9.000 1.000 2.000 0.487 7.808 °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 62.000 63.000 73.000 75.000 2.000 12.000 2.136 62.298 °C
Temp LM15 62.500 62.500 63.000 64.000 65.000 65.000 65.500 2.000 2.500 0.593 63.847 °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.000 72.250 72.375 73.000 74.375 84.375 86.250 2.000 12.125 2.125 73.480 °C
Temp LM19 62.625 62.750 63.000 64.000 65.000 65.250 65.500 2.000 2.500 0.573 63.990 °C
Temp LM2 67.250 71.500 71.750 72.750 74.500 84.000 86.000 2.750 12.500 2.063 73.249 °C
Temp LM20 31.000 32.000 32.000 34.000 36.000 37.000 38.000 4.000 5.000 1.123 33.769 °C
Temp LM21 62.850 62.850 63.850 65.850 67.850 67.850 68.850 4.000 5.000 1.191 65.934 °C
Temp LM3 43.000 43.000 44.000 45.000 48.000 49.000 51.000 4.000 6.000 1.236 45.495 °C
Temp LM4 44.850 44.850 45.850 46.850 48.850 49.850 50.850 3.000 5.000 0.928 46.944 °C
Temp LM5 44.850 44.850 45.850 46.850 48.850 49.850 50.850 3.000 5.000 0.917 46.949 °C
Temp LM6 51.850 52.850 53.850 54.850 57.850 61.850 67.850 4.000 9.000 1.604 55.264 °C
Temp LM7 44.850 44.850 45.850 46.850 48.850 49.850 50.850 3.000 5.000 0.928 46.951 °C
Temp LM8 40.000 40.000 40.000 42.000 43.000 43.000 43.000 3.000 3.000 0.810 41.627 °C
Temp LM9 38.000 38.500 39.000 40.000 42.000 49.000 51.000 3.000 10.500 1.794 40.295 °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) -253.634 -114.265 -72.099 -2.038 70.642 128.386 296.284 142.741 242.651 46.204 -1.205 µs -3.775 12.55

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) -1.682 -1.180 -0.659 0.137 0.534 0.784 0.982 1.192 1.964 0.398 0.046 ms -4.507 14.44

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.727 -1.354 -0.795 0.114 0.492 0.668 0.999 1.286 2.021 0.393 0.037 ms -5.083 17.89

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 -192.088 -82.177 -44.679 13.355 76.836 123.996 208.976 121.515 206.173 38.745 14.469 µs -1.972 6.874

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.280 2.968 ms 911 9054

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) -2.353 -1.817 -1.387 -0.863 -0.102 0.110 0.532 1.285 1.927 0.402 -0.817 ms -36.89 141.4

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.018 0.367 0.913 1.418 2.454 2.695 3.046 1.541 2.328 0.549 1.594 ms 12.78 38.44

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.732 6.909 22.088 90.452 128.065 622.167 83.543 123.333 29.705 32.833 µs 3.734 44.96

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.000 5.809 8.241 22.371 96.784 152.016 219.135 88.543 146.207 29.732 32.820 µs 2.631 10.52

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.347 3.903 5.937 22.100 103.302 156.821 211.674 97.365 152.918 31.970 33.701 µs 2.162 7.903

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 3.129 6.593 10.094 30.936 79.342 120.311 167.872 69.248 113.718 23.461 36.583 µs 3.374 11.77

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.827 5.538 6.566 10.595 5.165 6.306 1.655 1.568 ms 2.268 9.784

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.108 0.211 0.288 0.656 2.150 4.572 55.647 1.861 4.361 1.450 0.884 ms 25.79 952.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 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.122 0.175 0.256 0.566 1.388 3.452 34.886 1.131 3.277 1.156 0.720 ms 19.74 528.8

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.599 10.665 10.820 11.138 11.466 12.208 12.364 0.647 1.543 0.266 11.159 ppm 6.884e+04 2.825e+06
Local Clock Time Offset -234.708 -105.640 -61.518 -1.942 57.384 105.735 261.343 118.902 211.375 39.599 -1.544 µs -3.986 14.12
Local RMS Frequency Jitter 6.375 8.617 11.022 19.717 44.542 71.704 110.450 33.520 63.087 11.713 22.479 ppb 6.099 27.93
Local RMS Time Jitter 15.243 18.888 22.442 38.066 63.845 79.881 105.872 41.403 60.993 12.739 39.786 µs 16.97 60.95
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 2.433 4.732 6.909 22.088 90.452 128.065 622.167 83.543 123.333 29.705 32.833 µs 3.734 44.96
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 3.000 5.809 8.241 22.371 96.784 152.016 219.135 88.543 146.207 29.732 32.820 µs 2.631 10.52
Server Jitter 204.17.205.1 2.347 3.903 5.937 22.100 103.302 156.821 211.674 97.365 152.918 31.970 33.701 µs 2.162 7.903
Server Jitter 204.17.205.30 3.129 6.593 10.094 30.936 79.342 120.311 167.872 69.248 113.718 23.461 36.583 µs 3.374 11.77
Server Jitter 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 0.000 0.260 0.374 0.827 5.538 6.566 10.595 5.165 6.306 1.655 1.568 ms 2.268 9.784
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.108 0.211 0.288 0.656 2.150 4.572 55.647 1.861 4.361 1.450 0.884 ms 25.79 952.5
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.122 0.175 0.256 0.566 1.388 3.452 34.886 1.131 3.277 1.156 0.720 ms 19.74 528.8
Server Offset 2001:470:e815::24 (pi4.rellim.com) -253.634 -114.265 -72.099 -2.038 70.642 128.386 296.284 142.741 242.651 46.204 -1.205 µs -3.775 12.55
Server Offset 2001:470:e815::8 (spidey.rellim.com) -1.682 -1.180 -0.659 0.137 0.534 0.784 0.982 1.192 1.964 0.398 0.046 ms -4.507 14.44
Server Offset 204.17.205.1 -1.727 -1.354 -0.795 0.114 0.492 0.668 0.999 1.286 2.021 0.393 0.037 ms -5.083 17.89
Server Offset 204.17.205.30 -192.088 -82.177 -44.679 13.355 76.836 123.996 208.976 121.515 206.173 38.745 14.469 µs -1.972 6.874
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.280 2.968 ms 911 9054
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -2.353 -1.817 -1.387 -0.863 -0.102 0.110 0.532 1.285 1.927 0.402 -0.817 ms -36.89 141.4
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -0.018 0.367 0.913 1.418 2.454 2.695 3.046 1.541 2.328 0.549 1.594 ms 12.78 38.44
Temp /dev/sda 43.000 43.000 44.000 45.000 48.000 49.000 51.000 4.000 6.000 1.234 45.491 °C
Temp /dev/sdb 31.000 32.000 32.000 34.000 36.000 37.000 38.000 4.000 5.000 1.116 33.673 °C
Temp LM0 48.000 49.000 49.000 54.000 58.000 59.000 59.000 9.000 10.000 2.860 53.931 °C
Temp LM1 72.125 72.250 72.375 73.000 74.375 84.375 86.250 2.000 12.125 2.123 73.481 °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 59.000 60.000 60.000 60.000 3.000 3.000 0.796 58.738 °C
Temp LM12 5.000 7.000 7.000 8.000 8.000 9.000 9.000 1.000 2.000 0.487 7.808 °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 62.000 63.000 73.000 75.000 2.000 12.000 2.136 62.298 °C
Temp LM15 62.500 62.500 63.000 64.000 65.000 65.000 65.500 2.000 2.500 0.593 63.847 °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.000 72.250 72.375 73.000 74.375 84.375 86.250 2.000 12.125 2.125 73.480 °C
Temp LM19 62.625 62.750 63.000 64.000 65.000 65.250 65.500 2.000 2.500 0.573 63.990 °C
Temp LM2 67.250 71.500 71.750 72.750 74.500 84.000 86.000 2.750 12.500 2.063 73.249 °C
Temp LM20 31.000 32.000 32.000 34.000 36.000 37.000 38.000 4.000 5.000 1.123 33.769 °C
Temp LM21 62.850 62.850 63.850 65.850 67.850 67.850 68.850 4.000 5.000 1.191 65.934 °C
Temp LM3 43.000 43.000 44.000 45.000 48.000 49.000 51.000 4.000 6.000 1.236 45.495 °C
Temp LM4 44.850 44.850 45.850 46.850 48.850 49.850 50.850 3.000 5.000 0.928 46.944 °C
Temp LM5 44.850 44.850 45.850 46.850 48.850 49.850 50.850 3.000 5.000 0.917 46.949 °C
Temp LM6 51.850 52.850 53.850 54.850 57.850 61.850 67.850 4.000 9.000 1.604 55.264 °C
Temp LM7 44.850 44.850 45.850 46.850 48.850 49.850 50.850 3.000 5.000 0.928 46.951 °C
Temp LM8 40.000 40.000 40.000 42.000 43.000 43.000 43.000 3.000 3.000 0.810 41.627 °C
Temp LM9 38.000 38.500 39.000 40.000 42.000 49.000 51.000 3.000 10.500 1.794 40.295 °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.
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!