NTPsec

A-ntpsec-24-hour-stats

Report generated: Sat May 28 16:03:13 2022 UTC
Start Time: Fri May 27 16:03:12 2022 UTC
End Time: Sat May 28 16:03:12 2022 UTC
Report published: Sat May 28 09:03:21 2022 PDT
Report Period: 1.0 days

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -1.376 -0.909 -0.650 0.026 0.721 1.024 1.762 1.371 1.933 0.416 0.026 µs -3.541 8.711
Local Clock Frequency Offset -99.655 -98.129 -95.261 -71.152 -51.331 -50.262 -49.850 43.930 47.867 15.696 -72.868 ppb -196.7 1210

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 243.000 320.000 361.000 507.000 697.000 784.000 940.000 336.000 464.000 101.515 514.930 ns 80.24 385.7

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 51.000 61.000 70.000 97.000 138.000 175.000 238.000 68.000 114.000 22.300 99.807 10e-12 53.73 243.4

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

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

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



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -1.376 -0.909 -0.650 0.026 0.721 1.024 1.762 1.371 1.933 0.416 0.026 µs -3.541 8.711

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 -99.655 -98.129 -95.261 -71.152 -51.331 -50.262 -49.850 43.930 47.867 15.696 -72.868 ppb -196.7 1210
Temp ZONE0 51.540 51.540 52.078 52.616 53.692 53.692 54.230 1.614 2.152 0.568 52.770 °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 8.000 10.000 12.000 12.000 12.000 4.000 5.000 0.998 9.594 nSat 664.1 5946
TDOP 0.490 0.530 0.590 0.820 1.380 1.490 1.860 0.790 0.960 0.225 0.867 32.71 131.2

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

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 4.413 4.561 4.848 5.100 5.579 8.350 10.754 0.731 3.789 0.616 5.198 ms 439.4 3608

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.029 2.067 2.207 2.436 2.688 5.798 7.299 0.481 3.731 0.557 2.508 ms 59.42 351.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 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.082 -1.586 -0.897 -0.029 1.174 3.855 5.307 2.071 5.441 0.835 0.055 ms -0.5129 12.15

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

peer offset 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.11 -211.573 -138.239 -118.426 -44.442 28.034 39.519 229.171 146.460 177.758 46.500 -44.159 µs -13 39.48

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

peer offset 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.12 -228.042 -182.437 -158.354 -80.987 18.273 61.411 118.204 176.627 243.848 53.545 -73.355 µs -20.17 65.76

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

peer offset 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.79 4.992 5.256 5.355 5.637 5.937 6.645 7.102 0.582 1.389 0.212 5.652 ms 1.685e+04 4.336e+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.207.80

peer offset 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.80 5.463 7.202 7.305 7.568 8.341 11.544 14.117 1.036 4.343 0.758 7.708 ms 803.8 7789

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.993 0.993 1.393 1.706 2.075 3.235 3.235 0.683 2.243 0.276 1.717 ms 159.7 964.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 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 2.251 2.274 2.390 2.607 2.950 4.896 6.097 0.560 2.622 0.398 2.670 ms 208.3 1418

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 2.220 2.289 2.392 2.569 2.854 6.069 10.090 0.462 3.780 0.705 2.678 ms 38.46 278

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) -58.468 -55.309 -54.061 -48.850 -44.414 -42.777 -40.276 9.646 12.532 2.877 -49.020 ms -5927 1.079e+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 SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -1.377 -0.910 -0.651 0.027 0.722 1.025 1.763 1.373 1.935 0.417 0.026 µs -3.542 8.706

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

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.153 0.172 0.218 0.832 7.984 19.488 20.595 7.766 19.316 3.467 1.860 ms 2.268 11.68

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.104 0.162 0.225 0.886 9.521 20.017 129.548 9.295 19.855 8.105 2.300 ms 10.42 165.4

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.280 0.599 0.924 1.581 13.700 17.792 19.124 12.777 17.193 3.327 2.500 ms 2.891 12.31

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

peer jitter 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.11 11.075 26.345 41.999 109.113 573.810 764.635 2,812.386 531.811 738.290 209.522 169.269 µs 5.697 61.99

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

peer jitter 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.12 18.221 27.054 42.933 114.529 666.462 910.324 1,712.944 623.529 883.270 213.494 191.057 µs 2.769 14.49

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

peer jitter 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.79 0.108 0.175 0.205 0.917 10.349 34.690 193.243 10.144 34.515 16.243 3.393 ms 7.892 94.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 194.58.207.80

