NTPsec

C-ntpsec-72-hour-stats

Report generated: Mon Dec 6 20:04:18 2021 UTC
Start Time: Fri Dec 3 20:04:16 2021 UTC
End Time: Mon Dec 6 20:04:16 2021 UTC
Report published: Mon Dec 06 12:04:30 2021 PST
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 -2,011.000 -855.000 -639.000 -31.000 664.000 977.000 2,139.000 1,303.000 1,832.000 399.887 -13.527 ns -3.95 9.748
Local Clock Frequency Offset -5.127 -5.121 -5.072 -4.948 -4.897 -4.891 -4.890 0.175 0.230 0.056 -4.963 ppm -7.072e+05 6.303e+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 92.000 116.000 134.000 189.000 282.000 360.000 563.000 148.000 244.000 48.450 196.057 ns 38.87 167

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 21.000 34.000 43.000 83.000 190.000 284.000 559.000 147.000 250.000 50.553 95.765 10e-12 5.604 24.78

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,011.000 -855.000 -639.000 -31.000 664.000 977.000 2,139.000 1,303.000 1,832.000 399.887 -13.527 ns -3.95 9.748

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.127 -5.121 -5.072 -4.948 -4.897 -4.891 -4.890 0.175 0.230 0.056 -4.963 ppm -7.072e+05 6.303e+07
Temp ZONE0 55.844 56.382 56.920 57.996 59.072 59.072 59.610 2.152 2.690 0.677 58.191 °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 11.000 12.000 13.000 4.000 5.000 1.157 9.136 nSat 349.4 2563
TDOP 0.470 0.530 0.600 0.820 1.390 1.540 2.160 0.790 1.010 0.235 0.877 29.92 117.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. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



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 162.159.200.123

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 2.533 2.635 2.803 3.029 3.293 3.466 4.599 0.491 0.831 0.171 3.045 ms 4762 8.078e+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 0.505 2.115 2.263 2.456 2.698 2.884 3.146 0.435 0.769 0.177 2.459 ms 2190 2.869e+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 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 -2.657 -1.438 -0.766 0.023 0.552 1.077 1.899 1.318 2.515 0.434 -0.019 ms -5.346 20.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 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 -93.535 25.341 86.606 160.103 226.451 271.098 367.624 139.845 245.757 44.152 158.237 µs 24.67 86.18

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 194.58.202.211

peer offset 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.211 5.758 5.926 6.371 7.294 7.559 7.715 8.212 1.188 1.788 0.326 7.248 ms 9597 2.047e+05

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

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

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

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



Server Offset 194.58.202.219

peer offset 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.219 4.758 5.157 5.230 5.446 7.064 7.548 7.706 1.834 2.391 0.459 5.551 ms 1398 1.599e+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 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 3.053 3.053 3.095 3.295 3.498 3.641 3.641 0.403 0.588 0.124 3.300 ms 1.691e+04 4.354e+05

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

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

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

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



Server Offset 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.375 1.059 1.352 1.780 2.224 2.440 2.832 0.872 1.381 0.267 1.786 ms 202.1 1251

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

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.254.202 1.140 2.285 2.459 2.649 2.888 2.962 3.201 0.430 0.677 0.160 2.650 ms 3787 5.942e+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 63.145.169.3

peer offset 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 63.145.169.3 -85.575 -69.030 -57.046 0.645 1.272 3.241 5.241 58.319 72.271 22.966 -15.772 ms -10.8 33.78

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) -70.700 -66.281 -63.480 -55.593 -48.003 -45.702 -42.736 15.477 20.578 4.690 -55.549 ms -2157 2.821e+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,012.000 -856.000 -640.000 -32.000 665.000 978.000 2,140.000 1,305.000 1,834.000 400.651 -13.591 ns -3.951 9.742

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 162.159.200.123

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.100 0.130 0.192 0.724 3.146 4.539 15.738 2.954 4.409 1.145 1.070 ms 4.364 42.43

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.074 0.117 0.199 0.997 3.150 4.614 19.041 2.951 4.497 1.606 1.260 ms 7.23 78.59

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.267 0.434 0.817 1.674 3.500 10.202 26.207 2.683 9.768 1.670 1.948 ms 7.92 86.5

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.017 0.040 0.060 0.146 0.525 1.155 2.847 0.466 1.114 0.204 0.195 ms 4.834 37.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 194.58.202.211

peer jitter 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.211 0.052 0.146 0.229 0.970 3.581 6.328 18.856 3.352 6.182 1.787 1.348 ms 5.578 50.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.



Server Jitter 194.58.202.219

peer jitter 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.219 0.000 0.135 0.199 0.813 3.424 5.480 10.683 3.225 5.345 1.243 1.158 ms 3.306 20.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.



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.169 0.169 0.333 1.005 2.705 3.351 3.351 2.372 3.181 0.705 1.114 ms 3.217 9.588

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.220 0.286 0.362 0.879 3.309 4.888 19.440 2.947 4.602 1.503 1.241 ms 6.827 73.13

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

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.254.202 0.109 0.136 0.225 1.039 3.547 5.547 14.019 3.322 5.410 1.418 1.359 ms 4.65 37.13

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 63.145.169.3

