NTPsec

C-ntpsec-24-hour-stats

Report generated: Sun Aug 18 19:09:13 2019 UTC
Start Time: Sat Aug 17 19:09:12 2019 UTC
End Time: Sun Aug 18 19:09:12 2019 UTC
Report published: Sun Aug 18 12:10:24 2019 PDT
Report Period: 1.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 -1,225.000 -811.000 -597.000 -56.000 643.000 948.000 1,317.000 1,240.000 1,759.000 375.520 -27.733 ns -4.103 9.872
Local Clock Frequency Offset -8.065 -8.065 -8.063 -7.962 -7.921 -7.919 -7.918 0.142 0.146 0.050 -7.976 ppm -4.11e+06 6.584e+08

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 95.000 128.000 151.000 225.000 331.000 394.000 591.000 180.000 266.000 55.995 230.715 ns 40.56 168.1

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 24.000 37.000 47.000 78.000 160.000 238.000 419.000 113.000 201.000 41.108 87.997 10e-12 7.586 37.43

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 -1,225.000 -811.000 -597.000 -56.000 643.000 948.000 1,317.000 1,240.000 1,759.000 375.520 -27.733 ns -4.103 9.872

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 -8.065 -8.065 -8.063 -7.962 -7.921 -7.919 -7.918 0.142 0.146 0.050 -7.976 ppm -4.11e+06 6.584e+08
Temp ZONE0 57.458 57.996 57.996 59.072 60.148 60.148 60.148 2.152 2.152 0.691 59.052 °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 5.000 7.000 7.000 10.000 12.000 12.000 13.000 5.000 5.000 1.477 9.660 nSat 186.4 1124
TDOP 0.520 0.560 0.600 0.800 1.370 1.730 5.370 0.770 1.170 0.282 0.879 19.72 128.9

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 -0.358 -0.172 0.363 2.703 4.940 7.339 242.430 4.577 7.512 19.674 4.395 ms 9.168 111.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 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 0.490 0.580 0.853 3.126 6.822 7.087 7.348 5.969 6.508 2.153 3.811 ms 2.921 5.819

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 164.67.62.194

peer offset 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 164.67.62.194 1.701 2.421 2.545 2.737 3.081 3.556 4.655 0.536 1.135 0.216 2.763 ms 1668 2.016e+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 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -0.491 -0.424 -0.231 0.247 0.969 1.883 2.230 1.200 2.307 0.387 0.293 ms 0.7501 6.47

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.794 -4.797 -3.774 2.478 6.324 8.459 22.783 10.098 13.256 3.555 1.918 ms -0.8654 7.696

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 -116.941 -11.420 10.754 46.147 76.070 83.545 93.302 65.316 94.965 21.900 44.697 µs 3.309 10.09

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 0.274 0.865 1.120 1.985 3.775 4.091 6.057 2.655 3.226 0.929 2.250 ms 7.883 23.25

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

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 1.925 2.011 2.210 2.481 2.783 3.211 3.411 0.573 1.200 0.207 2.495 ms 1387 1.574e+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 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 1.188 1.286 1.440 1.788 2.244 2.728 2.837 0.803 1.442 0.248 1.812 ms 270.4 1848

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) -72.205 -69.923 -67.558 -57.059 -48.033 -45.059 -42.120 19.525 24.865 5.828 -57.346 ms -1306 1.452e+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(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) -1,226.000 -812.000 -598.000 -57.000 644.000 949.000 1,318.000 1,242.000 1,761.000 376.280 -27.842 ns -4.105 9.868

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 0.000 0.000 0.348 2.423 140.421 173.404 238.880 140.073 173.404 45.818 22.170 ms 0.7691 4.924

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 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.104 0.171 0.274 1.579 10.095 15.576 24.481 9.821 15.405 3.447 2.938 ms 1.804 8.179

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 164.67.62.194

