NTPsec

Kong

Report generated: Wed May 18 18:49:02 2022 UTC
Start Time: Tue May 17 18:49:01 2022 UTC
End Time: Wed May 18 18: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 -60.243 -39.111 -28.182 -2.396 35.857 69.118 107.592 64.039 108.229 20.341 0.152 µs -2.858 8.75
Local Clock Frequency Offset 9.993 10.013 10.059 10.201 10.376 10.466 10.501 0.318 0.454 0.113 10.215 ppm 7.097e+05 6.332e+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 8.445 9.029 10.302 16.393 26.195 31.300 37.686 15.893 22.271 4.919 17.016 µs 23.2 86.46

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.291 3.908 4.886 8.235 16.509 25.011 43.854 11.623 21.103 4.580 9.276 ppb 7.152 37.95

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 -60.243 -39.111 -28.182 -2.396 35.857 69.118 107.592 64.039 108.229 20.341 0.152 µs -2.858 8.75

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 9.993 10.013 10.059 10.201 10.376 10.466 10.501 0.318 0.454 0.113 10.215 ppm 7.097e+05 6.332e+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 47.000 47.000 47.000 48.000 51.000 52.000 52.000 4.000 5.000 1.156 48.704 °C
Temp /dev/sdc 35.000 35.000 35.000 36.000 39.000 39.000 39.000 4.000 4.000 1.290 36.415 °C
Temp /dev/sdd 25.000 25.000 26.000 27.000 31.000 33.000 33.000 5.000 8.000 2.151 27.889 °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 49.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.885 53.882 °C
Temp LM1 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM2 35.000 35.000 35.000 36.000 39.000 39.000 39.000 4.000 4.000 1.243 36.415 °C
Temp LM3 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM4 78.250 78.250 78.375 78.875 79.125 82.250 82.625 0.750 4.000 0.481 78.850 °C
Temp LM5 69.750 77.000 77.500 78.750 79.500 81.000 84.000 2.000 4.000 0.891 78.655 °C
Temp LM6 25.000 25.000 26.000 27.000 31.000 33.000 33.000 5.000 8.000 2.161 28.014 °C
Temp LM7 47.000 47.000 47.000 48.000 51.000 52.000 52.000 4.000 5.000 1.176 48.697 °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) -98.608 -46.027 -30.290 24.390 70.604 122.104 174.034 100.894 168.131 31.787 23.980 µs -0.4736 5.299

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) -776.804 -721.034 -559.031 41.330 293.630 371.730 412.173 852.661 1,092.764 247.656 -13.136 µs -5.234 15.38

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 -522.634 -377.735 -274.807 25.831 244.284 267.740 311.505 519.091 645.475 165.130 2.905 µs -4.203 10.34

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 -274.215 -118.280 -33.100 29.125 91.640 134.672 153.960 124.740 252.952 44.325 28.594 µs -2.378 12.88

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 -97.460 -73.636 -51.972 -15.361 30.409 65.301 132.227 82.381 138.937 27.136 -13.950 µs -7.138 19.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.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 -60.869 -57.223 -44.500 -6.922 29.738 63.471 70.400 74.238 120.694 23.556 -6.440 µs -5.794 14.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 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.699 -2.502 -2.288 -1.269 0.040 0.268 0.336 2.329 2.770 0.737 -1.179 ms -25.14 85.91

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) 1.392 1.462 1.629 1.880 2.118 2.233 2.389 0.489 0.771 0.146 1.872 ms 1687 2.035e+04

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,144.243 2,145.611 2,151.088 2,212.698 2,274.308 2,279.785 2,281.141 123.220 134.174 39.523 2,212.692 s 1.664e+05 9.159e+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.169 5.603 7.643 21.734 64.749 84.658 90.116 57.106 79.055 17.334 26.628 µs 3.06 8.99

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.256 4.405 6.076 12.992 38.554 60.359 73.227 32.478 55.954 10.633 16.224 µs 3.867 15.19

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.887 3.559 5.001 12.262 34.314 53.865 75.052 29.313 50.306 10.140 15.215 µs 3.683 15.25

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 6.111 8.222 11.758 30.507 76.667 113.336 241.162 64.909 105.114 22.470 35.362 µs 4.537 25.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 4.911 6.719 9.602 21.224 47.435 412.724 466.329 37.833 406.005 50.737 29.656 µs 6.11 48.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.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.839 4.516 6.213 18.193 53.950 65.862 124.243 47.737 61.346 15.364 22.299 µs 3.266 13.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 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.188 0.264 0.418 1.262 5.550 41.280 41.340 5.131 41.015 4.787 2.368 ms 4.769 37.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 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.157 0.182 0.219 0.509 2.534 14.863 16.077 2.315 14.680 1.754 0.880 ms 5.414 45.25

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.003 55.312 55.545 56.673 57.866 58.063 58.319 2.321 2.751 0.806 56.700 ms 3.34e+05 2.318e+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 9.993 10.013 10.059 10.201 10.376 10.466 10.501 0.318 0.454 0.113 10.215 ppm 7.097e+05 6.332e+07
Local Clock Time Offset -60.243 -39.111 -28.182 -2.396 35.857 69.118 107.592 64.039 108.229 20.341 0.152 µs -2.858 8.75
Local RMS Frequency Jitter 3.291 3.908 4.886 8.235 16.509 25.011 43.854 11.623 21.103 4.580 9.276 ppb 7.152 37.95
Local RMS Time Jitter 8.445 9.029 10.302 16.393 26.195 31.300 37.686 15.893 22.271 4.919 17.016 µs 23.2 86.46
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 3.169 5.603 7.643 21.734 64.749 84.658 90.116 57.106 79.055 17.334 26.628 µs 3.06 8.99
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 3.256 4.405 6.076 12.992 38.554 60.359 73.227 32.478 55.954 10.633 16.224 µs 3.867 15.19
Server Jitter 204.17.205.1 2.887 3.559 5.001 12.262 34.314 53.865 75.052 29.313 50.306 10.140 15.215 µs 3.683 15.25
Server Jitter 204.17.205.17 6.111 8.222 11.758 30.507 76.667 113.336 241.162 64.909 105.114 22.470 35.362 µs 4.537 25.65
Server Jitter 204.17.205.23 4.911 6.719 9.602 21.224 47.435 412.724 466.329 37.833 406.005 50.737 29.656 µs 6.11 48.09
Server Jitter 204.17.205.30 3.839 4.516 6.213 18.193 53.950 65.862 124.243 47.737 61.346 15.364 22.299 µs 3.266 13.9
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.188 0.264 0.418 1.262 5.550 41.280 41.340 5.131 41.015 4.787 2.368 ms 4.769 37.55
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.157 0.182 0.219 0.509 2.534 14.863 16.077 2.315 14.680 1.754 0.880 ms 5.414 45.25
Server Jitter SHM(2) 54.003 55.312 55.545 56.673 57.866 58.063 58.319 2.321 2.751 0.806 56.700 ms 3.34e+05 2.318e+07
Server Offset 2001:470:e815::24 (pi4.rellim.com) -98.608 -46.027 -30.290 24.390 70.604 122.104 174.034 100.894 168.131 31.787 23.980 µs -0.4736 5.299
Server Offset 2001:470:e815::8 (spidey.rellim.com) -776.804 -721.034 -559.031 41.330 293.630 371.730 412.173 852.661 1,092.764 247.656 -13.136 µs -5.234 15.38
Server Offset 204.17.205.1 -522.634 -377.735 -274.807 25.831 244.284 267.740 311.505 519.091 645.475 165.130 2.905 µs -4.203 10.34
Server Offset 204.17.205.17 -274.215 -118.280 -33.100 29.125 91.640 134.672 153.960 124.740 252.952 44.325 28.594 µs -2.378 12.88
Server Offset 204.17.205.23 -97.460 -73.636 -51.972 -15.361 30.409 65.301 132.227 82.381 138.937 27.136 -13.950 µs -7.138 19.86
Server Offset 204.17.205.30 -60.869 -57.223 -44.500 -6.922 29.738 63.471 70.400 74.238 120.694 23.556 -6.440 µs -5.794 14.89
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -2.699 -2.502 -2.288 -1.269 0.040 0.268 0.336 2.329 2.770 0.737 -1.179 ms -25.14 85.91
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 1.392 1.462 1.629 1.880 2.118 2.233 2.389 0.489 0.771 0.146 1.872 ms 1687 2.035e+04
Server Offset SHM(2) 2,144.243 2,145.611 2,151.088 2,212.698 2,274.308 2,279.785 2,281.141 123.220 134.174 39.523 2,212.692 s 1.664e+05 9.159e+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 47.000 47.000 47.000 48.000 51.000 52.000 52.000 4.000 5.000 1.156 48.704 °C
Temp /dev/sdc 35.000 35.000 35.000 36.000 39.000 39.000 39.000 4.000 4.000 1.290 36.415 °C
Temp /dev/sdd 25.000 25.000 26.000 27.000 31.000 33.000 33.000 5.000 8.000 2.151 27.889 °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 49.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.885 53.882 °C
Temp LM1 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM2 35.000 35.000 35.000 36.000 39.000 39.000 39.000 4.000 4.000 1.243 36.415 °C
Temp LM3 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM4 78.250 78.250 78.375 78.875 79.125 82.250 82.625 0.750 4.000 0.481 78.850 °C
Temp LM5 69.750 77.000 77.500 78.750 79.500 81.000 84.000 2.000 4.000 0.891 78.655 °C
Temp LM6 25.000 25.000 26.000 27.000 31.000 33.000 33.000 5.000 8.000 2.161 28.014 °C
Temp LM7 47.000 47.000 47.000 48.000 51.000 52.000 52.000 4.000 5.000 1.176 48.697 °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!