NTPsec

C-ntpsec-3-hour-stats

Report generated: Wed Oct 23 21:04:34 2019 UTC
Start Time: Wed Oct 23 18:04:33 2019 UTC
End Time: Wed Oct 23 21:04:33 2019 UTC
Report published: Wed Oct 23 14:05:48 2019 PDT
Report Period: 0.1 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 -704.000 -555.000 -358.000 -15.000 392.000 635.000 795.000 750.000 1,190.000 233.554 -11.614 ns -3.97 9.874
Local Clock Frequency Offset -7.196 -7.196 -7.196 -7.193 -7.192 -7.191 -7.191 0.0042 0.0048 0.0012 -7.194 ppm -2.219e+11 1.344e+15

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 78.000 102.000 116.000 170.000 261.000 279.000 307.000 145.000 177.000 44.670 178.063 ns 36.02 140.7

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 22.000 26.000 30.000 53.000 88.000 107.000 122.000 58.000 81.000 17.401 54.785 10e-12 17.29 61.26

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 -704.000 -555.000 -358.000 -15.000 392.000 635.000 795.000 750.000 1,190.000 233.554 -11.614 ns -3.97 9.874

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 -7.196 -7.196 -7.196 -7.193 -7.192 -7.191 -7.191 0.0042 0.0048 0.0012 -7.194 ppm -2.219e+11 1.344e+15
Temp ZONE0 63.376 63.376 63.376 63.914 64.452 64.990 64.990 1.076 1.614 0.417 63.896 °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 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.263 9.871 nSat 336.7 2434
TDOP 0.570 0.570 0.580 0.680 1.470 1.480 1.480 0.890 0.910 0.311 0.862 11.95 38.67

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.060 2.060 2.060 3.175 6.187 6.187 6.187 4.127 4.127 0.859 3.291 ms 33.11 142.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 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 -776.083 -776.083 -614.217 29.207 651.130 717.622 717.622 1,265.347 1,493.705 384.297 20.176 µs -3.59 7.898

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.637 1.637 2.295 2.802 3.230 3.343 3.343 0.935 1.707 0.332 2.743 ms 402.6 3065

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.243 -0.243 -0.232 0.571 1.677 1.876 1.876 1.909 2.120 0.542 0.636 ms 0.8467 2.823

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 2.544 2.544 2.544 3.249 7.951 7.951 7.951 5.407 5.407 1.821 4.110 ms 6.958 21.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 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 32.403 43.472 126.521 267.367 388.466 495.097 509.129 261.945 451.625 79.052 270.528 µs 21.27 72.21

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 4.679 4.679 4.894 5.746 6.716 6.966 6.966 1.822 2.287 0.523 5.754 ms 1030 1.061e+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.495 1.495 1.519 2.053 2.958 3.230 3.230 1.440 1.735 0.412 2.089 ms 80.58 391.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 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) -67.792 -67.127 -65.912 -56.979 -46.064 -45.160 -44.932 19.848 21.967 5.248 -56.959 ms -1701 2.058e+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) -705.000 -556.000 -359.000 -16.000 393.000 636.000 796.000 752.000 1,192.000 234.303 -11.674 ns -3.972 9.865

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.000 2.967 11.691 11.691 11.691 11.691 11.691 3.834 4.566 ms 1.19 2.602

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.634 0.634 0.927 2.123 9.591 10.084 10.084 8.664 9.450 3.017 3.745 ms 1.758 3.754

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.665 0.665 0.824 2.308 8.983 9.826 9.826 8.159 9.161 2.871 3.918 ms 1.928 3.998

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.473 0.473 0.856 4.366 16.492 16.836 16.836 15.636 16.362 5.518 6.796 ms 1.28 2.746

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.797 1.797 1.797 2.948 6.120 6.120 6.120 4.323 4.323 1.330 3.444 ms 9.592 29.45

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.117 0.125 0.181 0.875 75.237 77.653 82.082 75.056 77.528 21.699 8.830 ms 0.6057 4.059

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 1.077 1.077 1.237 2.748 9.085 9.831 9.831 7.848 8.754 2.272 3.464 ms 2.99 8.045

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.051 1.051 1.058 3.236 8.916 9.156 9.156 7.858 8.104 2.684 4.369 ms 2.714 5.773

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.472 0.615 0.814 2.752 6.502 7.279 7.402 5.688 6.665 1.869 3.225 ms 2.983 6.668

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) 28.000 67.000 92.000 211.000 473.000 641.000 708.000 381.000 574.000 117.998 235.560 ns 5.179 16.44

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 -7.196 -7.196 -7.196 -7.193 -7.192 -7.191 -7.191 0.0042 0.0048 0.0012 -7.194 ppm -2.219e+11 1.344e+15
Local Clock Time Offset -704.000 -555.000 -358.000 -15.000 392.000 635.000 795.000 750.000 1,190.000 233.554 -11.614 ns -3.97 9.874
Local RMS Frequency Jitter 22.000 26.000 30.000 53.000 88.000 107.000 122.000 58.000 81.000 17.401 54.785 10e-12 17.29 61.26
Local RMS Time Jitter 78.000 102.000 116.000 170.000 261.000 279.000 307.000 145.000 177.000 44.670 178.063 ns 36.02 140.7
Server Jitter 104.131.155.175 0.000 0.000 0.000 2.967 11.691 11.691 11.691 11.691 11.691 3.834 4.566 ms 1.19 2.602
Server Jitter 162.159.200.1 0.634 0.634 0.927 2.123 9.591 10.084 10.084 8.664 9.450 3.017 3.745 ms 1.758 3.754
Server Jitter 164.67.62.194 0.665 0.665 0.824 2.308 8.983 9.826 9.826 8.159 9.161 2.871 3.918 ms 1.928 3.998
Server Jitter 173.11.101.155 0.473 0.473 0.856 4.366 16.492 16.836 16.836 15.636 16.362 5.518 6.796 ms 1.28 2.746
Server Jitter 178.62.68.79 1.797 1.797 1.797 2.948 6.120 6.120 6.120 4.323 4.323 1.330 3.444 ms 9.592 29.45
Server Jitter 192.168.1.10 0.117 0.125 0.181 0.875 75.237 77.653 82.082 75.056 77.528 21.699 8.830 ms 0.6057 4.059
Server Jitter 203.123.48.219 1.077 1.077 1.237 2.748 9.085 9.831 9.831 7.848 8.754 2.272 3.464 ms 2.99 8.045
Server Jitter 204.17.205.24 1.051 1.051 1.058 3.236 8.916 9.156 9.156 7.858 8.104 2.684 4.369 ms 2.714 5.773
Server Jitter SHM(0) 0.472 0.615 0.814 2.752 6.502 7.279 7.402 5.688 6.665 1.869 3.225 ms 2.983 6.668
Server Jitter SHM(1) 28.000 67.000 92.000 211.000 473.000 641.000 708.000 381.000 574.000 117.998 235.560 ns 5.179 16.44
Server Offset 104.131.155.175 2.060 2.060 2.060 3.175 6.187 6.187 6.187 4.127 4.127 0.859 3.291 ms 33.11 142.3
Server Offset 162.159.200.1 -776.083 -776.083 -614.217 29.207 651.130 717.622 717.622 1,265.347 1,493.705 384.297 20.176 µs -3.59 7.898
Server Offset 164.67.62.194 1.637 1.637 2.295 2.802 3.230 3.343 3.343 0.935 1.707 0.332 2.743 ms 402.6 3065
Server Offset 173.11.101.155 -0.243 -0.243 -0.232 0.571 1.677 1.876 1.876 1.909 2.120 0.542 0.636 ms 0.8467 2.823
Server Offset 178.62.68.79 2.544 2.544 2.544 3.249 7.951 7.951 7.951 5.407 5.407 1.821 4.110 ms 6.958 21.05
Server Offset 192.168.1.10 32.403 43.472 126.521 267.367 388.466 495.097 509.129 261.945 451.625 79.052 270.528 µs 21.27 72.21
Server Offset 203.123.48.219 4.679 4.679 4.894 5.746 6.716 6.966 6.966 1.822 2.287 0.523 5.754 ms 1030 1.061e+04
Server Offset 204.17.205.24 1.495 1.495 1.519 2.053 2.958 3.230 3.230 1.440 1.735 0.412 2.089 ms 80.58 391.6
Server Offset SHM(0) -67.792 -67.127 -65.912 -56.979 -46.064 -45.160 -44.932 19.848 21.967 5.248 -56.959 ms -1701 2.058e+04
Server Offset SHM(1) -705.000 -556.000 -359.000 -16.000 393.000 636.000 796.000 752.000 1,192.000 234.303 -11.674 ns -3.972 9.865
TDOP 0.570 0.570 0.580 0.680 1.470 1.480 1.480 0.890 0.910 0.311 0.862 11.95 38.67
Temp ZONE0 63.376 63.376 63.376 63.914 64.452 64.990 64.990 1.076 1.614 0.417 63.896 °C
nSats 8.000 8.000 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.263 9.871 nSat 336.7 2434
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!