NTPsec

Kong

Report generated: Wed Aug 17 13:59:02 2022 UTC
Start Time: Wed Aug 10 13:59:01 2022 UTC
End Time: Wed Aug 17 13:59:01 2022 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 -126.940 -51.543 -35.886 -0.598 36.478 58.593 185.593 72.364 110.136 23.048 -0.317 µs -3.794 12.04
Local Clock Frequency Offset 10.454 10.522 10.654 11.277 11.657 11.836 11.924 1.004 1.313 0.299 11.241 ppm 4.892e+04 1.792e+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 7.328 9.723 11.623 18.261 28.170 34.487 48.903 16.547 24.764 5.135 18.834 µs 27.89 107.6

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 2.962 4.421 5.451 10.153 19.959 33.879 51.490 14.508 29.458 5.218 11.067 ppb 7.34 34.29

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 -126.940 -51.543 -35.886 -0.598 36.478 58.593 185.593 72.364 110.136 23.048 -0.317 µs -3.794 12.04

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.454 10.522 10.654 11.277 11.657 11.836 11.924 1.004 1.313 0.299 11.241 ppm 4.892e+04 1.792e+06
Temp /dev/sda 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp /dev/sdb 44.000 45.000 46.000 50.000 51.000 52.000 52.000 5.000 7.000 1.878 49.227 °C
Temp /dev/sdc 33.000 33.000 34.000 38.000 39.000 40.000 40.000 5.000 7.000 1.847 37.109 °C
Temp /dev/sdd 24.000 24.000 25.000 30.000 33.000 35.000 36.000 8.000 11.000 2.544 29.068 °C
Temp /dev/sde 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM0 40.000 41.000 41.000 44.000 45.000 45.000 45.000 4.000 4.000 1.070 43.324 °C
Temp LM1 39.000 39.500 40.500 43.000 46.000 48.000 51.500 5.500 8.500 1.748 43.117 °C
Temp LM10 72.250 72.875 73.375 76.625 81.625 84.125 86.875 8.250 11.250 2.704 76.728 °C
Temp LM11 62.500 62.750 63.000 64.750 65.500 65.750 66.000 2.500 3.000 0.737 64.557 °C
Temp LM12 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM13 33.000 33.000 34.000 38.000 39.000 40.000 40.000 5.000 7.000 1.889 37.219 °C
Temp LM14 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM15 49.000 49.000 50.000 54.000 58.000 59.000 60.000 8.000 10.000 2.866 53.846 °C
Temp LM16 72.375 72.875 73.375 76.625 81.625 84.125 86.875 8.250 11.250 2.703 76.731 °C
Temp LM17 61.750 72.500 73.000 76.500 81.500 83.250 87.000 8.500 10.750 2.664 76.556 °C
Temp LM18 24.000 24.000 25.000 30.000 33.000 35.000 37.000 8.000 11.000 2.591 29.122 °C
Temp LM19 44.000 45.000 46.000 50.000 51.000 52.000 52.000 5.000 7.000 1.870 49.225 °C
Temp LM2 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.039 25.001 °C
Temp LM3 57.000 57.000 58.000 60.000 61.000 61.000 61.000 3.000 4.000 0.900 59.681 °C
Temp LM4 6.000 6.000 6.000 8.000 9.000 9.000 11.000 3.000 3.000 0.669 7.815 °C
Temp LM5 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM6 61.000 61.500 62.000 65.500 70.500 73.000 75.500 8.500 11.500 2.712 65.535 °C
Temp LM7 62.500 62.500 63.000 64.500 65.500 65.500 66.000 2.500 3.000 0.753 64.420 °C
Temp LM8 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM9 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °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) -124.116 -63.003 -35.945 27.848 75.283 96.089 222.866 111.228 159.092 34.061 25.045 µs -1.118 4.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) -542.386 -443.272 -302.845 9.353 205.059 285.634 423.695 507.904 728.906 157.623 -13.083 µs -5.176 14.59

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 -591.593 -491.952 -360.607 -14.600 268.580 392.121 546.472 629.187 884.073 186.386 -20.544 µs -4.892 12.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 204.17.205.17

peer offset 204.17.205.17 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.17 -117.271 -50.390 -24.305 30.069 86.241 112.633 160.129 110.546 163.023 33.953 30.727 µs -0.2801 3.542

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.23

