NTPsec

Kong

Report generated: Wed Aug 17 19:49:01 2022 UTC
Start Time: Tue Aug 16 19:49:01 2022 UTC
End Time: Wed Aug 17 19:49:01 2022 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 -100.810 -62.807 -35.543 -0.046 32.916 46.284 59.424 68.459 109.091 21.865 -1.085 µs -4.787 14.17
Local Clock Frequency Offset 11.097 11.136 11.172 11.470 11.829 11.847 11.857 0.657 0.711 0.175 11.422 ppm 2.667e+05 1.717e+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 9.586 10.746 12.134 18.491 28.404 33.307 36.190 16.270 22.561 4.846 19.090 µs 35.01 139.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 3.760 4.302 5.100 9.950 21.253 28.738 35.150 16.153 24.436 4.922 10.983 ppb 7.13 25.34

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 -100.810 -62.807 -35.543 -0.046 32.916 46.284 59.424 68.459 109.091 21.865 -1.085 µs -4.787 14.17

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.097 11.136 11.172 11.470 11.829 11.847 11.857 0.657 0.711 0.175 11.422 ppm 2.667e+05 1.717e+07
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 49.000 49.000 50.000 51.000 52.000 52.000 52.000 2.000 3.000 0.641 50.872 °C
Temp /dev/sdc 36.000 37.000 38.000 39.000 40.000 40.000 40.000 2.000 3.000 0.749 38.740 °C
Temp /dev/sdd 29.000 29.000 29.000 31.000 35.000 36.000 38.000 6.000 7.000 1.592 31.135 °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 43.000 43.000 43.000 44.000 45.000 45.000 45.000 2.000 2.000 0.555 44.024 °C
Temp LM1 42.500 42.500 42.500 43.500 47.500 48.500 48.500 5.000 6.000 1.280 43.967 °C
Temp LM10 74.750 75.000 75.875 77.000 83.125 84.375 84.750 7.250 9.375 2.098 77.744 °C
Temp LM11 64.500 64.500 64.750 65.250 65.750 65.750 66.000 1.000 1.250 0.280 65.135 °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 37.000 37.000 38.000 39.000 40.000 40.000 40.000 2.000 3.000 0.688 38.809 °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 59.000 8.000 10.000 2.816 53.892 °C
Temp LM16 74.625 75.000 75.875 77.000 83.125 84.500 84.750 7.250 9.500 2.098 77.747 °C
Temp LM17 73.750 74.250 75.000 77.000 82.250 84.000 84.250 7.250 9.750 1.934 77.465 °C
Temp LM18 29.000 29.000 29.000 31.000 35.000 36.000 36.000 6.000 7.000 1.520 31.184 °C
Temp LM19 49.000 49.000 50.000 51.000 52.000 52.000 52.000 2.000 3.000 0.623 50.865 °C
Temp LM2 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM3 60.000 60.000 60.000 60.000 61.000 61.000 61.000 1.000 1.000 0.459 60.302 °C
Temp LM4 6.000 6.000 6.000 8.000 8.000 9.000 9.000 2.000 3.000 0.595 7.812 °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 63.500 64.000 64.500 66.000 72.000 73.500 73.500 7.500 9.500 2.093 66.550 °C
Temp LM7 64.500 64.500 64.500 65.000 65.500 65.500 66.000 1.000 1.000 0.309 64.967 °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 -70.480 -37.032 29.708 75.789 89.784 116.943 112.821 160.264 34.430 25.200 µs -1.449 4.76

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) -465.012 -441.703 -396.657 -34.698 171.164 192.942 217.359 567.821 634.645 172.991 -43.606 µs -6.421 17.93

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 -404.178 -371.929 -327.584 -27.120 253.326 278.038 292.057 580.910 649.967 173.779 -35.617 µs -5.412 13.26

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

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

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

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



