NTPsec

b-ntpsec-5-day-stats

Report generated: Sun Aug 18 19:16:53 2019 UTC
Start Time: Tue Aug 13 19:16:18 2019 UTC
End Time: Sun Aug 18 19:16:18 2019 UTC
Report published: Sun Aug 18 12:18:24 2019 PDT
Report Period: 5.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 -2,723.000 -896.000 -626.000 25.000 627.000 884.000 1,532.000 1,253.000 1,780.000 378.127 17.929 ns -3.823 9.799
Local Clock Frequency Offset -6.155 -6.135 -6.043 -5.817 -5.766 -5.760 -5.756 0.277 0.375 0.083 -5.849 ppm -3.588e+05 2.551e+07

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 87.000 121.000 141.000 210.000 312.000 366.000 1,340.000 171.000 245.000 55.870 216.980 ns 34.82 173.9

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 18.000 30.000 37.000 70.000 209.000 299.000 521.000 172.000 269.000 57.287 89.253 10e-12 3.898 14.97

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 -2,723.000 -896.000 -626.000 25.000 627.000 884.000 1,532.000 1,253.000 1,780.000 378.127 17.929 ns -3.823 9.799

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 -6.155 -6.135 -6.043 -5.817 -5.766 -5.760 -5.756 0.277 0.375 0.083 -5.849 ppm -3.588e+05 2.551e+07
Temp ZONE0 57.996 58.534 59.072 60.148 62.300 62.838 63.376 3.228 4.304 0.944 60.036 °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 6.000 7.000 9.000 11.000 12.000 12.000 4.000 6.000 1.409 9.128 nSat 180.9 1084
TDOP 0.540 0.590 0.620 0.870 1.560 2.070 5.700 0.940 1.480 0.326 0.963 16.43 89.13

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 -24.012 -0.109 0.996 2.900 6.917 8.529 11.430 5.920 8.639 1.888 3.164 ms 0.2967 41.29

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

peer offset 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.213.2.253 0.004 1.300 1.791 2.243 2.830 3.343 4.671 1.038 2.042 0.356 2.265 ms 170.2 1015

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 0.659 2.019 2.196 2.470 2.895 3.205 3.719 0.699 1.186 0.231 2.499 ms 974.9 9871

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 -10.987 -3.866 -2.083 3.848 7.204 8.372 10.097 9.287 12.238 2.901 3.134 ms -0.5009 3.773

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 -133.344 -10.823 11.597 47.321 76.483 85.316 147.510 64.886 96.139 21.270 46.116 µs 4.451 12.26

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.037 -0.001 0.001 0.002 0.005 0.006 0.009 0.005 0.006 17,317,146.618 -484,597.181 s -39.88 1430

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.782 1.158 1.344 1.725 2.177 2.494 4.057 0.833 1.336 0.265 1.739 ms 190.5 1183

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

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

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

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



Server Offset 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 -0.892 2.084 2.245 2.531 2.930 3.236 3.831 0.685 1.152 0.250 2.551 ms 801.8 7602

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 -4.073 -2.862 -1.951 -0.635 0.892 2.282 6.615 2.843 5.145 0.923 -0.598 ms -8.272 26.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 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) -194.121 -107.877 -102.849 -88.728 -77.022 -72.934 -61.939 25.826 34.944 7.766 -89.160 ms -1982 2.522e+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) -2,724.000 -897.000 -627.000 25.000 628.000 885.000 1,533.000 1,255.000 1,782.000 378.889 17.982 ns -3.822 9.79

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.302 1.625 115.965 180.513 305.993 115.662 180.513 38.475 13.768 ms 1.619 10.91

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

