NTPsec

c-ntpsec-72-hour-stats

Report generated: Sun Aug 18 18:12:37 2019 UTC
Start Time: Thu Aug 15 18:12:34 2019 UTC
End Time: Sun Aug 18 18:12:34 2019 UTC
Report published: Sun Aug 18 11:13:54 2019 PDT
Report Period: 3.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,501.000 -955.000 -684.000 -26.000 713.000 990.000 1,475.000 1,397.000 1,945.000 424.965 -11.054 ns -4.028 9.738
Local Clock Frequency Offset -8.096 -8.094 -8.065 -7.940 -7.822 -7.809 -7.806 0.243 0.285 0.069 -7.947 ppm -1.597e+06 1.867e+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 152.000 233.000 360.000 434.000 622.000 208.000 306.000 64.802 241.733 ns 29.42 114.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 38.000 48.000 90.000 197.000 314.000 553.000 149.000 276.000 52.626 102.284 10e-12 5.962 26.36

The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.

Lower is better. An ideal clock would be a horizontal line at 0ppm.

RMS Frequency Jitter is field 6 in the loopstats log file.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -1,501.000 -955.000 -684.000 -26.000 713.000 990.000 1,475.000 1,397.000 1,945.000 424.965 -11.054 ns -4.028 9.738

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.096 -8.094 -8.065 -7.940 -7.822 -7.809 -7.806 0.243 0.285 0.069 -7.947 ppm -1.597e+06 1.867e+08
Temp ZONE0 57.458 57.996 57.996 59.610 61.762 62.300 62.838 3.766 4.304 1.018 59.614 °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.479 9.615 nSat 182.8 1096
TDOP 0.520 0.570 0.600 0.800 1.370 1.740 5.370 0.770 1.170 0.269 0.879 21.81 127.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.358 0.033 0.942 2.636 5.038 22.082 242.430 4.095 22.049 15.551 3.974 ms 12.28 187.7

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 -6.660 -6.164 -2.307 2.855 6.547 7.027 7.348 8.855 13.191 2.902 2.577 ms -1.183 4.037

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.028 2.410 2.483 2.745 3.198 3.695 4.657 0.715 1.285 0.258 2.791 ms 975.9 9921

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 -1.379 -0.678 -0.285 0.228 0.805 1.703 2.823 1.089 2.381 0.393 0.252 ms -0.005633 9.165

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.904 -3.949 2.409 6.324 8.459 22.783 10.273 13.363 3.640 1.830 ms -0.9465 7.571

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 -70.263 -17.641 8.955 46.623 76.818 85.111 128.764 67.863 102.752 21.818 45.328 µs 3.848 9.792

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 -619,315,200.052 -0.001 0.000 0.002 0.004 0.006 0.009 0.004 0.007 21,680,352.189 -759,895.949 s -32.71 938.6

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 204.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.906 2.048 2.226 2.508 2.976 3.211 3.569 0.750 1.164 0.241 2.536 ms 889.7 8762

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.003 1.251 1.401 1.749 2.190 2.682 13.327 0.789 1.431 0.497 1.791 ms 40.83 585.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 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.751 -70.115 -67.536 -57.290 -48.005 -44.848 -42.764 19.531 25.267 5.775 -57.456 ms -1345 1.509e+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,502.000 -956.000 -685.000 -27.000 714.000 991.000 1,476.000 1,399.000 1,947.000 425.736 -11.100 ns -4.028 9.733

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.104 146.247 219.912 380.953 146.247 219.912 50.741 22.025 ms 1.418 10.68

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.181 0.310 1.626 10.172 16.383 95.190 9.862 16.202 4.890 3.347 ms 7.437 133.6

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.135 0.168 0.288 1.721 10.311 15.063 20.771 10.023 14.896 3.628 3.311 ms 1.401 5.046

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.204 0.299 0.520 1.860 13.047 15.978 24.033 12.527 15.678 3.953 3.682 ms 1.521 5.008

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.317 13.521 25.085 25.148 13.222 25.085 4.769 4.511 ms 1.359 5.129

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.007 0.015 0.025 0.093 8.657 9.768 27.569 8.632 9.753 2.677 1.170 ms 0.7817 6.379

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.000 0.000 0.000 0.002 0.011 0.017 553,932,354.692 0.011 0.017 30,388,820.043 2,074,535.148 s 11.66 191.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 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.117 0.178 0.257 1.866 9.771 12.925 14.648 9.514 12.747 3.486 3.550 ms 1.05 2.784

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.000 0.158 0.306 1.476 10.178 16.130 30.875 9.872 15.972 3.809 3.000 ms 2.104 12.21

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.083 0.361 0.599 2.432 6.649 8.326 11.507 6.050 7.965 1.960 2.923 ms 2.446 6.233

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) 39.000 85.000 120.000 260.000 561.000 746.000 1,329.000 441.000 661.000 139.812 289.392 ns 5.687 18.77

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -8.096 -8.094 -8.065 -7.940 -7.822 -7.809 -7.806 0.243 0.285 0.069 -7.947 ppm -1.597e+06 1.867e+08
Local Clock Time Offset -1,501.000 -955.000 -684.000 -26.000 713.000 990.000 1,475.000 1,397.000 1,945.000 424.965 -11.054 ns -4.028 9.738
Local RMS Frequency Jitter 24.000 38.000 48.000 90.000 197.000 314.000 553.000 149.000 276.000 52.626 102.284 10e-12 5.962 26.36
Local RMS Time Jitter 95.000 128.000 152.000 233.000 360.000 434.000 622.000 208.000 306.000 64.802 241.733 ns 29.42 114.1
Server Jitter 104.131.155.175 0.000 0.000 0.000 2.104 146.247 219.912 380.953 146.247 219.912 50.741 22.025 ms 1.418 10.68
Server Jitter 162.159.200.1 0.104 0.181 0.310 1.626 10.172 16.383 95.190 9.862 16.202 4.890 3.347 ms 7.437 133.6
Server Jitter 164.67.62.194 0.135 0.168 0.288 1.721 10.311 15.063 20.771 10.023 14.896 3.628 3.311 ms 1.401 5.046
Server Jitter 173.11.101.155 0.204 0.299 0.520 1.860 13.047 15.978 24.033 12.527 15.678 3.953 3.682 ms 1.521 5.008
Server Jitter 178.62.68.79 0.000 0.000 0.299 2.317 13.521 25.085 25.148 13.222 25.085 4.769 4.511 ms 1.359 5.129
Server Jitter 192.168.1.10 0.007 0.015 0.025 0.093 8.657 9.768 27.569 8.632 9.753 2.677 1.170 ms 0.7817 6.379
Server Jitter 203.123.48.219 0.000 0.000 0.000 0.002 0.011 0.017 553,932,354.692 0.011 0.017 30,388,820.043 2,074,535.148 s 11.66 191.8
Server Jitter 204.123.2.5 0.117 0.178 0.257 1.866 9.771 12.925 14.648 9.514 12.747 3.486 3.550 ms 1.05 2.784
Server Jitter 204.17.205.24 0.000 0.158 0.306 1.476 10.178 16.130 30.875 9.872 15.972 3.809 3.000 ms 2.104 12.21
Server Jitter SHM(0) 0.083 0.361 0.599 2.432 6.649 8.326 11.507 6.050 7.965 1.960 2.923 ms 2.446 6.233
Server Jitter SHM(1) 39.000 85.000 120.000 260.000 561.000 746.000 1,329.000 441.000 661.000 139.812 289.392 ns 5.687 18.77
Server Offset 104.131.155.175 -0.358 0.033 0.942 2.636 5.038 22.082 242.430 4.095 22.049 15.551 3.974 ms 12.28 187.7
Server Offset 162.159.200.1 -6.660 -6.164 -2.307 2.855 6.547 7.027 7.348 8.855 13.191 2.902 2.577 ms -1.183 4.037
Server Offset 164.67.62.194 1.028 2.410 2.483 2.745 3.198 3.695 4.657 0.715 1.285 0.258 2.791 ms 975.9 9921
Server Offset 173.11.101.155 -1.379 -0.678 -0.285 0.228 0.805 1.703 2.823 1.089 2.381 0.393 0.252 ms -0.005633 9.165
Server Offset 178.62.68.79 -6.794 -4.904 -3.949 2.409 6.324 8.459 22.783 10.273 13.363 3.640 1.830 ms -0.9465 7.571
Server Offset 192.168.1.10 -70.263 -17.641 8.955 46.623 76.818 85.111 128.764 67.863 102.752 21.818 45.328 µs 3.848 9.792
Server Offset 203.123.48.219 -619,315,200.052 -0.001 0.000 0.002 0.004 0.006 0.009 0.004 0.007 21,680,352.189 -759,895.949 s -32.71 938.6
Server Offset 204.123.2.5 1.906 2.048 2.226 2.508 2.976 3.211 3.569 0.750 1.164 0.241 2.536 ms 889.7 8762
Server Offset 204.17.205.24 1.003 1.251 1.401 1.749 2.190 2.682 13.327 0.789 1.431 0.497 1.791 ms 40.83 585.9
Server Offset SHM(0) -72.751 -70.115 -67.536 -57.290 -48.005 -44.848 -42.764 19.531 25.267 5.775 -57.456 ms -1345 1.509e+04
Server Offset SHM(1) -1,502.000 -956.000 -685.000 -27.000 714.000 991.000 1,476.000 1,399.000 1,947.000 425.736 -11.100 ns -4.028 9.733
TDOP 0.520 0.570 0.600 0.800 1.370 1.740 5.370 0.770 1.170 0.269 0.879 21.81 127.8
Temp ZONE0 57.458 57.996 57.996 59.610 61.762 62.300 62.838 3.766 4.304 1.018 59.614 °C
nSats 5.000 7.000 7.000 10.000 12.000 12.000 13.000 5.000 5.000 1.479 9.615 nSat 182.8 1096
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!