NTPsec

B-ntpsec-12-hour-stats

Report generated: Sun Aug 18 19:06:54 2019 UTC
Start Time: Sun Aug 18 07:06:52 2019 UTC
End Time: Sun Aug 18 19:06:52 2019 UTC
Report published: Sun Aug 18 12:07:08 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 -621.000 -412.000 -253.000 75.000 412.000 543.000 825.000 665.000 955.000 204.872 74.421 ns -2.137 5.5
Local Clock Frequency Offset -5.810 -5.808 -5.805 -5.782 -5.766 -5.763 -5.761 0.039 0.045 0.0133 -5.782 ppm -8.338e+07 3.643e+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 116.000 130.000 148.000 223.000 319.000 377.000 470.000 171.000 247.000 52.770 226.091 ns 45.88 192.6

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 19.000 28.000 32.000 50.000 78.000 93.000 110.000 46.000 65.000 13.973 51.622 10e-12 28.45 108.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 -621.000 -412.000 -253.000 75.000 412.000 543.000 825.000 665.000 955.000 204.872 74.421 ns -2.137 5.5

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.810 -5.808 -5.805 -5.782 -5.766 -5.763 -5.761 0.039 0.045 0.0133 -5.782 ppm -8.338e+07 3.643e+10
Temp ZONE0 57.996 58.534 59.072 59.072 60.148 60.148 60.148 1.076 1.614 0.404 59.354 °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.474 8.657 nSat 130.7 714.1
TDOP 0.550 0.580 0.620 0.890 1.780 2.580 2.910 1.160 2.000 0.391 1.029 11.15 42.83

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.273 -0.109 0.796 3.115 4.270 4.734 8.104 3.474 4.844 1.150 2.889 ms 8.089 26.36

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.972 1.972 2.001 2.243 2.583 2.886 2.886 0.582 0.914 0.182 2.263 ms 1540 1.807e+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 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.970 1.982 2.130 2.402 2.691 2.783 3.016 0.560 0.802 0.160 2.413 ms 2822 4.028e+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 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 -5.649 -5.135 -3.501 0.814 6.860 7.880 9.776 10.361 13.015 3.295 1.146 ms -2.031 4.312

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.054 -2.838 12.159 48.913 76.907 86.071 96.455 64.748 88.909 20.971 47.591 µs 5.087 13.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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 0.150 0.559 0.780 1.088 1.496 1.706 1.797 0.716 1.148 0.228 1.096 ms 66.84 303.8

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.277 1.286 1.421 1.721 2.042 2.211 2.283 0.621 0.925 0.193 1.716 ms 513.8 4247

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 2.079 2.143 2.240 2.481 2.725 2.910 2.946 0.486 0.767 0.149 2.490 ms 3939 6.271e+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 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 -3.584 -2.412 -1.683 -0.567 0.461 2.232 2.934 2.144 4.644 0.741 -0.568 ms -10.26 32.62

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) -114.177 -107.361 -101.778 -87.431 -75.733 -71.990 -62.770 26.045 35.371 7.797 -87.908 ms -1886 2.362e+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) -622.000 -413.000 -254.000 76.000 413.000 544.000 826.000 667.000 957.000 205.587 74.692 ns -2.141 5.498

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.256 0.336 1.379 33.009 125.505 125.728 32.673 125.248 22.720 7.470 ms 2.173 13.07

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.294 0.294 0.359 1.427 8.875 12.601 12.601 8.517 12.308 2.745 2.641 ms 1.555 4.838

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.134 0.162 0.224 1.359 9.368 28.703 28.806 9.144 28.541 4.518 3.180 ms 2.237 13.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 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.172 0.184 0.406 1.951 9.864 10.765 13.456 9.459 10.581 3.176 3.430 ms 1.257 3.241

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.017 0.030 0.117 8.637 9.775 24.522 8.606 9.758 2.896 1.465 ms 0.8878 7.595

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.213 0.227 0.282 1.074 9.264 9.973 10.422 8.982 9.747 2.960 2.382 ms 1.071 3.103

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.191 0.245 1.364 10.122 14.165 14.175 9.878 13.974 3.180 2.577 ms 1.307 4.527

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.156 0.188 0.217 0.949 7.498 12.319 12.357 7.281 12.132 2.415 1.877 ms 1.748 7.115

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.744 1.175 5.855 36.105 37.780 38.865 34.930 37.036 10.554 10.688 ms 1.204 3.401

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.442 2.974 3.998 7.499 13.818 17.064 23.295 9.819 14.090 3.025 8.013 ms 10.35 33.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 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) 59.000 85.000 112.000 213.000 405.000 506.000 714.000 293.000 421.000 91.277 229.746 ns 9.127 30.35

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.810 -5.808 -5.805 -5.782 -5.766 -5.763 -5.761 0.039 0.045 0.0133 -5.782 ppm -8.338e+07 3.643e+10
Local Clock Time Offset -621.000 -412.000 -253.000 75.000 412.000 543.000 825.000 665.000 955.000 204.872 74.421 ns -2.137 5.5
Local RMS Frequency Jitter 19.000 28.000 32.000 50.000 78.000 93.000 110.000 46.000 65.000 13.973 51.622 10e-12 28.45 108.7
Local RMS Time Jitter 116.000 130.000 148.000 223.000 319.000 377.000 470.000 171.000 247.000 52.770 226.091 ns 45.88 192.6
Server Jitter 104.131.155.175 0.000 0.256 0.336 1.379 33.009 125.505 125.728 32.673 125.248 22.720 7.470 ms 2.173 13.07
Server Jitter 162.213.2.253 0.294 0.294 0.359 1.427 8.875 12.601 12.601 8.517 12.308 2.745 2.641 ms 1.555 4.838
Server Jitter 169.229.128.134 0.134 0.162 0.224 1.359 9.368 28.703 28.806 9.144 28.541 4.518 3.180 ms 2.237 13.33
Server Jitter 178.62.68.79 0.172 0.184 0.406 1.951 9.864 10.765 13.456 9.459 10.581 3.176 3.430 ms 1.257 3.241
Server Jitter 192.168.1.10 0.011 0.017 0.030 0.117 8.637 9.775 24.522 8.606 9.758 2.896 1.465 ms 0.8878 7.595
Server Jitter 203.123.48.219 0.213 0.227 0.282 1.074 9.264 9.973 10.422 8.982 9.747 2.960 2.382 ms 1.071 3.103
Server Jitter 204.17.205.24 0.130 0.191 0.245 1.364 10.122 14.165 14.175 9.878 13.974 3.180 2.577 ms 1.307 4.527
Server Jitter 66.220.9.122 0.156 0.188 0.217 0.949 7.498 12.319 12.357 7.281 12.132 2.415 1.877 ms 1.748 7.115
Server Jitter 76.14.161.109 0.529 0.744 1.175 5.855 36.105 37.780 38.865 34.930 37.036 10.554 10.688 ms 1.204 3.401
Server Jitter SHM(0) 1.442 2.974 3.998 7.499 13.818 17.064 23.295 9.819 14.090 3.025 8.013 ms 10.35 33.85
Server Jitter SHM(1) 59.000 85.000 112.000 213.000 405.000 506.000 714.000 293.000 421.000 91.277 229.746 ns 9.127 30.35
Server Offset 104.131.155.175 -0.273 -0.109 0.796 3.115 4.270 4.734 8.104 3.474 4.844 1.150 2.889 ms 8.089 26.36
Server Offset 162.213.2.253 1.972 1.972 2.001 2.243 2.583 2.886 2.886 0.582 0.914 0.182 2.263 ms 1540 1.807e+04
Server Offset 169.229.128.134 1.970 1.982 2.130 2.402 2.691 2.783 3.016 0.560 0.802 0.160 2.413 ms 2822 4.028e+04
Server Offset 178.62.68.79 -5.649 -5.135 -3.501 0.814 6.860 7.880 9.776 10.361 13.015 3.295 1.146 ms -2.031 4.312
Server Offset 192.168.1.10 -70.054 -2.838 12.159 48.913 76.907 86.071 96.455 64.748 88.909 20.971 47.591 µs 5.087 13.3
Server Offset 203.123.48.219 0.150 0.559 0.780 1.088 1.496 1.706 1.797 0.716 1.148 0.228 1.096 ms 66.84 303.8
Server Offset 204.17.205.24 1.277 1.286 1.421 1.721 2.042 2.211 2.283 0.621 0.925 0.193 1.716 ms 513.8 4247
Server Offset 66.220.9.122 2.079 2.143 2.240 2.481 2.725 2.910 2.946 0.486 0.767 0.149 2.490 ms 3939 6.271e+04
Server Offset 76.14.161.109 -3.584 -2.412 -1.683 -0.567 0.461 2.232 2.934 2.144 4.644 0.741 -0.568 ms -10.26 32.62
Server Offset SHM(0) -114.177 -107.361 -101.778 -87.431 -75.733 -71.990 -62.770 26.045 35.371 7.797 -87.908 ms -1886 2.362e+04
Server Offset SHM(1) -622.000 -413.000 -254.000 76.000 413.000 544.000 826.000 667.000 957.000 205.587 74.692 ns -2.141 5.498
TDOP 0.550 0.580 0.620 0.890 1.780 2.580 2.910 1.160 2.000 0.391 1.029 11.15 42.83
Temp ZONE0 57.996 58.534 59.072 59.072 60.148 60.148 60.148 1.076 1.614 0.404 59.354 °C
nSats 5.000 6.000 7.000 9.000 11.000 12.000 12.000 4.000 6.000 1.474 8.657 nSat 130.7 714.1
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!