NTPsec

A-ntpsec-7-day-stats

Report generated: Tue Mar 25 12:10:04 2025 UTC
Start Time: Tue Mar 18 12:10:01 2025 UTC
End Time: Tue Mar 25 12:10:01 2025 UTC
Report published: Tue Mar 25 05:10:23 AM 2025 PDT
Report Period: 7.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 -4.003 -1.969 -1.368 0.033 1.297 1.840 4.477 2.665 3.809 0.809 0.009 µs -4.068 10.48
Local Clock Frequency Offset -621.521 -616.226 -558.716 -331.711 -136.459 -65.704 -60.776 422.257 550.522 123.848 -344.325 ppb -65.42 293.5

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 0.327 0.547 0.650 0.960 1.401 1.633 2.302 0.751 1.086 0.231 0.984 µs 45.27 189.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 150.000 217.000 258.000 380.000 536.000 617.000 1,068.000 278.000 400.000 85.639 386.072 10e-12 54.23 236.5

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 -4.003 -1.969 -1.368 0.033 1.297 1.840 4.477 2.665 3.809 0.809 0.009 µs -4.068 10.48

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 -621.521 -616.226 -558.716 -331.711 -136.459 -65.704 -60.776 422.257 550.522 123.848 -344.325 ppb -65.42 293.5
Temp ZONE0 42.932 44.008 44.008 46.160 48.312 49.388 49.926 4.304 5.380 1.260 46.344 °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 7.000 8.000 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.059 9.866 nSat 600.1 5208
TDOP 0.490 0.500 0.550 0.790 1.230 1.410 1.710 0.680 0.910 0.197 0.821 42.55 179

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 15.204.249.252

peer offset 15.204.249.252 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 15.204.249.252 2.700 3.404 4.355 5.082 6.200 7.987 9.638 1.845 4.584 0.761 5.230 ms 221.4 1430

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

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

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

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



Server Offset 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 0.723 1.437 1.655 2.258 3.115 3.494 4.175 1.460 2.057 0.464 2.309 ms 75.15 356

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.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 0.036 0.701 0.929 2.107 3.146 3.726 4.815 2.217 3.025 0.722 2.001 ms 11.07 32.73

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.108 1.181 1.436 1.880 2.862 3.628 5.202 1.426 2.447 0.582 2.102 ms 26.06 97.11

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 -4.124 -2.735 -1.665 0.592 2.694 3.676 5.096 4.359 6.410 1.364 0.563 ms -2.038 5.518

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

peer offset 192.12.19.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.12.19.20 -0.375 1.741 2.162 2.684 3.691 4.100 7.513 1.529 2.358 0.578 2.890 ms 76.22 363

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 50.116.42.84

peer offset 50.116.42.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.116.42.84 1.786 2.229 2.545 3.568 4.695 5.008 8.838 2.150 2.780 0.702 3.606 ms 83.48 403.7

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 52.10.183.132

peer offset 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 52.10.183.132 2.502 3.186 3.482 4.397 5.491 6.074 8.721 2.009 2.888 0.650 4.452 ms 218.5 1392

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 64.142.122.36

peer offset 64.142.122.36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.142.122.36 -0.723 1.099 1.338 1.802 2.756 3.184 4.801 1.418 2.085 0.562 2.004 ms 25.09 93.77

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

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

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

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



Server Offset 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 -0.262 1.550 1.853 2.308 3.307 3.374 4.338 1.453 1.823 0.531 2.502 ms 62.17 275

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) -102.727 -101.107 -99.764 -97.057 -95.250 -94.644 -93.001 4.514 6.463 1.399 -97.274 ms -3.507e+05 2.474e+07

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) -4.004 -1.970 -1.369 0.034 1.298 1.841 4.478 2.667 3.811 0.810 0.009 µs -4.068 10.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 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 15.204.249.252

peer jitter 15.204.249.252 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 15.204.249.252 0.090 0.227 0.359 1.555 4.287 12.728 20.895 3.927 12.501 2.171 1.987 ms 4.421 28.3

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.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.180 0.329 0.675 1.720 5.354 13.730 21.264 4.680 13.402 2.298 2.209 ms 4.641 30.53

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.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.114 0.208 0.416 1.704 3.531 9.075 24.012 3.115 8.867 1.697 1.931 ms 7.215 76.62

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.135 0.239 0.599 1.811 4.921 11.887 46.822 4.322 11.648 2.455 2.262 ms 8.92 135.9

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.496 1.174 1.666 3.129 6.766 11.336 23.649 5.100 10.162 1.856 3.506 ms 6.593 38.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 192.12.19.20

peer jitter 192.12.19.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.12.19.20 0.000 0.234 0.511 1.597 16.417 34.569 50.259 15.906 34.335 5.920 3.391 ms 2.605 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 50.116.42.84

peer jitter 50.116.42.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.116.42.84 0.154 0.250 0.436 1.621 3.895 10.222 18.153 3.458 9.972 1.742 1.942 ms 5.1 36.23

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 52.10.183.132

peer jitter 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 52.10.183.132 0.141 0.236 0.423 1.520 4.441 12.219 18.714 4.018 11.983 1.971 1.967 ms 4.399 27.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 64.142.122.36