peer offset 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.23 -148.472 -85.355 -60.789 -16.034 29.256 56.609 165.720 90.045 141.964 28.639 -15.808 µs -8.156 23.74

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 -159.390 -79.369 -49.343 -5.668 38.665 63.670 140.941 88.008 143.039 28.429 -6.233 µs -5.716 18.22

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) 3.621 4.405 4.583 4.932 5.250 5.410 5.845 0.667 1.005 0.207 4.924 ms 1.199e+04 2.754e+05

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,296.288 -886.331 -644.162 -338.783 -63.925 98.289 393.058 580.237 984.620 182.390 -343.584 µs -33.08 129

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) -3.226 -1.953 -0.542 0.469 1.034 1.453 1.694 1.576 3.406 0.515 0.410 ms -3.439 20.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 SHM(2)

peer offset SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(2) 1,157.795 1,167.379 1,205.706 1,636.932 2,068.151 2,106.480 2,116.049 862.444 939.102 276.628 1,636.923 s 133.7 731.6

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

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

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

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



Server 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) 3.460 5.289 7.753 22.031 74.494 101.605 778.064 66.741 96.316 37.781 30.651 µs 9.964 154.9

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:e815::8 (spidey.rellim.com)

peer jitter 2001:470:e815::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 2.740 4.290 6.103 14.767 43.348 70.386 858.994 37.245 66.096 22.201 18.764 µs 25 927.9

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.222 3.756 5.071 13.696 39.807 68.848 123.897 34.736 65.092 12.486 17.126 µs 3.51 16.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 204.17.205.17

peer jitter 204.17.205.17 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.17 3.872 7.379 10.329 24.487 57.014 85.652 995.585 46.685 78.273 38.002 29.316 µs 19.12 455.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.



Server Jitter 204.17.205.23

peer jitter 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.23 3.465 6.377 9.074 22.269 49.434 81.572 1,250.979 40.360 75.195 39.586 26.729 µs 19.62 515.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 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 2.498 4.721 7.360 19.371 54.145 75.481 136.843 46.785 70.760 15.556 23.524 µs 3.367 12.55

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.061 0.163 0.242 0.525 1.405 4.687 8.549 1.163 4.523 0.651 0.675 ms 5.761 47.45

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.095 0.151 0.222 0.452 1.016 1.714 5.990 0.794 1.563 0.398 0.532 ms 8.308 98.93

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.057 0.149 0.217 0.469 1.038 2.092 16.528 0.821 1.943 0.643 0.556 ms 16.76 391.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.



Server Jitter SHM(2)

