NTPsec

B-ntpsec-1-hour-stats

Report generated: Wed Oct 23 21:02:23 2019 UTC
Start Time: Wed Oct 23 20:01:53 2019 UTC
End Time: Wed Oct 23 21:02:21 2019 UTC
Report published: Wed Oct 23 14:02:38 2019 PDT
Report Period: 0.0 days

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 -592.000 -550.000 -428.000 -44.000 334.000 459.000 530.000 762.000 1,009.000 219.474 -42.769 ns -5.224 13.03
Local Clock Frequency Offset -5.701 -5.701 -5.700 -5.698 -5.697 -5.697 -5.697 0.0038 0.0042 0.0011 -5.698 ppm -1.243e+11 6.204e+14

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 101.000 115.000 155.000 238.000 307.000 328.000 336.000 152.000 213.000 46.909 235.044 ns 76.23 352.9

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 28.000 30.000 33.000 54.000 78.000 83.000 88.000 45.000 53.000 12.443 53.911 10e-12 47.23 195.8

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 -592.000 -550.000 -428.000 -44.000 334.000 459.000 530.000 762.000 1,009.000 219.474 -42.769 ns -5.224 13.03

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 -5.701 -5.701 -5.700 -5.698 -5.697 -5.697 -5.697 0.0038 0.0042 0.0011 -5.698 ppm -1.243e+11 6.204e+14
Temp ZONE0 59.072 59.072 59.072 60.148 60.148 60.148 60.148 1.076 1.076 0.331 59.843 °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.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 8.000 8.000 9.000 10.000 11.000 11.000 11.000 2.000 3.000 0.726 10.150 nSat 2223 2.933e+04
TDOP 0.590 0.590 0.600 0.720 1.000 1.180 1.180 0.400 0.590 0.142 0.740 87.59 436.6

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



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 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 2.864 2.864 2.864 3.266 3.664 3.664 3.664 0.800 0.800 0.318 3.181 ms 754.9 7047

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 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 1.792 1.792 1.792 2.370 2.851 2.851 2.851 1.060 1.060 0.272 2.321 ms 449.6 3555

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 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 6.501 6.501 6.501 6.661 8.894 8.894 8.894 2.392 2.392 1.092 7.352 ms 206.1 1293

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 192.168.1.10

peer offset 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.10 -60.195 -60.195 30.241 132.039 203.721 243.633 243.633 173.480 303.828 59.841 128.007 µs 4.034 9.817

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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 2.605 2.605 2.605 3.499 4.064 4.064 4.064 1.459 1.459 0.460 3.426 ms 287.6 1977

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

peer offset 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.24 0.800 0.800 0.800 1.806 2.563 2.563 2.563 1.763 1.763 0.392 1.790 ms 55.29 233.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 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 1.878 1.878 1.878 2.852 3.273 3.273 3.273 1.395 1.395 0.390 2.692 ms 222.2 1407

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 76.14.161.109

