NTPsec

Kong

Report generated: Sat Jul 2 04:49:01 2022 UTC
Start Time: Fri Jul 1 04:49:01 2022 UTC
End Time: Sat Jul 2 04: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 -102.084 -69.230 -41.303 -3.089 39.015 68.380 81.469 80.318 137.610 24.608 -1.779 µs -4.487 12.93
Local Clock Frequency Offset 9.806 9.852 9.905 10.354 10.604 10.825 10.922 0.699 0.974 0.211 10.308 ppm 1.098e+05 5.263e+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 9.138 9.769 10.937 17.895 29.122 35.413 42.421 18.185 25.644 5.404 18.616 µs 22.87 84.92

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.438 4.499 5.551 9.763 26.646 33.903 39.632 21.095 29.404 6.016 11.410 ppb 5.442 20.36

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 -102.084 -69.230 -41.303 -3.089 39.015 68.380 81.469 80.318 137.610 24.608 -1.779 µs -4.487 12.93

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.806 9.852 9.905 10.354 10.604 10.825 10.922 0.699 0.974 0.211 10.308 ppm 1.098e+05 5.263e+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 46.000 46.000 46.000 49.000 49.000 49.000 50.000 3.000 3.000 0.974 48.288 °C
Temp /dev/sdc 33.000 33.000 34.000 36.000 37.000 37.000 38.000 3.000 4.000 0.976 35.611 °C
Temp /dev/sdd 24.000 24.000 25.000 27.000 31.000 32.000 32.000 6.000 8.000 1.705 26.976 °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 39.000 39.000 40.000 42.000 42.000 43.000 43.000 2.000 4.000 0.845 41.535 °C
Temp LM1 38.000 38.000 38.500 40.000 41.500 45.000 45.500 3.000 7.000 1.141 40.163 °C
Temp LM10 76.500 76.500 76.625 77.875 78.625 84.500 84.875 2.000 8.000 1.116 77.927 °C
Temp LM11 61.500 61.500 61.750 62.750 63.500 63.750 63.750 1.750 2.250 0.566 62.661 °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 36.000 37.000 37.000 37.000 3.000 4.000 0.952 35.653 °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.731 53.972 °C
Temp LM16 76.500 76.500 76.625 77.875 78.625 84.250 84.875 2.000 7.750 1.107 77.931 °C
Temp LM17 75.500 76.000 76.500 78.000 79.250 83.750 85.750 2.750 7.750 1.117 77.957 °C
Temp LM18 24.000 24.000 25.000 27.000 31.000 32.000 32.000 6.000 8.000 1.759 27.042 °C
Temp LM19 46.000 46.000 46.000 49.000 49.000 50.000 50.000 3.000 4.000 0.980 48.299 °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 56.000 56.000 56.000 58.000 58.000 59.000 59.000 2.000 3.000 0.780 57.399 °C
Temp LM4 5.000 6.000 6.000 7.000 7.000 8.000 9.000 1.000 2.000 0.548 6.760 °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 65.500 65.500 65.500 66.500 67.500 72.500 73.500 2.000 7.000 1.090 66.720 °C
Temp LM7 61.500 61.500 61.500 62.500 63.500 63.500 63.500 2.000 2.000 0.569 62.498 °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) -112.659 -83.871 -36.609 22.438 74.071 128.258 151.836 110.680 212.129 35.938 21.170 µs -1.387 5.908

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) -664.726 -614.647 -570.947 75.778 458.512 498.099 509.926 1,029.459 1,112.746 316.311 -4.472 µs -4.518 11.13

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 -564.357 -533.592 -494.449 5.242 557.754 627.184 656.558 1,052.203 1,160.776 290.644 -9.283 µs -4.078 9.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.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 -126.815 -70.065 -30.365 25.915 78.479 103.856 114.319 108.844 173.921 33.965 25.435 µs -1.075 4.557

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 -127.165 -92.360 -73.973 -18.695 34.042 76.947 112.900 108.015 169.307 33.569 -17.982 µs -8.055 22.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 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 -153.137 -87.011 -46.040 -5.831 39.513 78.438 90.907 85.553 165.449 27.954 -5.855 µs -5.81 19.69

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,110.844 -988.259 -880.743 -501.966 -148.828 157.465 251.913 731.915 1,145.724 221.420 -506.396 µs -45.07 181.1

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) 1.139 1.307 1.550 1.817 2.134 2.269 2.577 0.585 0.962 0.183 1.824 ms 742.4 6885

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) 150.227 151.596 157.071 218.679 280.284 285.761 287.119 123.213 134.165 39.520 218.672 s 106.8 547.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 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) 4.851 6.243 8.583 21.273 65.500 104.910 415.443 56.917 98.667 28.242 28.670 µs 7.181 84.84

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.535 5.347 7.378 15.085 36.198 53.765 66.472 28.820 48.418 9.165 17.370 µs 5.23 19.64

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.455 3.698 5.329 13.810 34.901 45.741 59.722 29.572 42.043 9.287 15.929 µs 3.905 12.85

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 4.493 7.467 10.686 23.056 49.657 69.706 181.320 38.971 62.239 14.729 26.328 µs 5.798 37.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 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.107 6.438 8.762 23.322 60.542 74.950 100.404 51.780 68.512 15.695 27.349 µs 3.985 12.47

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.223 5.532 7.473 19.584 51.393 69.111 96.153 43.920 63.579 13.961 23.203 µs 4.008 14.64

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.123 0.193 0.297 0.718 2.297 3.439 3.895 2.000 3.246 0.673 0.952 ms 3.072 10.21

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.112 0.129 0.227 0.478 1.266 2.218 7.375 1.039 2.090 0.524 0.579 ms 8.655 103.7

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) 51.599 55.290 55.540 56.707 57.844 58.077 59.084 2.304 2.787 0.809 56.697 ms 3.301e+05 2.282e+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.806 9.852 9.905 10.354 10.604 10.825 10.922 0.699 0.974 0.211 10.308 ppm 1.098e+05 5.263e+06
Local Clock Time Offset -102.084 -69.230 -41.303 -3.089 39.015 68.380 81.469 80.318 137.610 24.608 -1.779 µs -4.487 12.93
Local RMS Frequency Jitter 3.438 4.499 5.551 9.763 26.646 33.903 39.632 21.095 29.404 6.016 11.410 ppb 5.442 20.36
Local RMS Time Jitter 9.138 9.769 10.937 17.895 29.122 35.413 42.421 18.185 25.644 5.404 18.616 µs 22.87 84.92
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 4.851 6.243 8.583 21.273 65.500 104.910 415.443 56.917 98.667 28.242 28.670 µs 7.181 84.84
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 2.535 5.347 7.378 15.085 36.198 53.765 66.472 28.820 48.418 9.165 17.370 µs 5.23 19.64
Server Jitter 204.17.205.1 2.455 3.698 5.329 13.810 34.901 45.741 59.722 29.572 42.043 9.287 15.929 µs 3.905 12.85
Server Jitter 204.17.205.17 4.493 7.467 10.686 23.056 49.657 69.706 181.320 38.971 62.239 14.729 26.328 µs 5.798 37.77
Server Jitter 204.17.205.23 5.107 6.438 8.762 23.322 60.542 74.950 100.404 51.780 68.512 15.695 27.349 µs 3.985 12.47
Server Jitter 204.17.205.30 3.223 5.532 7.473 19.584 51.393 69.111 96.153 43.920 63.579 13.961 23.203 µs 4.008 14.64
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.123 0.193 0.297 0.718 2.297 3.439 3.895 2.000 3.246 0.673 0.952 ms 3.072 10.21
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.112 0.129 0.227 0.478 1.266 2.218 7.375 1.039 2.090 0.524 0.579 ms 8.655 103.7
Server Jitter SHM(2) 51.599 55.290 55.540 56.707 57.844 58.077 59.084 2.304 2.787 0.809 56.697 ms 3.301e+05 2.282e+07
Server Offset 2001:470:e815::24 (pi4.rellim.com) -112.659 -83.871 -36.609 22.438 74.071 128.258 151.836 110.680 212.129 35.938 21.170 µs -1.387 5.908
Server Offset 2001:470:e815::8 (spidey.rellim.com) -664.726 -614.647 -570.947 75.778 458.512 498.099 509.926 1,029.459 1,112.746 316.311 -4.472 µs -4.518 11.13
Server Offset 204.17.205.1 -564.357 -533.592 -494.449 5.242 557.754 627.184 656.558 1,052.203 1,160.776 290.644 -9.283 µs -4.078 9.59
Server Offset 204.17.205.17 -126.815 -70.065 -30.365 25.915 78.479 103.856 114.319 108.844 173.921 33.965 25.435 µs -1.075 4.557
Server Offset 204.17.205.23 -127.165 -92.360 -73.973 -18.695 34.042 76.947 112.900 108.015 169.307 33.569 -17.982 µs -8.055 22.6
Server Offset 204.17.205.30 -153.137 -87.011 -46.040 -5.831 39.513 78.438 90.907 85.553 165.449 27.954 -5.855 µs -5.81 19.69
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -1,110.844 -988.259 -880.743 -501.966 -148.828 157.465 251.913 731.915 1,145.724 221.420 -506.396 µs -45.07 181.1
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 1.139 1.307 1.550 1.817 2.134 2.269 2.577 0.585 0.962 0.183 1.824 ms 742.4 6885
Server Offset SHM(2) 150.227 151.596 157.071 218.679 280.284 285.761 287.119 123.213 134.165 39.520 218.672 s 106.8 547.4
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 46.000 46.000 46.000 49.000 49.000 49.000 50.000 3.000 3.000 0.974 48.288 °C
Temp /dev/sdc 33.000 33.000 34.000 36.000 37.000 37.000 38.000 3.000 4.000 0.976 35.611 °C
Temp /dev/sdd 24.000 24.000 25.000 27.000 31.000 32.000 32.000 6.000 8.000 1.705 26.976 °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 39.000 39.000 40.000 42.000 42.000 43.000 43.000 2.000 4.000 0.845 41.535 °C
Temp LM1 38.000 38.000 38.500 40.000 41.500 45.000 45.500 3.000 7.000 1.141 40.163 °C
Temp LM10 76.500 76.500 76.625 77.875 78.625 84.500 84.875 2.000 8.000 1.116 77.927 °C
Temp LM11 61.500 61.500 61.750 62.750 63.500 63.750 63.750 1.750 2.250 0.566 62.661 °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 36.000 37.000 37.000 37.000 3.000 4.000 0.952 35.653 °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.731 53.972 °C
Temp LM16 76.500 76.500 76.625 77.875 78.625 84.250 84.875 2.000 7.750 1.107 77.931 °C
Temp LM17 75.500 76.000 76.500 78.000 79.250 83.750 85.750 2.750 7.750 1.117 77.957 °C
Temp LM18 24.000 24.000 25.000 27.000 31.000 32.000 32.000 6.000 8.000 1.759 27.042 °C
Temp LM19 46.000 46.000 46.000 49.000 49.000 50.000 50.000 3.000 4.000 0.980 48.299 °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 56.000 56.000 56.000 58.000 58.000 59.000 59.000 2.000 3.000 0.780 57.399 °C
Temp LM4 5.000 6.000 6.000 7.000 7.000 8.000 9.000 1.000 2.000 0.548 6.760 °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 65.500 65.500 65.500 66.500 67.500 72.500 73.500 2.000 7.000 1.090 66.720 °C
Temp LM7 61.500 61.500 61.500 62.500 63.500 63.500 63.500 2.000 2.000 0.569 62.498 °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!