Server Offset 204.17.205.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 -107.809 -68.952 -26.086 30.899 86.721 111.598 149.667 112.807 180.550 34.932 30.155 µs -0.6144 4.092

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 -135.860 -99.939 -67.011 -14.381 25.109 41.322 63.772 92.120 141.261 27.542 -15.969 µs -9.335 29.61

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 -113.346 -92.385 -51.182 -8.106 35.796 42.954 72.281 86.978 135.339 26.191 -8.857 µs -6.818 20.31

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) 4.375 4.523 4.625 4.970 5.265 5.415 5.496 0.639 0.892 0.194 4.959 ms 1.487e+04 3.667e+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) -866.094 -692.341 -569.159 -335.174 -72.475 83.631 106.962 496.684 775.972 156.012 -328.541 µs -39.21 153.3

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) -639.489 -440.799 87.184 446.284 769.257 988.571 1,378.930 682.073 1,429.370 224.077 427.882 µs 2.763 10.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 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) 2,012.439 2,013.810 2,019.286 2,080.890 2,142.489 2,147.967 2,149.322 123.203 134.157 39.518 2,080.882 s 1.38e+05 7.136e+06

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.234 7.911 21.926 78.026 311.365 393.889 70.115 306.131 39.536 32.933 µs 4.975 38.61

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.384 4.667 6.666 15.264 44.092 68.209 110.162 37.426 63.542 13.217 19.003 µs 3.91 18.33

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 3.291 3.580 5.053 12.879 34.938 70.102 103.778 29.885 66.522 11.647 15.848 µs 4.015 21.59

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 5.891 7.477 10.451 22.866 52.923 82.426 132.586 42.472 74.949 15.311 26.756 µs 4.901 22.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 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 5.475 7.274 9.786 24.078 62.448 137.608 1,250.979 52.662 130.334 85.296 34.181 µs 10.17 133.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.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.325 4.290 6.233 19.994 61.256 83.708 87.626 55.023 79.418 16.174 24.478 µs 3.303 10.92

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.082 0.140 0.216 0.459 1.897 4.720 4.906 1.681 4.580 0.761 0.691 ms 3.299 15.76

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.136 0.142 0.228 0.425 0.847 1.577 3.385 0.619 1.435 0.325 0.494 ms 6.697 53.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 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.101 0.135 0.212 0.449 0.859 2.868 3.128 0.647 2.733 0.353 0.504 ms 6.185 42.51

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) 54.084 55.290 55.537 56.797 57.828 58.045 58.304 2.291 2.754 0.804 56.693 ms 3.367e+05 2.344e+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 11.097 11.136 11.172 11.470 11.829 11.847 11.857 0.657 0.711 0.175 11.422 ppm 2.667e+05 1.717e+07
Local Clock Time Offset -100.810 -62.807 -35.543 -0.046 32.916 46.284 59.424 68.459 109.091 21.865 -1.085 µs -4.787 14.17
Local RMS Frequency Jitter 3.760 4.302 5.100 9.950 21.253 28.738 35.150 16.153 24.436 4.922 10.983 ppb 7.13 25.34
Local RMS Time Jitter 9.586 10.746 12.134 18.491 28.404 33.307 36.190 16.270 22.561 4.846 19.090 µs 35.01 139.6
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 3.460 5.234 7.911 21.926 78.026 311.365 393.889 70.115 306.131 39.536 32.933 µs 4.975 38.61
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 3.384 4.667 6.666 15.264 44.092 68.209 110.162 37.426 63.542 13.217 19.003 µs 3.91 18.33
Server Jitter 204.17.205.1 3.291 3.580 5.053 12.879 34.938 70.102 103.778 29.885 66.522 11.647 15.848 µs 4.015 21.59
Server Jitter 204.17.205.17 5.891 7.477 10.451 22.866 52.923 82.426 132.586 42.472 74.949 15.311 26.756 µs 4.901 22.65
Server Jitter 204.17.205.23 5.475 7.274 9.786 24.078 62.448 137.608 1,250.979 52.662 130.334 85.296 34.181 µs 10.17 133.9
Server Jitter 204.17.205.30 3.325 4.290 6.233 19.994 61.256 83.708 87.626 55.023 79.418 16.174 24.478 µs 3.303 10.92
Server Jitter 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 0.082 0.140 0.216 0.459 1.897 4.720 4.906 1.681 4.580 0.761 0.691 ms 3.299 15.76
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.136 0.142 0.228 0.425 0.847 1.577 3.385 0.619 1.435 0.325 0.494 ms 6.697 53.24
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.101 0.135 0.212 0.449 0.859 2.868 3.128 0.647 2.733 0.353 0.504 ms 6.185 42.51
Server Jitter SHM(2) 54.084 55.290 55.537 56.797 57.828 58.045 58.304 2.291 2.754 0.804 56.693 ms 3.367e+05 2.344e+07
Server Offset 2001:470:e815::24 (pi4.rellim.com) -124.116 -70.480 -37.032 29.708 75.789 89.784 116.943 112.821 160.264 34.430 25.200 µs -1.449 4.76
Server Offset 2001:470:e815::8 (spidey.rellim.com) -465.012 -441.703 -396.657 -34.698 171.164 192.942 217.359 567.821 634.645 172.991 -43.606 µs -6.421 17.93
Server Offset 204.17.205.1 -404.178 -371.929 -327.584 -27.120 253.326 278.038 292.057 580.910 649.967 173.779 -35.617 µs -5.412 13.26
Server Offset 204.17.205.17 -107.809 -68.952 -26.086 30.899 86.721 111.598 149.667 112.807 180.550 34.932 30.155 µs -0.6144 4.092
Server Offset 204.17.205.23 -135.860 -99.939 -67.011 -14.381 25.109 41.322 63.772 92.120 141.261 27.542 -15.969 µs -9.335 29.61
Server Offset 204.17.205.30 -113.346 -92.385 -51.182 -8.106 35.796 42.954 72.281 86.978 135.339 26.191 -8.857 µs -6.818 20.31
Server Offset 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 4.375 4.523 4.625 4.970 5.265 5.415 5.496 0.639 0.892 0.194 4.959 ms 1.487e+04 3.667e+05
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -866.094 -692.341 -569.159 -335.174 -72.475 83.631 106.962 496.684 775.972 156.012 -328.541 µs -39.21 153.3
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -639.489 -440.799 87.184 446.284 769.257 988.571 1,378.930 682.073 1,429.370 224.077 427.882 µs 2.763 10.55
Server Offset SHM(2) 2,012.439 2,013.810 2,019.286 2,080.890 2,142.489 2,147.967 2,149.322 123.203 134.157 39.518 2,080.882 s 1.38e+05 7.136e+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 49.000 49.000 50.000 51.000 52.000 52.000 52.000 2.000 3.000 0.641 50.872 °C
Temp /dev/sdc 36.000 37.000 38.000 39.000 40.000 40.000 40.000 2.000 3.000 0.749 38.740 °C
Temp /dev/sdd 29.000 29.000 29.000 31.000 35.000 36.000 38.000 6.000 7.000 1.592 31.135 °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 43.000 43.000 43.000 44.000 45.000 45.000 45.000 2.000 2.000 0.555 44.024 °C
Temp LM1 42.500 42.500 42.500 43.500 47.500 48.500 48.500 5.000 6.000 1.280 43.967 °C
Temp LM10 74.750 75.000 75.875 77.000 83.125 84.375 84.750 7.250 9.375 2.098 77.744 °C
Temp LM11 64.500 64.500 64.750 65.250 65.750 65.750 66.000 1.000 1.250 0.280 65.135 °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 37.000 37.000 38.000 39.000 40.000 40.000 40.000 2.000 3.000 0.688 38.809 °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 59.000 8.000 10.000 2.816 53.892 °C
Temp LM16 74.625 75.000 75.875 77.000 83.125 84.500 84.750 7.250 9.500 2.098 77.747 °C
Temp LM17 73.750 74.250 75.000 77.000 82.250 84.000 84.250 7.250 9.750 1.934 77.465 °C
Temp LM18 29.000 29.000 29.000 31.000 35.000 36.000 36.000 6.000 7.000 1.520 31.184 °C
Temp LM19 49.000 49.000 50.000 51.000 52.000 52.000 52.000 2.000 3.000 0.623 50.865 °C
Temp LM2 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM3 60.000 60.000 60.000 60.000 61.000 61.000 61.000 1.000 1.000 0.459 60.302 °C
Temp LM4 6.000 6.000 6.000 8.000 8.000 9.000 9.000 2.000 3.000 0.595 7.812 °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 63.500 64.000 64.500 66.000 72.000 73.500 73.500 7.500 9.500 2.093 66.550 °C
Temp LM7 64.500 64.500 64.500 65.000 65.500 65.500 66.000 1.000 1.000 0.309 64.967 °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/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!