peer offset 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 76.14.161.109 -1.331 -1.331 -1.331 0.089 2.082 2.082 2.082 3.413 3.413 0.915 0.092 ms -2.753 6.322

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(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -411.025 -402.899 -393.694 -375.105 -353.275 -343.056 -324.160 40.419 59.843 12.495 -374.444 ms -2.979e+04 9.255e+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 SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -593.000 -550.000 -429.000 -45.000 335.000 460.000 531.000 764.000 1,010.000 220.185 -42.942 ns -5.223 13.01

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 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 1.112 1.112 1.112 5.168 5.620 5.620 5.620 4.508 4.508 2.118 3.282 ms 1.831 2.964

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 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 169.229.128.134 0.382 0.382 0.382 2.177 10.139 10.139 10.139 9.757 9.757 3.687 3.743 ms 1.016 2.284

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 178.62.68.79

peer jitter 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.62.68.79 1.906 1.906 1.906 2.774 2.889 2.889 2.889 0.983 0.983 0.439 2.523 ms 120.9 634.4

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 192.168.1.10

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 0.131 0.131 0.191 0.705 75.292 75.754 75.754 75.101 75.622 18.461 5.803 ms 1.124 6.755

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 203.123.48.219

peer jitter 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 203.123.48.219 0.943 0.943 0.943 1.829 75.171 75.171 75.171 74.228 74.228 24.899 11.568 ms 0.3958 2.836

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

peer jitter 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.24 1.570 1.570 1.570 3.947 5.155 5.155 5.155 3.585 3.585 0.874 3.710 ms 43.02 166.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 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 1.431 1.431 1.431 3.619 75.217 75.217 75.217 73.786 73.786 17.609 8.909 ms 1.717 7.548

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 76.14.161.109

peer jitter 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 76.14.161.109 2.504 2.504 2.504 7.231 36.589 36.589 36.589 34.085 34.085 9.661 11.140 ms 2.345 6.756

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(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 2.930 4.633 6.293 11.927 23.136 29.185 40.001 16.842 24.552 5.268 13.029 ms 8.795 29.69

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(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 91.000 91.000 120.000 206.000 404.000 510.000 554.000 284.000 419.000 86.227 226.173 ns 10.34 34.95

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 -5.701 -5.701 -5.700 -5.698 -5.697 -5.697 -5.697 0.0038 0.0042 0.0011 -5.698 ppm -1.243e+11 6.204e+14
Local Clock Time Offset -592.000 -550.000 -428.000 -44.000 334.000 459.000 530.000 762.000 1,009.000 219.474 -42.769 ns -5.224 13.03
Local RMS Frequency Jitter 28.000 30.000 33.000 54.000 78.000 83.000 88.000 45.000 53.000 12.443 53.911 10e-12 47.23 195.8
Local RMS Time Jitter 101.000 115.000 155.000 238.000 307.000 328.000 336.000 152.000 213.000 46.909 235.044 ns 76.23 352.9
Server Jitter 104.131.155.175 1.112 1.112 1.112 5.168 5.620 5.620 5.620 4.508 4.508 2.118 3.282 ms 1.831 2.964
Server Jitter 169.229.128.134 0.382 0.382 0.382 2.177 10.139 10.139 10.139 9.757 9.757 3.687 3.743 ms 1.016 2.284
Server Jitter 178.62.68.79 1.906 1.906 1.906 2.774 2.889 2.889 2.889 0.983 0.983 0.439 2.523 ms 120.9 634.4
Server Jitter 192.168.1.10 0.131 0.131 0.191 0.705 75.292 75.754 75.754 75.101 75.622 18.461 5.803 ms 1.124 6.755
Server Jitter 203.123.48.219 0.943 0.943 0.943 1.829 75.171 75.171 75.171 74.228 74.228 24.899 11.568 ms 0.3958 2.836
Server Jitter 204.17.205.24 1.570 1.570 1.570 3.947 5.155 5.155 5.155 3.585 3.585 0.874 3.710 ms 43.02 166.8
Server Jitter 66.220.9.122 1.431 1.431 1.431 3.619 75.217 75.217 75.217 73.786 73.786 17.609 8.909 ms 1.717 7.548
Server Jitter 76.14.161.109 2.504 2.504 2.504 7.231 36.589 36.589 36.589 34.085 34.085 9.661 11.140 ms 2.345 6.756
Server Jitter SHM(0) 2.930 4.633 6.293 11.927 23.136 29.185 40.001 16.842 24.552 5.268 13.029 ms 8.795 29.69
Server Jitter SHM(1) 91.000 91.000 120.000 206.000 404.000 510.000 554.000 284.000 419.000 86.227 226.173 ns 10.34 34.95
Server Offset 104.131.155.175 2.864 2.864 2.864 3.266 3.664 3.664 3.664 0.800 0.800 0.318 3.181 ms 754.9 7047
Server Offset 169.229.128.134 1.792 1.792 1.792 2.370 2.851 2.851 2.851 1.060 1.060 0.272 2.321 ms 449.6 3555
Server Offset 178.62.68.79 6.501 6.501 6.501 6.661 8.894 8.894 8.894 2.392 2.392 1.092 7.352 ms 206.1 1293
Server Offset 192.168.1.10 -60.195 -60.195 30.241 132.039 203.721 243.633 243.633 173.480 303.828 59.841 128.007 µs 4.034 9.817
Server Offset 203.123.48.219 2.605 2.605 2.605 3.499 4.064 4.064 4.064 1.459 1.459 0.460 3.426 ms 287.6 1977
Server Offset 204.17.205.24 0.800 0.800 0.800 1.806 2.563 2.563 2.563 1.763 1.763 0.392 1.790 ms 55.29 233.3
Server Offset 66.220.9.122 1.878 1.878 1.878 2.852 3.273 3.273 3.273 1.395 1.395 0.390 2.692 ms 222.2 1407
Server Offset 76.14.161.109 -1.331 -1.331 -1.331 0.089 2.082 2.082 2.082 3.413 3.413 0.915 0.092 ms -2.753 6.322
Server Offset SHM(0) -411.025 -402.899 -393.694 -375.105 -353.275 -343.056 -324.160 40.419 59.843 12.495 -374.444 ms -2.979e+04 9.255e+05
Server Offset SHM(1) -593.000 -550.000 -429.000 -45.000 335.000 460.000 531.000 764.000 1,010.000 220.185 -42.942 ns -5.223 13.01
TDOP 0.590 0.590 0.600 0.720 1.000 1.180 1.180 0.400 0.590 0.142 0.740 87.59 436.6
Temp ZONE0 59.072 59.072 59.072 60.148 60.148 60.148 60.148 1.076 1.076 0.331 59.843 °C
nSats 8.000 8.000 9.000 10.000 11.000 11.000 11.000 2.000 3.000 0.726 10.150 nSat 2223 2.933e+04
Summary as CSV file


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!