peer jitter SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(2) 53.972 55.282 55.524 56.766 57.842 58.067 59.677 2.319 2.785 0.807 56.693 ms 3.319e+05 2.299e+07

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.454 10.522 10.654 11.277 11.657 11.836 11.924 1.004 1.313 0.299 11.241 ppm 4.892e+04 1.792e+06
Local Clock Time Offset -126.940 -51.543 -35.886 -0.598 36.478 58.593 185.593 72.364 110.136 23.048 -0.317 µs -3.794 12.04
Local RMS Frequency Jitter 2.962 4.421 5.451 10.153 19.959 33.879 51.490 14.508 29.458 5.218 11.067 ppb 7.34 34.29
Local RMS Time Jitter 7.328 9.723 11.623 18.261 28.170 34.487 48.903 16.547 24.764 5.135 18.834 µs 27.89 107.6
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 3.460 5.289 7.753 22.031 74.494 101.605 778.064 66.741 96.316 37.781 30.651 µs 9.964 154.9
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 2.740 4.290 6.103 14.767 43.348 70.386 858.994 37.245 66.096 22.201 18.764 µs 25 927.9
Server Jitter 204.17.205.1 2.222 3.756 5.071 13.696 39.807 68.848 123.897 34.736 65.092 12.486 17.126 µs 3.51 16.09
Server Jitter 204.17.205.17 3.872 7.379 10.329 24.487 57.014 85.652 995.585 46.685 78.273 38.002 29.316 µs 19.12 455.8
Server Jitter 204.17.205.23 3.465 6.377 9.074 22.269 49.434 81.572 1,250.979 40.360 75.195 39.586 26.729 µs 19.62 515.3
Server Jitter 204.17.205.30 2.498 4.721 7.360 19.371 54.145 75.481 136.843 46.785 70.760 15.556 23.524 µs 3.367 12.55
Server Jitter 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 0.061 0.163 0.242 0.525 1.405 4.687 8.549 1.163 4.523 0.651 0.675 ms 5.761 47.45
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.095 0.151 0.222 0.452 1.016 1.714 5.990 0.794 1.563 0.398 0.532 ms 8.308 98.93
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.057 0.149 0.217 0.469 1.038 2.092 16.528 0.821 1.943 0.643 0.556 ms 16.76 391.8
Server Jitter SHM(2) 53.972 55.282 55.524 56.766 57.842 58.067 59.677 2.319 2.785 0.807 56.693 ms 3.319e+05 2.299e+07
Server Offset 2001:470:e815::24 (pi4.rellim.com) -124.116 -63.003 -35.945 27.848 75.283 96.089 222.866 111.228 159.092 34.061 25.045 µs -1.118 4.55
Server Offset 2001:470:e815::8 (spidey.rellim.com) -542.386 -443.272 -302.845 9.353 205.059 285.634 423.695 507.904 728.906 157.623 -13.083 µs -5.176 14.59
Server Offset 204.17.205.1 -591.593 -491.952 -360.607 -14.600 268.580 392.121 546.472 629.187 884.073 186.386 -20.544 µs -4.892 12.86
Server Offset 204.17.205.17 -117.271 -50.390 -24.305 30.069 86.241 112.633 160.129 110.546 163.023 33.953 30.727 µs -0.2801 3.542
Server Offset 204.17.205.23 -148.472 -85.355 -60.789 -16.034 29.256 56.609 165.720 90.045 141.964 28.639 -15.808 µs -8.156 23.74
Server Offset 204.17.205.30 -159.390 -79.369 -49.343 -5.668 38.665 63.670 140.941 88.008 143.039 28.429 -6.233 µs -5.716 18.22
Server Offset 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 3.621 4.405 4.583 4.932 5.250 5.410 5.845 0.667 1.005 0.207 4.924 ms 1.199e+04 2.754e+05
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -1,296.288 -886.331 -644.162 -338.783 -63.925 98.289 393.058 580.237 984.620 182.390 -343.584 µs -33.08 129
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -3.226 -1.953 -0.542 0.469 1.034 1.453 1.694 1.576 3.406 0.515 0.410 ms -3.439 20.89
Server Offset SHM(2) 1,157.795 1,167.379 1,205.706 1,636.932 2,068.151 2,106.480 2,116.049 862.444 939.102 276.628 1,636.923 s 133.7 731.6
Temp /dev/sda 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp /dev/sdb 44.000 45.000 46.000 50.000 51.000 52.000 52.000 5.000 7.000 1.878 49.227 °C
Temp /dev/sdc 33.000 33.000 34.000 38.000 39.000 40.000 40.000 5.000 7.000 1.847 37.109 °C
Temp /dev/sdd 24.000 24.000 25.000 30.000 33.000 35.000 36.000 8.000 11.000 2.544 29.068 °C
Temp /dev/sde 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM0 40.000 41.000 41.000 44.000 45.000 45.000 45.000 4.000 4.000 1.070 43.324 °C
Temp LM1 39.000 39.500 40.500 43.000 46.000 48.000 51.500 5.500 8.500 1.748 43.117 °C
Temp LM10 72.250 72.875 73.375 76.625 81.625 84.125 86.875 8.250 11.250 2.704 76.728 °C
Temp LM11 62.500 62.750 63.000 64.750 65.500 65.750 66.000 2.500 3.000 0.737 64.557 °C
Temp LM12 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM13 33.000 33.000 34.000 38.000 39.000 40.000 40.000 5.000 7.000 1.889 37.219 °C
Temp LM14 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM15 49.000 49.000 50.000 54.000 58.000 59.000 60.000 8.000 10.000 2.866 53.846 °C
Temp LM16 72.375 72.875 73.375 76.625 81.625 84.125 86.875 8.250 11.250 2.703 76.731 °C
Temp LM17 61.750 72.500 73.000 76.500 81.500 83.250 87.000 8.500 10.750 2.664 76.556 °C
Temp LM18 24.000 24.000 25.000 30.000 33.000 35.000 37.000 8.000 11.000 2.591 29.122 °C
Temp LM19 44.000 45.000 46.000 50.000 51.000 52.000 52.000 5.000 7.000 1.870 49.225 °C
Temp LM2 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.039 25.001 °C
Temp LM3 57.000 57.000 58.000 60.000 61.000 61.000 61.000 3.000 4.000 0.900 59.681 °C
Temp LM4 6.000 6.000 6.000 8.000 9.000 9.000 11.000 3.000 3.000 0.669 7.815 °C
Temp LM5 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM6 61.000 61.500 62.000 65.500 70.500 73.000 75.500 8.500 11.500 2.712 65.535 °C
Temp LM7 62.500 62.500 63.000 64.500 65.500 65.500 66.000 2.500 3.000 0.753 64.420 °C
Temp LM8 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM9 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °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!