peer jitter 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 63.145.169.3 0.000 0.186 0.901 22.889 59.725 88.888 98.264 58.824 88.701 19.250 25.151 ms 1.893 5.743

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.064 0.215 0.340 0.973 3.114 5.785 10.625 2.773 5.570 1.022 1.255 ms 3.438 15.92

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 78.000 106.000 227.000 531.000 729.000 1,664.000 425.000 651.000 141.256 262.245 ns 4.947 19.56

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.127 -5.121 -5.072 -4.948 -4.897 -4.891 -4.890 0.175 0.230 0.056 -4.963 ppm -7.072e+05 6.303e+07
Local Clock Time Offset -2,011.000 -855.000 -639.000 -31.000 664.000 977.000 2,139.000 1,303.000 1,832.000 399.887 -13.527 ns -3.95 9.748
Local RMS Frequency Jitter 21.000 34.000 43.000 83.000 190.000 284.000 559.000 147.000 250.000 50.553 95.765 10e-12 5.604 24.78
Local RMS Time Jitter 92.000 116.000 134.000 189.000 282.000 360.000 563.000 148.000 244.000 48.450 196.057 ns 38.87 167
Server Jitter 162.159.200.123 0.100 0.130 0.192 0.724 3.146 4.539 15.738 2.954 4.409 1.145 1.070 ms 4.364 42.43
Server Jitter 169.229.128.134 0.074 0.117 0.199 0.997 3.150 4.614 19.041 2.951 4.497 1.606 1.260 ms 7.23 78.59
Server Jitter 173.11.101.155 0.267 0.434 0.817 1.674 3.500 10.202 26.207 2.683 9.768 1.670 1.948 ms 7.92 86.5
Server Jitter 192.168.1.10 0.017 0.040 0.060 0.146 0.525 1.155 2.847 0.466 1.114 0.204 0.195 ms 4.834 37.2
Server Jitter 194.58.202.211 0.052 0.146 0.229 0.970 3.581 6.328 18.856 3.352 6.182 1.787 1.348 ms 5.578 50.73
Server Jitter 194.58.202.219 0.000 0.135 0.199 0.813 3.424 5.480 10.683 3.225 5.345 1.243 1.158 ms 3.306 20.73
Server Jitter 203.123.48.219 0.169 0.169 0.333 1.005 2.705 3.351 3.351 2.372 3.181 0.705 1.114 ms 3.217 9.588
Server Jitter 204.17.205.24 0.220 0.286 0.362 0.879 3.309 4.888 19.440 2.947 4.602 1.503 1.241 ms 6.827 73.13
Server Jitter 216.218.254.202 0.109 0.136 0.225 1.039 3.547 5.547 14.019 3.322 5.410 1.418 1.359 ms 4.65 37.13
Server Jitter 63.145.169.3 0.000 0.186 0.901 22.889 59.725 88.888 98.264 58.824 88.701 19.250 25.151 ms 1.893 5.743
Server Jitter SHM(0) 0.064 0.215 0.340 0.973 3.114 5.785 10.625 2.773 5.570 1.022 1.255 ms 3.438 15.92
Server Jitter SHM(1) 27.000 78.000 106.000 227.000 531.000 729.000 1,664.000 425.000 651.000 141.256 262.245 ns 4.947 19.56
Server Offset 162.159.200.123 2.533 2.635 2.803 3.029 3.293 3.466 4.599 0.491 0.831 0.171 3.045 ms 4762 8.078e+04
Server Offset 169.229.128.134 0.505 2.115 2.263 2.456 2.698 2.884 3.146 0.435 0.769 0.177 2.459 ms 2190 2.869e+04
Server Offset 173.11.101.155 -2.657 -1.438 -0.766 0.023 0.552 1.077 1.899 1.318 2.515 0.434 -0.019 ms -5.346 20.9
Server Offset 192.168.1.10 -93.535 25.341 86.606 160.103 226.451 271.098 367.624 139.845 245.757 44.152 158.237 µs 24.67 86.18
Server Offset 194.58.202.211 5.758 5.926 6.371 7.294 7.559 7.715 8.212 1.188 1.788 0.326 7.248 ms 9597 2.047e+05
Server Offset 194.58.202.219 4.758 5.157 5.230 5.446 7.064 7.548 7.706 1.834 2.391 0.459 5.551 ms 1398 1.599e+04
Server Offset 203.123.48.219 3.053 3.053 3.095 3.295 3.498 3.641 3.641 0.403 0.588 0.124 3.300 ms 1.691e+04 4.354e+05
Server Offset 204.17.205.24 0.375 1.059 1.352 1.780 2.224 2.440 2.832 0.872 1.381 0.267 1.786 ms 202.1 1251
Server Offset 216.218.254.202 1.140 2.285 2.459 2.649 2.888 2.962 3.201 0.430 0.677 0.160 2.650 ms 3787 5.942e+04
Server Offset 63.145.169.3 -85.575 -69.030 -57.046 0.645 1.272 3.241 5.241 58.319 72.271 22.966 -15.772 ms -10.8 33.78
Server Offset SHM(0) -70.700 -66.281 -63.480 -55.593 -48.003 -45.702 -42.736 15.477 20.578 4.690 -55.549 ms -2157 2.821e+04
Server Offset SHM(1) -2,012.000 -856.000 -640.000 -32.000 665.000 978.000 2,140.000 1,305.000 1,834.000 400.651 -13.591 ns -3.951 9.742
TDOP 0.470 0.530 0.600 0.820 1.390 1.540 2.160 0.790 1.010 0.235 0.877 29.92 117.8
Temp ZONE0 55.844 56.382 56.920 57.996 59.072 59.072 59.610 2.152 2.690 0.677 58.191 °C
nSats 6.000 7.000 7.000 9.000 11.000 12.000 13.000 4.000 5.000 1.157 9.136 nSat 349.4 2563
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!