NTPsec

B-ntpsec-12-hour-stats

Report generated: Mon Sep 16 02:03:33 2019 UTC
Start Time: Sun Sep 15 14:03:30 2019 UTC
End Time: Mon Sep 16 02:03:30 2019 UTC
Report published: Sun Sep 15 19:03:46 2019 PDT
Report Period: 0.5 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 -817.000 -614.000 -434.000 -57.000 272.000 411.000 656.000 706.000 1,025.000 217.209 -70.124 ns -6.478 17.56
Local Clock Frequency Offset -5.691 -5.688 -5.683 -5.640 -5.635 -5.635 -5.634 0.048 0.054 0.0155 -5.648 ppm -4.842e+07 1.765e+10

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 107.000 121.000 137.000 195.000 280.000 331.000 394.000 143.000 210.000 43.258 198.870 ns 58.15 261

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 27.000 31.000 47.000 93.000 112.000 130.000 62.000 85.000 18.885 52.713 10e-12 12.36 42.7

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 -817.000 -614.000 -434.000 -57.000 272.000 411.000 656.000 706.000 1,025.000 217.209 -70.124 ns -6.478 17.56

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.691 -5.688 -5.683 -5.640 -5.635 -5.635 -5.634 0.048 0.054 0.0155 -5.648 ppm -4.842e+07 1.765e+10
Temp ZONE0 55.844 55.844 56.382 56.920 59.072 59.072 59.610 2.690 3.228 0.855 57.341 °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 7.000 7.000 9.000 12.000 12.000 12.000 5.000 5.000 1.492 9.369 nSat 162.9 946.4
TDOP 0.570 0.600 0.620 0.840 1.350 1.560 2.060 0.730 0.960 0.242 0.899 29.48 117.7

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 -19.940 -19.940 -19.940 2.291 5.350 5.350 5.350 25.291 25.291 6.383 0.846 ms -6.072 24.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 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 1.231 1.231 1.936 2.243 2.560 2.917 2.917 0.624 1.686 0.210 2.244 ms 935 9306

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.872 1.981 2.116 2.370 2.752 3.511 3.681 0.636 1.530 0.236 2.409 ms 809.5 7769

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 -4.227 -4.227 -2.859 3.124 6.500 7.216 7.216 9.359 11.443 2.735 2.661 ms -0.967 3.308

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 -58.802 -1.134 15.527 50.839 85.278 108.723 226.166 69.751 109.857 23.801 50.873 µs 5.3 19.45

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 -752.724 -680.492 -426.328 -31.744 344.994 613.702 708.259 771.322 1,294.194 227.273 -37.110 µs -5.288 15.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 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.099 1.035 1.317 1.703 2.115 2.394 2.486 0.798 1.358 0.283 1.704 ms 141.1 776.5

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 -0.428 1.987 2.133 2.489 2.896 3.219 3.641 0.764 1.232 0.346 2.489 ms 252.8 1646

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 -2.968 -2.700 -1.839 -0.709 0.399 1.565 1.814 2.238 4.265 0.722 -0.699 ms -13.23 40.27

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) -465.399 -423.161 -412.058 -367.207 -320.306 -306.799 -273.285 91.752 116.362 28.245 -367.029 ms -2783 3.953e+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) -818.000 -615.000 -435.000 -58.000 273.000 412.000 657.000 708.000 1,027.000 217.936 -70.343 ns -6.474 17.53

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 0.712 25.291 25.291 25.291 25.291 25.291 8.257 5.619 ms 0.2319 2.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 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.315 0.315 0.395 2.246 8.919 9.770 9.770 8.524 9.455 2.347 3.193 ms 2.362 6.398

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.361 0.371 0.533 2.832 10.840 13.498 13.520 10.306 13.127 3.533 4.208 ms 1.459 3.464

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.990 0.990 1.396 4.979 10.567 21.341 21.341 9.171 20.351 4.142 5.772 ms 2.654 8.987

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.011 0.021 0.034 0.202 8.706 12.359 38.863 8.672 12.338 3.412 2.030 ms 2.366 23.88

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.302 0.353 0.690 4.340 11.722 18.745 18.880 11.032 18.392 3.710 4.679 ms 2.091 6.577

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.256 0.262 0.693 3.108 11.985 27.781 27.916 11.293 27.518 4.400 4.861 ms 2.47 11.7

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.277 0.345 0.448 2.552 10.346 20.734 133.691 9.898 20.389 11.626 4.495 ms 8.057 89.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.



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.682 0.867 2.088 17.736 100.278 108.045 108.087 98.191 107.178 31.078 28.859 ms 1.138 3.182

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.276 4.660 6.213 11.709 23.322 31.158 63.110 17.109 26.497 5.508 12.873 ms 7.848 28.26

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) 34.000 78.000 101.000 186.000 363.000 463.000 576.000 262.000 385.000 81.675 203.537 ns 8.859 28.96

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.691 -5.688 -5.683 -5.640 -5.635 -5.635 -5.634 0.048 0.054 0.0155 -5.648 ppm -4.842e+07 1.765e+10
Local Clock Time Offset -817.000 -614.000 -434.000 -57.000 272.000 411.000 656.000 706.000 1,025.000 217.209 -70.124 ns -6.478 17.56
Local RMS Frequency Jitter 24.000 27.000 31.000 47.000 93.000 112.000 130.000 62.000 85.000 18.885 52.713 10e-12 12.36 42.7
Local RMS Time Jitter 107.000 121.000 137.000 195.000 280.000 331.000 394.000 143.000 210.000 43.258 198.870 ns 58.15 261
Server Jitter 104.131.155.175 0.000 0.000 0.000 0.712 25.291 25.291 25.291 25.291 25.291 8.257 5.619 ms 0.2319 2.2
Server Jitter 162.213.2.253 0.315 0.315 0.395 2.246 8.919 9.770 9.770 8.524 9.455 2.347 3.193 ms 2.362 6.398
Server Jitter 169.229.128.134 0.361 0.371 0.533 2.832 10.840 13.498 13.520 10.306 13.127 3.533 4.208 ms 1.459 3.464
Server Jitter 178.62.68.79 0.990 0.990 1.396 4.979 10.567 21.341 21.341 9.171 20.351 4.142 5.772 ms 2.654 8.987
Server Jitter 192.168.1.10 0.011 0.021 0.034 0.202 8.706 12.359 38.863 8.672 12.338 3.412 2.030 ms 2.366 23.88
Server Jitter 203.123.48.219 0.302 0.353 0.690 4.340 11.722 18.745 18.880 11.032 18.392 3.710 4.679 ms 2.091 6.577
Server Jitter 204.17.205.24 0.256 0.262 0.693 3.108 11.985 27.781 27.916 11.293 27.518 4.400 4.861 ms 2.47 11.7
Server Jitter 216.218.192.202 0.277 0.345 0.448 2.552 10.346 20.734 133.691 9.898 20.389 11.626 4.495 ms 8.057 89.77
Server Jitter 76.14.161.109 0.682 0.867 2.088 17.736 100.278 108.045 108.087 98.191 107.178 31.078 28.859 ms 1.138 3.182
Server Jitter SHM(0) 2.276 4.660 6.213 11.709 23.322 31.158 63.110 17.109 26.497 5.508 12.873 ms 7.848 28.26
Server Jitter SHM(1) 34.000 78.000 101.000 186.000 363.000 463.000 576.000 262.000 385.000 81.675 203.537 ns 8.859 28.96
Server Offset 104.131.155.175 -19.940 -19.940 -19.940 2.291 5.350 5.350 5.350 25.291 25.291 6.383 0.846 ms -6.072 24.26
Server Offset 162.213.2.253 1.231 1.231 1.936 2.243 2.560 2.917 2.917 0.624 1.686 0.210 2.244 ms 935 9306
Server Offset 169.229.128.134 1.872 1.981 2.116 2.370 2.752 3.511 3.681 0.636 1.530 0.236 2.409 ms 809.5 7769
Server Offset 178.62.68.79 -4.227 -4.227 -2.859 3.124 6.500 7.216 7.216 9.359 11.443 2.735 2.661 ms -0.967 3.308
Server Offset 192.168.1.10 -58.802 -1.134 15.527 50.839 85.278 108.723 226.166 69.751 109.857 23.801 50.873 µs 5.3 19.45
Server Offset 203.123.48.219 -752.724 -680.492 -426.328 -31.744 344.994 613.702 708.259 771.322 1,294.194 227.273 -37.110 µs -5.288 15.79
Server Offset 204.17.205.24 -0.099 1.035 1.317 1.703 2.115 2.394 2.486 0.798 1.358 0.283 1.704 ms 141.1 776.5
Server Offset 216.218.192.202 -0.428 1.987 2.133 2.489 2.896 3.219 3.641 0.764 1.232 0.346 2.489 ms 252.8 1646
Server Offset 76.14.161.109 -2.968 -2.700 -1.839 -0.709 0.399 1.565 1.814 2.238 4.265 0.722 -0.699 ms -13.23 40.27
Server Offset SHM(0) -465.399 -423.161 -412.058 -367.207 -320.306 -306.799 -273.285 91.752 116.362 28.245 -367.029 ms -2783 3.953e+04
Server Offset SHM(1) -818.000 -615.000 -435.000 -58.000 273.000 412.000 657.000 708.000 1,027.000 217.936 -70.343 ns -6.474 17.53
TDOP 0.570 0.600 0.620 0.840 1.350 1.560 2.060 0.730 0.960 0.242 0.899 29.48 117.7
Temp ZONE0 55.844 55.844 56.382 56.920 59.072 59.072 59.610 2.690 3.228 0.855 57.341 °C
nSats 6.000 7.000 7.000 9.000 12.000 12.000 12.000 5.000 5.000 1.492 9.369 nSat 162.9 946.4
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!