peer jitter 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.80 0.141 0.190 0.246 0.784 13.114 17.861 29.377 12.868 17.671 3.872 2.021 ms 2.01 11.52

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.188 0.188 0.309 0.855 12.322 16.476 16.476 12.013 16.288 3.834 2.333 ms 1.311 5.444

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.176 0.194 0.271 1.062 5.876 18.283 23.400 5.605 18.088 2.584 1.581 ms 4.299 31.22

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.145 0.177 0.256 0.998 6.213 17.834 18.158 5.958 17.657 2.825 1.718 ms 2.718 14.61

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.074 0.159 0.273 0.884 2.286 3.210 4.518 2.014 3.051 0.641 1.029 ms 3.364 10.79

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) 0.094 0.199 0.260 0.470 0.882 1.101 1.612 0.622 0.902 0.194 0.507 µs 10.17 34.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 -99.655 -98.129 -95.261 -71.152 -51.331 -50.262 -49.850 43.930 47.867 15.696 -72.868 ppb -196.7 1210
Local Clock Time Offset -1.376 -0.909 -0.650 0.026 0.721 1.024 1.762 1.371 1.933 0.416 0.026 µs -3.541 8.711
Local RMS Frequency Jitter 51.000 61.000 70.000 97.000 138.000 175.000 238.000 68.000 114.000 22.300 99.807 10e-12 53.73 243.4
Local RMS Time Jitter 243.000 320.000 361.000 507.000 697.000 784.000 940.000 336.000 464.000 101.515 514.930 ns 80.24 385.7
Server Jitter 162.159.200.1 0.153 0.172 0.218 0.832 7.984 19.488 20.595 7.766 19.316 3.467 1.860 ms 2.268 11.68
Server Jitter 169.229.128.134 0.104 0.162 0.225 0.886 9.521 20.017 129.548 9.295 19.855 8.105 2.300 ms 10.42 165.4
Server Jitter 173.11.101.155 0.280 0.599 0.924 1.581 13.700 17.792 19.124 12.777 17.193 3.327 2.500 ms 2.891 12.31
Server Jitter 192.168.1.11 11.075 26.345 41.999 109.113 573.810 764.635 2,812.386 531.811 738.290 209.522 169.269 µs 5.697 61.99
Server Jitter 192.168.1.12 18.221 27.054 42.933 114.529 666.462 910.324 1,712.944 623.529 883.270 213.494 191.057 µs 2.769 14.49
Server Jitter 194.58.207.79 0.108 0.175 0.205 0.917 10.349 34.690 193.243 10.144 34.515 16.243 3.393 ms 7.892 94.92
Server Jitter 194.58.207.80 0.141 0.190 0.246 0.784 13.114 17.861 29.377 12.868 17.671 3.872 2.021 ms 2.01 11.52
Server Jitter 204.17.205.24 0.188 0.188 0.309 0.855 12.322 16.476 16.476 12.013 16.288 3.834 2.333 ms 1.311 5.444
Server Jitter 216.218.192.202 0.176 0.194 0.271 1.062 5.876 18.283 23.400 5.605 18.088 2.584 1.581 ms 4.299 31.22
Server Jitter 216.218.254.202 0.145 0.177 0.256 0.998 6.213 17.834 18.158 5.958 17.657 2.825 1.718 ms 2.718 14.61
Server Jitter SHM(0) 0.074 0.159 0.273 0.884 2.286 3.210 4.518 2.014 3.051 0.641 1.029 ms 3.364 10.79
Server Jitter SHM(1) 0.094 0.199 0.260 0.470 0.882 1.101 1.612 0.622 0.902 0.194 0.507 µs 10.17 34.35
Server Offset 162.159.200.1 4.413 4.561 4.848 5.100 5.579 8.350 10.754 0.731 3.789 0.616 5.198 ms 439.4 3608
Server Offset 169.229.128.134 1.029 2.067 2.207 2.436 2.688 5.798 7.299 0.481 3.731 0.557 2.508 ms 59.42 351.3
Server Offset 173.11.101.155 -2.082 -1.586 -0.897 -0.029 1.174 3.855 5.307 2.071 5.441 0.835 0.055 ms -0.5129 12.15
Server Offset 192.168.1.11 -211.573 -138.239 -118.426 -44.442 28.034 39.519 229.171 146.460 177.758 46.500 -44.159 µs -13 39.48
Server Offset 192.168.1.12 -228.042 -182.437 -158.354 -80.987 18.273 61.411 118.204 176.627 243.848 53.545 -73.355 µs -20.17 65.76
Server Offset 194.58.207.79 4.992 5.256 5.355 5.637 5.937 6.645 7.102 0.582 1.389 0.212 5.652 ms 1.685e+04 4.336e+05
Server Offset 194.58.207.80 5.463 7.202 7.305 7.568 8.341 11.544 14.117 1.036 4.343 0.758 7.708 ms 803.8 7789
Server Offset 204.17.205.24 0.993 0.993 1.393 1.706 2.075 3.235 3.235 0.683 2.243 0.276 1.717 ms 159.7 964.8
Server Offset 216.218.192.202 2.251 2.274 2.390 2.607 2.950 4.896 6.097 0.560 2.622 0.398 2.670 ms 208.3 1418
Server Offset 216.218.254.202 2.220 2.289 2.392 2.569 2.854 6.069 10.090 0.462 3.780 0.705 2.678 ms 38.46 278
Server Offset SHM(0) -58.468 -55.309 -54.061 -48.850 -44.414 -42.777 -40.276 9.646 12.532 2.877 -49.020 ms -5927 1.079e+05
Server Offset SHM(1) -1.377 -0.910 -0.651 0.027 0.722 1.025 1.763 1.373 1.935 0.417 0.026 µs -3.542 8.706
TDOP 0.490 0.530 0.590 0.820 1.380 1.490 1.860 0.790 0.960 0.225 0.867 32.71 131.2
Temp ZONE0 51.540 51.540 52.078 52.616 53.692 53.692 54.230 1.614 2.152 0.568 52.770 °C
nSats 6.000 7.000 8.000 10.000 12.000 12.000 12.000 4.000 5.000 0.998 9.594 nSat 664.1 5946
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!