peer jitter 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 164.67.62.194 0.139 0.152 0.313 1.726 10.127 14.397 15.752 9.814 14.245 3.352 3.192 ms 1.46 4.636

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 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.299 0.336 0.524 1.904 15.249 17.627 24.033 14.724 17.290 4.837 4.317 ms 1.194 3.748

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 0.000 0.000 0.299 2.316 14.038 25.085 25.148 13.739 25.085 4.940 4.565 ms 1.373 5.188

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.009 0.016 0.026 0.102 8.658 9.811 12.275 8.632 9.795 2.726 1.345 ms 0.4599 3.311

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.156 0.217 0.348 1.704 11.502 13.968 19.693 11.154 13.751 3.962 3.738 ms 1.143 3.634

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

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.178 0.188 0.379 1.903 9.859 13.477 13.507 9.481 13.289 3.585 3.656 ms 1.175 3.155

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 0.187 0.211 0.334 1.543 10.521 26.288 30.875 10.187 26.077 4.138 3.101 ms 2.53 14.86

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) 0.106 0.325 0.583 2.377 6.679 8.692 11.507 6.096 8.367 2.033 2.901 ms 2.259 5.799

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) 43.000 83.000 119.000 255.000 544.000 715.000 1,004.000 425.000 632.000 134.608 283.167 ns 5.856 18.93

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -8.065 -8.065 -8.063 -7.962 -7.921 -7.919 -7.918 0.142 0.146 0.050 -7.976 ppm -4.11e+06 6.584e+08
Local Clock Time Offset -1,225.000 -811.000 -597.000 -56.000 643.000 948.000 1,317.000 1,240.000 1,759.000 375.520 -27.733 ns -4.103 9.872
Local RMS Frequency Jitter 24.000 37.000 47.000 78.000 160.000 238.000 419.000 113.000 201.000 41.108 87.997 10e-12 7.586 37.43
Local RMS Time Jitter 95.000 128.000 151.000 225.000 331.000 394.000 591.000 180.000 266.000 55.995 230.715 ns 40.56 168.1
Server Jitter 104.131.155.175 0.000 0.000 0.348 2.423 140.421 173.404 238.880 140.073 173.404 45.818 22.170 ms 0.7691 4.924
Server Jitter 162.159.200.1 0.104 0.171 0.274 1.579 10.095 15.576 24.481 9.821 15.405 3.447 2.938 ms 1.804 8.179
Server Jitter 164.67.62.194 0.139 0.152 0.313 1.726 10.127 14.397 15.752 9.814 14.245 3.352 3.192 ms 1.46 4.636
Server Jitter 173.11.101.155 0.299 0.336 0.524 1.904 15.249 17.627 24.033 14.724 17.290 4.837 4.317 ms 1.194 3.748
Server Jitter 178.62.68.79 0.000 0.000 0.299 2.316 14.038 25.085 25.148 13.739 25.085 4.940 4.565 ms 1.373 5.188
Server Jitter 192.168.1.10 0.009 0.016 0.026 0.102 8.658 9.811 12.275 8.632 9.795 2.726 1.345 ms 0.4599 3.311
Server Jitter 203.123.48.219 0.156 0.217 0.348 1.704 11.502 13.968 19.693 11.154 13.751 3.962 3.738 ms 1.143 3.634
Server Jitter 204.123.2.5 0.178 0.188 0.379 1.903 9.859 13.477 13.507 9.481 13.289 3.585 3.656 ms 1.175 3.155
Server Jitter 204.17.205.24 0.187 0.211 0.334 1.543 10.521 26.288 30.875 10.187 26.077 4.138 3.101 ms 2.53 14.86
Server Jitter SHM(0) 0.106 0.325 0.583 2.377 6.679 8.692 11.507 6.096 8.367 2.033 2.901 ms 2.259 5.799
Server Jitter SHM(1) 43.000 83.000 119.000 255.000 544.000 715.000 1,004.000 425.000 632.000 134.608 283.167 ns 5.856 18.93
Server Offset 104.131.155.175 -0.358 -0.172 0.363 2.703 4.940 7.339 242.430 4.577 7.512 19.674 4.395 ms 9.168 111.6
Server Offset 162.159.200.1 0.490 0.580 0.853 3.126 6.822 7.087 7.348 5.969 6.508 2.153 3.811 ms 2.921 5.819
Server Offset 164.67.62.194 1.701 2.421 2.545 2.737 3.081 3.556 4.655 0.536 1.135 0.216 2.763 ms 1668 2.016e+04
Server Offset 173.11.101.155 -0.491 -0.424 -0.231 0.247 0.969 1.883 2.230 1.200 2.307 0.387 0.293 ms 0.7501 6.47
Server Offset 178.62.68.79 -6.794 -4.797 -3.774 2.478 6.324 8.459 22.783 10.098 13.256 3.555 1.918 ms -0.8654 7.696
Server Offset 192.168.1.10 -116.941 -11.420 10.754 46.147 76.070 83.545 93.302 65.316 94.965 21.900 44.697 µs 3.309 10.09
Server Offset 203.123.48.219 0.274 0.865 1.120 1.985 3.775 4.091 6.057 2.655 3.226 0.929 2.250 ms 7.883 23.25
Server Offset 204.123.2.5 1.925 2.011 2.210 2.481 2.783 3.211 3.411 0.573 1.200 0.207 2.495 ms 1387 1.574e+04
Server Offset 204.17.205.24 1.188 1.286 1.440 1.788 2.244 2.728 2.837 0.803 1.442 0.248 1.812 ms 270.4 1848
Server Offset SHM(0) -72.205 -69.923 -67.558 -57.059 -48.033 -45.059 -42.120 19.525 24.865 5.828 -57.346 ms -1306 1.452e+04
Server Offset SHM(1) -1,226.000 -812.000 -598.000 -57.000 644.000 949.000 1,318.000 1,242.000 1,761.000 376.280 -27.842 ns -4.105 9.868
TDOP 0.520 0.560 0.600 0.800 1.370 1.730 5.370 0.770 1.170 0.282 0.879 19.72 128.9
Temp ZONE0 57.458 57.996 57.996 59.072 60.148 60.148 60.148 2.152 2.152 0.691 59.052 °C
nSats 5.000 7.000 7.000 10.000 12.000 12.000 13.000 5.000 5.000 1.477 9.660 nSat 186.4 1124
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!