NTPsec

A-ntpsec-12-hour-stats

Report generated: Sat May 31 23:07:08 2025 UTC
Start Time: Sat May 31 11:07:08 2025 UTC
End Time: Sat May 31 23:07:08 2025 UTC
Report published: Sat May 31 04:07:30 PM 2025 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 -6.264 -1.939 -1.255 0.089 1.150 1.915 12.393 2.405 3.854 0.864 0.047 µs -2.343 23.77
Local Clock Frequency Offset -296.631 -295.273 -294.189 -250.763 -92.773 -70.099 -61.005 201.416 225.174 63.871 -230.814 ppb -110.9 563.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.376 0.490 0.593 0.873 1.292 1.821 2.860 0.699 1.331 0.245 0.905 µs 29.55 128.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 0.158 0.200 0.233 0.334 0.507 1.378 3.322 0.274 1.178 0.208 0.367 ppb 10.24 106.1

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 -6.264 -1.939 -1.255 0.089 1.150 1.915 12.393 2.405 3.854 0.864 0.047 µs -2.343 23.77

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 -296.631 -295.273 -294.189 -250.763 -92.773 -70.099 -61.005 201.416 225.174 63.871 -230.814 ppb -110.9 563.5
Temp ZONE0 46.160 46.160 46.160 47.236 49.388 49.388 52.616 3.228 3.228 0.829 47.445 °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.036 9.836 nSat 638.1 5645
TDOP 0.510 0.550 0.600 0.810 1.220 1.430 1.650 0.620 0.880 0.199 0.851 45.98 196.9

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 5.423 5.532 5.664 6.323 8.295 8.438 8.492 2.631 2.906 0.740 6.533 ms 504.8 4170

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.519 0.519 0.970 1.500 2.028 4.103 4.103 1.058 3.583 0.445 1.517 ms 23.36 103.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 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.559 0.559 0.663 1.068 1.704 3.563 3.563 1.042 3.004 0.491 1.174 ms 9.447 42.06

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.270 0.452 0.574 1.040 1.678 3.042 3.166 1.103 2.590 0.433 1.113 ms 10.76 45.46

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.729 -4.718 -3.750 -2.206 1.583 3.233 3.512 5.333 7.951 1.628 -1.819 ms -14.68 41.54

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 1.475 1.572 1.745 2.318 2.973 4.666 4.833 1.228 3.093 0.529 2.402 ms 57.58 278.4

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 2.631 2.759 2.976 3.581 5.657 5.891 5.899 2.681 3.132 0.796 3.846 ms 68.91 325.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 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 1.969 2.053 2.414 3.601 4.602 5.563 5.740 2.188 3.510 0.656 3.599 ms 103.9 533.6

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 1.811 1.950 2.071 2.446 2.972 3.283 3.312 0.901 1.333 0.273 2.448 ms 530.3 4433

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.881 0.948 1.265 1.812 3.489 3.981 4.101 2.224 3.032 0.580 1.937 ms 21.65 87.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 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) -101.963 -100.470 -99.514 -96.926 -95.202 -94.442 -93.215 4.312 6.029 1.342 -97.150 ms -3.955e+05 2.905e+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) -6.265 -1.940 -1.256 0.090 1.151 1.916 12.394 2.407 3.856 0.865 0.047 µs -2.346 23.72

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.311 0.566 1.396 2.954 10.389 12.438 13.319 8.993 11.872 2.464 3.697 ms 3.586 12.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 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.629 0.629 0.865 1.510 8.402 16.639 16.639 7.537 16.010 2.912 2.230 ms 3.443 16.12

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.478 0.478 0.901 1.924 10.387 19.297 19.297 9.486 18.819 2.936 2.909 ms 3.498 17.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.837 1.062 1.431 2.618 5.385 13.345 13.363 3.954 12.283 1.689 3.035 ms 6.338 35.86

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 1.258 1.370 1.595 2.518 6.507 8.882 9.224 4.912 7.512 1.596 3.084 ms 5.467 19.47

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.702 1.017 1.276 3.147 30.631 35.036 42.007 29.355 34.019 7.397 5.672 ms 2.45 10.05

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.349 0.629 0.996 2.902 8.492 12.187 13.178 7.496 11.558 2.228 3.346 ms 3.552 13.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 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.308 0.579 0.764 1.428 2.939 11.475 14.281 2.175 10.896 1.489 1.732 ms 6.484 49.95

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.245 0.287 0.511 1.130 3.227 5.222 5.767 2.717 4.935 0.870 1.411 ms 4.234 16.83

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.879 0.907 1.143 2.627 8.071 10.223 10.329 6.928 9.317 1.956 3.308 ms 4.078 13.48

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.053 0.083 0.116 0.329 1.045 1.457 2.385 0.929 1.375 0.311 0.425 ms 2.82 10.11

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.169 0.316 0.442 0.854 1.775 2.835 8.617 1.333 2.519 0.552 0.967 µs 7.302 61.06

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 -296.631 -295.273 -294.189 -250.763 -92.773 -70.099 -61.005 201.416 225.174 63.871 -230.814 ppb -110.9 563.5
Local Clock Time Offset -6.264 -1.939 -1.255 0.089 1.150 1.915 12.393 2.405 3.854 0.864 0.047 µs -2.343 23.77
Local RMS Frequency Jitter 0.158 0.200 0.233 0.334 0.507 1.378 3.322 0.274 1.178 0.208 0.367 ppb 10.24 106.1
Local RMS Time Jitter 0.376 0.490 0.593 0.873 1.292 1.821 2.860 0.699 1.331 0.245 0.905 µs 29.55 128.7
Server Jitter 15.204.249.252 0.311 0.566 1.396 2.954 10.389 12.438 13.319 8.993 11.872 2.464 3.697 ms 3.586 12.43
Server Jitter 162.159.200.1 0.629 0.629 0.865 1.510 8.402 16.639 16.639 7.537 16.010 2.912 2.230 ms 3.443 16.12
Server Jitter 162.159.200.123 0.478 0.478 0.901 1.924 10.387 19.297 19.297 9.486 18.819 2.936 2.909 ms 3.498 17.7
Server Jitter 169.229.128.134 0.837 1.062 1.431 2.618 5.385 13.345 13.363 3.954 12.283 1.689 3.035 ms 6.338 35.86
Server Jitter 173.11.101.155 1.258 1.370 1.595 2.518 6.507 8.882 9.224 4.912 7.512 1.596 3.084 ms 5.467 19.47
Server Jitter 192.12.19.20 0.702 1.017 1.276 3.147 30.631 35.036 42.007 29.355 34.019 7.397 5.672 ms 2.45 10.05
Server Jitter 50.116.42.84 0.349 0.629 0.996 2.902 8.492 12.187 13.178 7.496 11.558 2.228 3.346 ms 3.552 13.01
Server Jitter 52.10.183.132 0.308 0.579 0.764 1.428 2.939 11.475 14.281 2.175 10.896 1.489 1.732 ms 6.484 49.95
Server Jitter 64.142.122.36 0.245 0.287 0.511 1.130 3.227 5.222 5.767 2.717 4.935 0.870 1.411 ms 4.234 16.83
Server Jitter 66.220.9.122 0.879 0.907 1.143 2.627 8.071 10.223 10.329 6.928 9.317 1.956 3.308 ms 4.078 13.48
Server Jitter SHM(0) 0.053 0.083 0.116 0.329 1.045 1.457 2.385 0.929 1.375 0.311 0.425 ms 2.82 10.11
Server Jitter SHM(1) 0.169 0.316 0.442 0.854 1.775 2.835 8.617 1.333 2.519 0.552 0.967 µs 7.302 61.06
Server Offset 15.204.249.252 5.423 5.532 5.664 6.323 8.295 8.438 8.492 2.631 2.906 0.740 6.533 ms 504.8 4170
Server Offset 162.159.200.1 0.519 0.519 0.970 1.500 2.028 4.103 4.103 1.058 3.583 0.445 1.517 ms 23.36 103.8
Server Offset 162.159.200.123 0.559 0.559 0.663 1.068 1.704 3.563 3.563 1.042 3.004 0.491 1.174 ms 9.447 42.06
Server Offset 169.229.128.134 0.270 0.452 0.574 1.040 1.678 3.042 3.166 1.103 2.590 0.433 1.113 ms 10.76 45.46
Server Offset 173.11.101.155 -4.729 -4.718 -3.750 -2.206 1.583 3.233 3.512 5.333 7.951 1.628 -1.819 ms -14.68 41.54
Server Offset 192.12.19.20 1.475 1.572 1.745 2.318 2.973 4.666 4.833 1.228 3.093 0.529 2.402 ms 57.58 278.4
Server Offset 50.116.42.84 2.631 2.759 2.976 3.581 5.657 5.891 5.899 2.681 3.132 0.796 3.846 ms 68.91 325.9
Server Offset 52.10.183.132 1.969 2.053 2.414 3.601 4.602 5.563 5.740 2.188 3.510 0.656 3.599 ms 103.9 533.6
Server Offset 64.142.122.36 1.811 1.950 2.071 2.446 2.972 3.283 3.312 0.901 1.333 0.273 2.448 ms 530.3 4433
Server Offset 66.220.9.122 0.881 0.948 1.265 1.812 3.489 3.981 4.101 2.224 3.032 0.580 1.937 ms 21.65 87.15
Server Offset SHM(0) -101.963 -100.470 -99.514 -96.926 -95.202 -94.442 -93.215 4.312 6.029 1.342 -97.150 ms -3.955e+05 2.905e+07
Server Offset SHM(1) -6.265 -1.940 -1.256 0.090 1.151 1.916 12.394 2.407 3.856 0.865 0.047 µs -2.346 23.72
TDOP 0.510 0.550 0.600 0.810 1.220 1.430 1.650 0.620 0.880 0.199 0.851 45.98 196.9
Temp ZONE0 46.160 46.160 46.160 47.236 49.388 49.388 52.616 3.228 3.228 0.829 47.445 °C
nSats 7.000 8.000 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.036 9.836 nSat 638.1 5645
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!