peer jitter 64.142.122.36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.142.122.36 0.083 0.211 0.355 1.590 6.090 11.573 118.194 5.735 11.362 5.471 2.351 ms 14.64 282.3

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.080 0.165 0.249 1.048 3.317 9.784 14.873 3.068 9.620 1.524 1.396 ms 4.651 33.36

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(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.039 0.080 0.110 0.306 0.975 1.373 3.078 0.864 1.293 0.287 0.396 ms 2.843 10.01

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.115 0.364 0.496 0.975 1.930 2.460 4.832 1.434 2.096 0.449 1.063 µs 7.818 25.97

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 -621.521 -616.226 -558.716 -331.711 -136.459 -65.704 -60.776 422.257 550.522 123.848 -344.325 ppb -65.42 293.5
Local Clock Time Offset -4.003 -1.969 -1.368 0.033 1.297 1.840 4.477 2.665 3.809 0.809 0.009 µs -4.068 10.48
Local RMS Frequency Jitter 150.000 217.000 258.000 380.000 536.000 617.000 1,068.000 278.000 400.000 85.639 386.072 10e-12 54.23 236.5
Local RMS Time Jitter 0.327 0.547 0.650 0.960 1.401 1.633 2.302 0.751 1.086 0.231 0.984 µs 45.27 189.6
Server Jitter 15.204.249.252 0.090 0.227 0.359 1.555 4.287 12.728 20.895 3.927 12.501 2.171 1.987 ms 4.421 28.3
Server Jitter 162.159.200.1 0.180 0.329 0.675 1.720 5.354 13.730 21.264 4.680 13.402 2.298 2.209 ms 4.641 30.53
Server Jitter 162.159.200.123 0.114 0.208 0.416 1.704 3.531 9.075 24.012 3.115 8.867 1.697 1.931 ms 7.215 76.62
Server Jitter 169.229.128.134 0.135 0.239 0.599 1.811 4.921 11.887 46.822 4.322 11.648 2.455 2.262 ms 8.92 135.9
Server Jitter 173.11.101.155 0.496 1.174 1.666 3.129 6.766 11.336 23.649 5.100 10.162 1.856 3.506 ms 6.593 38.77
Server Jitter 192.12.19.20 0.000 0.234 0.511 1.597 16.417 34.569 50.259 15.906 34.335 5.920 3.391 ms 2.605 14.61
Server Jitter 50.116.42.84 0.154 0.250 0.436 1.621 3.895 10.222 18.153 3.458 9.972 1.742 1.942 ms 5.1 36.23
Server Jitter 52.10.183.132 0.141 0.236 0.423 1.520 4.441 12.219 18.714 4.018 11.983 1.971 1.967 ms 4.399 27.85
Server Jitter 64.142.122.36 0.083 0.211 0.355 1.590 6.090 11.573 118.194 5.735 11.362 5.471 2.351 ms 14.64 282.3
Server Jitter 66.220.9.122 0.080 0.165 0.249 1.048 3.317 9.784 14.873 3.068 9.620 1.524 1.396 ms 4.651 33.36
Server Jitter SHM(0) 0.039 0.080 0.110 0.306 0.975 1.373 3.078 0.864 1.293 0.287 0.396 ms 2.843 10.01
Server Jitter SHM(1) 0.115 0.364 0.496 0.975 1.930 2.460 4.832 1.434 2.096 0.449 1.063 µs 7.818 25.97
Server Offset 15.204.249.252 2.700 3.404 4.355 5.082 6.200 7.987 9.638 1.845 4.584 0.761 5.230 ms 221.4 1430
Server Offset 162.159.200.1 0.723 1.437 1.655 2.258 3.115 3.494 4.175 1.460 2.057 0.464 2.309 ms 75.15 356
Server Offset 162.159.200.123 0.036 0.701 0.929 2.107 3.146 3.726 4.815 2.217 3.025 0.722 2.001 ms 11.07 32.73
Server Offset 169.229.128.134 -1.108 1.181 1.436 1.880 2.862 3.628 5.202 1.426 2.447 0.582 2.102 ms 26.06 97.11
Server Offset 173.11.101.155 -4.124 -2.735 -1.665 0.592 2.694 3.676 5.096 4.359 6.410 1.364 0.563 ms -2.038 5.518
Server Offset 192.12.19.20 -0.375 1.741 2.162 2.684 3.691 4.100 7.513 1.529 2.358 0.578 2.890 ms 76.22 363
Server Offset 50.116.42.84 1.786 2.229 2.545 3.568 4.695 5.008 8.838 2.150 2.780 0.702 3.606 ms 83.48 403.7
Server Offset 52.10.183.132 2.502 3.186 3.482 4.397 5.491 6.074 8.721 2.009 2.888 0.650 4.452 ms 218.5 1392
Server Offset 64.142.122.36 -0.723 1.099 1.338 1.802 2.756 3.184 4.801 1.418 2.085 0.562 2.004 ms 25.09 93.77
Server Offset 66.220.9.122 -0.262 1.550 1.853 2.308 3.307 3.374 4.338 1.453 1.823 0.531 2.502 ms 62.17 275
Server Offset SHM(0) -102.727 -101.107 -99.764 -97.057 -95.250 -94.644 -93.001 4.514 6.463 1.399 -97.274 ms -3.507e+05 2.474e+07
Server Offset SHM(1) -4.004 -1.970 -1.369 0.034 1.298 1.841 4.478 2.667 3.811 0.810 0.009 µs -4.068 10.48
TDOP 0.490 0.500 0.550 0.790 1.230 1.410 1.710 0.680 0.910 0.197 0.821 42.55 179
Temp ZONE0 42.932 44.008 44.008 46.160 48.312 49.388 49.926 4.304 5.380 1.260 46.344 °C
nSats 7.000 8.000 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.059 9.866 nSat 600.1 5208
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!