peer jitter 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.213.2.253 0.000 0.201 0.333 1.603 10.058 15.517 39.666 9.725 15.315 4.281 3.359 ms 3.115 24.33

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.000 0.196 0.309 1.735 10.425 16.063 73.543 10.116 15.867 4.244 3.341 ms 4.203 55.69

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.234 0.440 1.954 12.074 20.526 44.591 11.635 20.291 4.392 3.823 ms 2.274 13.85

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.017 0.028 0.099 8.670 9.817 27.920 8.642 9.800 2.748 1.230 ms 0.8859 7.625

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.010 0.017 619,315,200.007 0.010 0.017 29,942,333.569 1,952,399.701 s 12.94 235.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 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.130 0.209 0.322 1.490 9.731 14.165 59.196 9.408 13.956 4.179 2.985 ms 4.927 61.27

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 0.078 0.188 0.276 1.678 10.649 15.290 111.487 10.373 15.103 5.602 3.374 ms 9.642 180.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 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 0.529 0.788 1.338 8.888 37.414 48.105 101.569 36.077 47.317 12.733 13.069 ms 1.741 8.022

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) 1.104 3.030 4.069 7.517 13.961 17.205 112.108 9.893 14.175 3.070 8.066 ms 10.48 45.36

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) 27.000 80.000 108.000 209.000 411.000 528.000 2,679.000 303.000 448.000 97.353 227.303 ns 8.304 45.73

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 -6.155 -6.135 -6.043 -5.817 -5.766 -5.760 -5.756 0.277 0.375 0.083 -5.849 ppm -3.588e+05 2.551e+07
Local Clock Time Offset -2,723.000 -896.000 -626.000 25.000 627.000 884.000 1,532.000 1,253.000 1,780.000 378.127 17.929 ns -3.823 9.799
Local RMS Frequency Jitter 18.000 30.000 37.000 70.000 209.000 299.000 521.000 172.000 269.000 57.287 89.253 10e-12 3.898 14.97
Local RMS Time Jitter 87.000 121.000 141.000 210.000 312.000 366.000 1,340.000 171.000 245.000 55.870 216.980 ns 34.82 173.9
Server Jitter 104.131.155.175 0.000 0.000 0.302 1.625 115.965 180.513 305.993 115.662 180.513 38.475 13.768 ms 1.619 10.91
Server Jitter 162.213.2.253 0.000 0.201 0.333 1.603 10.058 15.517 39.666 9.725 15.315 4.281 3.359 ms 3.115 24.33
Server Jitter 169.229.128.134 0.000 0.196 0.309 1.735 10.425 16.063 73.543 10.116 15.867 4.244 3.341 ms 4.203 55.69
Server Jitter 178.62.68.79 0.000 0.234 0.440 1.954 12.074 20.526 44.591 11.635 20.291 4.392 3.823 ms 2.274 13.85
Server Jitter 192.168.1.10 0.009 0.017 0.028 0.099 8.670 9.817 27.920 8.642 9.800 2.748 1.230 ms 0.8859 7.625
Server Jitter 203.123.48.219 0.000 0.000 0.000 0.002 0.010 0.017 619,315,200.007 0.010 0.017 29,942,333.569 1,952,399.701 s 12.94 235.9
Server Jitter 204.17.205.24 0.130 0.209 0.322 1.490 9.731 14.165 59.196 9.408 13.956 4.179 2.985 ms 4.927 61.27
Server Jitter 66.220.9.122 0.078 0.188 0.276 1.678 10.649 15.290 111.487 10.373 15.103 5.602 3.374 ms 9.642 180.2
Server Jitter 76.14.161.109 0.529 0.788 1.338 8.888 37.414 48.105 101.569 36.077 47.317 12.733 13.069 ms 1.741 8.022
Server Jitter SHM(0) 1.104 3.030 4.069 7.517 13.961 17.205 112.108 9.893 14.175 3.070 8.066 ms 10.48 45.36
Server Jitter SHM(1) 27.000 80.000 108.000 209.000 411.000 528.000 2,679.000 303.000 448.000 97.353 227.303 ns 8.304 45.73
Server Offset 104.131.155.175 -24.012 -0.109 0.996 2.900 6.917 8.529 11.430 5.920 8.639 1.888 3.164 ms 0.2967 41.29
Server Offset 162.213.2.253 0.004 1.300 1.791 2.243 2.830 3.343 4.671 1.038 2.042 0.356 2.265 ms 170.2 1015
Server Offset 169.229.128.134 0.659 2.019 2.196 2.470 2.895 3.205 3.719 0.699 1.186 0.231 2.499 ms 974.9 9871
Server Offset 178.62.68.79 -10.987 -3.866 -2.083 3.848 7.204 8.372 10.097 9.287 12.238 2.901 3.134 ms -0.5009 3.773
Server Offset 192.168.1.10 -133.344 -10.823 11.597 47.321 76.483 85.316 147.510 64.886 96.139 21.270 46.116 µs 4.451 12.26
Server Offset 203.123.48.219 -619,315,200.037 -0.001 0.001 0.002 0.005 0.006 0.009 0.005 0.006 17,317,146.618 -484,597.181 s -39.88 1430
Server Offset 204.17.205.24 0.782 1.158 1.344 1.725 2.177 2.494 4.057 0.833 1.336 0.265 1.739 ms 190.5 1183
Server Offset 66.220.9.122 -0.892 2.084 2.245 2.531 2.930 3.236 3.831 0.685 1.152 0.250 2.551 ms 801.8 7602
Server Offset 76.14.161.109 -4.073 -2.862 -1.951 -0.635 0.892 2.282 6.615 2.843 5.145 0.923 -0.598 ms -8.272 26.25
Server Offset SHM(0) -194.121 -107.877 -102.849 -88.728 -77.022 -72.934 -61.939 25.826 34.944 7.766 -89.160 ms -1982 2.522e+04
Server Offset SHM(1) -2,724.000 -897.000 -627.000 25.000 628.000 885.000 1,533.000 1,255.000 1,782.000 378.889 17.982 ns -3.822 9.79
TDOP 0.540 0.590 0.620 0.870 1.560 2.070 5.700 0.940 1.480 0.326 0.963 16.43 89.13
Temp ZONE0 57.996 58.534 59.072 60.148 62.300 62.838 63.376 3.228 4.304 0.944 60.036 °C
nSats 5.000 6.000 7.000 9.000 11.000 12.000 12.000 4.000 6.000 1.409 9.128 nSat 180.9 1084
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!