NTPsec

B-ntpsec-6-hour-stats

Report generated: Thu Apr 2 03:01:39 2020 UTC
Start Time: Wed Apr 1 21:01:38 2020 UTC
End Time: Thu Apr 2 03:01:38 2020 UTC
Report published: Wed Apr 01 20:01:44 2020 PDT
Report Period: 0.2 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,178.000 -990.000 -790.000 -233.000 166.000 294.000 468.000 956.000 1,284.000 282.001 -261.555 ns -13.41 42.79
Local Clock Frequency Offset -5.763 -5.763 -5.762 -5.725 -5.680 -5.678 -5.677 0.082 0.086 0.027 -5.723 ppm -9.438e+06 1.995e+09

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 198.000 212.000 238.000 348.000 479.000 523.000 572.000 241.000 311.000 73.817 352.654 ns 65.47 295.3

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 43.000 48.000 55.000 89.000 138.000 149.000 162.000 83.000 101.000 24.861 91.296 10e-12 27.5 100.6

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,178.000 -990.000 -790.000 -233.000 166.000 294.000 468.000 956.000 1,284.000 282.001 -261.555 ns -13.41 42.79

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.763 -5.763 -5.762 -5.725 -5.680 -5.678 -5.677 0.082 0.086 0.027 -5.723 ppm -9.438e+06 1.995e+09
Temp ZONE0 61.224 61.762 62.300 62.300 62.838 63.376 63.376 0.538 1.614 0.324 62.491 °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 6.000 6.000 7.000 8.000 9.000 9.000 10.000 2.000 3.000 0.751 7.691 nSat 815.4 7788
TDOP 0.710 0.720 0.860 1.040 1.670 2.580 2.660 0.810 1.860 0.334 1.190 26.01 103.8

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.688 0.688 1.738 2.574 3.516 3.699 3.699 1.778 3.010 0.529 2.593 ms 70.69 321.2

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.627 1.627 1.946 2.347 2.985 3.213 3.213 1.039 1.586 0.299 2.372 ms 356.3 2631

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 -5.270 -5.270 -5.270 4.288 8.082 8.082 8.082 13.352 13.352 3.290 3.545 ms -0.6413 3.225

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 35.811 43.609 63.422 94.651 137.443 151.220 200.512 74.021 107.611 22.863 96.824 µs 44.13 183.9

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.153 0.153 0.534 2.651 3.206 3.361 3.361 2.672 3.208 0.874 2.290 ms 7.928 17.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.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.998 0.998 1.588 1.966 2.589 2.750 2.750 1.000 1.752 0.324 2.021 ms 159.6 920.9

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 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 1.686 1.686 2.284 2.617 3.128 3.493 3.493 0.844 1.807 0.301 2.649 ms 498.3 4077

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 216.218.254.202

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.254.202 2.372 2.372 2.392 2.788 3.331 3.926 3.926 0.939 1.554 0.311 2.814 ms 547.3 4639

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 -10.684 -10.684 -6.592 -1.367 1.890 3.497 3.497 8.482 14.181 2.458 -1.714 ms -10.9 36.73

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) -375.613 -362.375 -352.772 -324.755 -289.190 -271.813 -248.488 63.582 90.563 18.760 -323.948 ms -6151 1.133e+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) -1,179.000 -991.000 -791.000 -234.000 167.000 295.000 469.000 958.000 1,286.000 282.442 -262.194 ns -13.41 42.78

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.434 0.434 0.559 2.406 9.585 12.307 12.307 9.026 11.873 3.269 3.993 ms 1.48 3.187

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.223 0.223 0.664 2.460 9.328 11.700 11.700 8.664 11.477 2.776 3.461 ms 2.21 6.2

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.370 1.370 1.370 4.281 10.674 10.674 10.674 9.305 9.305 2.990 4.649 ms 2.658 6.174

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.016 0.017 0.032 0.131 8.617 12.230 13.953 8.585 12.213 2.615 1.366 ms 0.8772 5.409

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.832 0.832 1.110 2.963 8.559 9.656 9.656 7.449 8.824 2.466 3.863 ms 2.911 7.123

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.646 0.646 0.819 1.766 9.746 9.924 9.924 8.927 9.277 2.445 2.630 ms 2.451 7.494

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 216.218.192.202

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.423 0.423 0.751 2.627 7.002 9.328 9.328 6.251 8.905 2.058 3.011 ms 2.601 7.098

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 216.218.254.202

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.254.202 0.483 0.483 0.604 3.242 12.811 13.234 13.234 12.207 12.752 3.757 4.454 ms 1.596 3.848

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 1.285 1.285 2.210 12.456 39.047 58.947 58.947 36.838 57.662 10.637 13.720 ms 2.671 9.496

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.169 3.898 5.307 10.142 21.266 30.158 56.573 15.958 26.260 5.322 11.376 ms 6.647 25.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 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) 97.000 129.000 170.000 320.000 599.000 755.000 1,034.000 429.000 626.000 133.291 339.776 ns 9.456 31.63

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.763 -5.763 -5.762 -5.725 -5.680 -5.678 -5.677 0.082 0.086 0.027 -5.723 ppm -9.438e+06 1.995e+09
Local Clock Time Offset -1,178.000 -990.000 -790.000 -233.000 166.000 294.000 468.000 956.000 1,284.000 282.001 -261.555 ns -13.41 42.79
Local RMS Frequency Jitter 43.000 48.000 55.000 89.000 138.000 149.000 162.000 83.000 101.000 24.861 91.296 10e-12 27.5 100.6
Local RMS Time Jitter 198.000 212.000 238.000 348.000 479.000 523.000 572.000 241.000 311.000 73.817 352.654 ns 65.47 295.3
Server Jitter 104.131.155.175 0.434 0.434 0.559 2.406 9.585 12.307 12.307 9.026 11.873 3.269 3.993 ms 1.48 3.187
Server Jitter 169.229.128.134 0.223 0.223 0.664 2.460 9.328 11.700 11.700 8.664 11.477 2.776 3.461 ms 2.21 6.2
Server Jitter 178.62.68.79 1.370 1.370 1.370 4.281 10.674 10.674 10.674 9.305 9.305 2.990 4.649 ms 2.658 6.174
Server Jitter 192.168.1.10 0.016 0.017 0.032 0.131 8.617 12.230 13.953 8.585 12.213 2.615 1.366 ms 0.8772 5.409
Server Jitter 203.123.48.219 0.832 0.832 1.110 2.963 8.559 9.656 9.656 7.449 8.824 2.466 3.863 ms 2.911 7.123
Server Jitter 204.17.205.24 0.646 0.646 0.819 1.766 9.746 9.924 9.924 8.927 9.277 2.445 2.630 ms 2.451 7.494
Server Jitter 216.218.192.202 0.423 0.423 0.751 2.627 7.002 9.328 9.328 6.251 8.905 2.058 3.011 ms 2.601 7.098
Server Jitter 216.218.254.202 0.483 0.483 0.604 3.242 12.811 13.234 13.234 12.207 12.752 3.757 4.454 ms 1.596 3.848
Server Jitter 76.14.161.109 1.285 1.285 2.210 12.456 39.047 58.947 58.947 36.838 57.662 10.637 13.720 ms 2.671 9.496
Server Jitter SHM(0) 2.169 3.898 5.307 10.142 21.266 30.158 56.573 15.958 26.260 5.322 11.376 ms 6.647 25.9
Server Jitter SHM(1) 97.000 129.000 170.000 320.000 599.000 755.000 1,034.000 429.000 626.000 133.291 339.776 ns 9.456 31.63
Server Offset 104.131.155.175 0.688 0.688 1.738 2.574 3.516 3.699 3.699 1.778 3.010 0.529 2.593 ms 70.69 321.2
Server Offset 169.229.128.134 1.627 1.627 1.946 2.347 2.985 3.213 3.213 1.039 1.586 0.299 2.372 ms 356.3 2631
Server Offset 178.62.68.79 -5.270 -5.270 -5.270 4.288 8.082 8.082 8.082 13.352 13.352 3.290 3.545 ms -0.6413 3.225
Server Offset 192.168.1.10 35.811 43.609 63.422 94.651 137.443 151.220 200.512 74.021 107.611 22.863 96.824 µs 44.13 183.9
Server Offset 203.123.48.219 0.153 0.153 0.534 2.651 3.206 3.361 3.361 2.672 3.208 0.874 2.290 ms 7.928 17.86
Server Offset 204.17.205.24 0.998 0.998 1.588 1.966 2.589 2.750 2.750 1.000 1.752 0.324 2.021 ms 159.6 920.9
Server Offset 216.218.192.202 1.686 1.686 2.284 2.617 3.128 3.493 3.493 0.844 1.807 0.301 2.649 ms 498.3 4077
Server Offset 216.218.254.202 2.372 2.372 2.392 2.788 3.331 3.926 3.926 0.939 1.554 0.311 2.814 ms 547.3 4639
Server Offset 76.14.161.109 -10.684 -10.684 -6.592 -1.367 1.890 3.497 3.497 8.482 14.181 2.458 -1.714 ms -10.9 36.73
Server Offset SHM(0) -375.613 -362.375 -352.772 -324.755 -289.190 -271.813 -248.488 63.582 90.563 18.760 -323.948 ms -6151 1.133e+05
Server Offset SHM(1) -1,179.000 -991.000 -791.000 -234.000 167.000 295.000 469.000 958.000 1,286.000 282.442 -262.194 ns -13.41 42.78
TDOP 0.710 0.720 0.860 1.040 1.670 2.580 2.660 0.810 1.860 0.334 1.190 26.01 103.8
Temp ZONE0 61.224 61.762 62.300 62.300 62.838 63.376 63.376 0.538 1.614 0.324 62.491 °C
nSats 6.000 6.000 7.000 8.000 9.000 9.000 10.000 2.000 3.000 0.751 7.691 nSat 815.4 7788
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!