NTPsec

A-ntpsec-12-hour-stats

Report generated: Tue May 20 05:07:03 2025 UTC
Start Time: Mon May 19 17:07:02 2025 UTC
End Time: Tue May 20 05:07:02 2025 UTC
Report published: Mon May 19 10:07:19 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 -2.726 -1.822 -1.202 0.148 1.166 1.561 2.764 2.368 3.383 0.713 0.092 µs -3.686 9.96
Local Clock Frequency Offset -289.413 -288.498 -280.838 -137.146 -40.939 -39.627 -37.796 239.899 248.871 85.368 -147.370 ppb -28.67 103.9

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.362 0.516 0.610 0.880 1.272 1.468 1.952 0.662 0.952 0.204 0.903 µs 51.18 220.8

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 159.000 198.000 239.000 337.000 469.000 538.000 667.000 230.000 340.000 71.782 343.806 10e-12 66.34 304.3

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.726 -1.822 -1.202 0.148 1.166 1.561 2.764 2.368 3.383 0.713 0.092 µs -3.686 9.96

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 -289.413 -288.498 -280.838 -137.146 -40.939 -39.627 -37.796 239.899 248.871 85.368 -147.370 ppb -28.67 103.9
Temp ZONE0 46.160 46.160 47.236 48.312 49.926 49.926 50.464 2.690 3.766 0.983 48.484 °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 11.000 12.000 12.000 3.000 4.000 0.975 9.594 nSat 716.4 6571
TDOP 0.540 0.540 0.590 0.810 1.260 1.330 1.540 0.670 0.790 0.208 0.857 40.34 164.3

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 3.144 3.189 3.738 4.554 6.989 10.000 13.899 3.251 6.811 1.354 4.982 ms 30.11 140.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 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.915 0.915 0.915 1.604 3.396 3.396 3.396 2.482 2.482 0.692 1.570 ms 7.504 25.68

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.405 0.259 0.402 1.202 3.165 4.457 5.759 2.763 4.197 0.863 1.399 ms 4.025 15.53

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.901 -0.754 1.601 2.378 3.241 5.458 5.574 1.640 6.212 0.752 2.395 ms 16.68 63.92

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 -7.520 -5.124 -4.189 -2.101 1.294 4.773 5.090 5.483 9.898 1.847 -1.806 ms -12.84 36.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.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.257 0.764 2.017 2.680 4.349 5.342 6.703 2.332 4.577 0.799 2.811 ms 24.76 98.61

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 0.629 0.932 1.329 2.243 4.228 6.179 6.631 2.898 5.248 0.928 2.453 ms 10.94 40.62

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

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

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

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



Server Offset 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.224 2.252 3.100 3.900 7.688 10.001 10.886 4.588 7.749 1.572 4.538 ms 13.95 51.12

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.440 0.517 1.571 2.131 3.287 6.614 6.634 1.716 6.097 0.773 2.223 ms 15.74 80.08

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 -8.637 -0.114 0.849 2.609 3.667 6.819 6.883 2.818 6.933 1.350 2.477 ms -0.4414 28.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 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.102 -100.241 -99.321 -96.742 -94.803 -94.266 -93.359 4.517 5.974 1.320 -96.834 ms -4.111e+05 3.057e+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) -2.727 -1.823 -1.203 0.149 1.167 1.562 2.765 2.370 3.385 0.713 0.092 µs -3.686 9.953

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.355 0.819 1.100 2.753 14.932 24.073 82.167 13.833 23.253 7.546 5.141 ms 6.093 61.72

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 1.369 1.369 1.369 2.174 6.075 6.075 6.075 4.706 4.706 1.315 2.572 ms 5.479 18.15

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.814 0.934 1.146 3.428 20.123 32.058 32.448 18.977 31.124 6.462 5.929 ms 1.926 7.109

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.551 0.732 1.167 3.717 24.771 38.029 38.391 23.603 37.297 7.518 7.074 ms 1.891 7.256

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.978 1.255 1.616 4.079 17.874 21.350 22.336 16.258 20.095 4.646 5.756 ms 2.425 7.384

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.555 0.770 1.159 3.331 24.815 34.767 35.183 23.657 33.997 8.038 7.370 ms 1.292 3.945

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.578 0.596 0.995 3.133 20.032 38.416 38.483 19.037 37.820 6.856 5.912 ms 1.975 8.328

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.764 0.879 1.076 3.225 20.666 30.698 31.289 19.589 29.819 6.935 6.350 ms 1.587 5.401

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.319 0.759 1.114 2.951 16.577 22.731 31.663 15.463 21.972 5.527 5.816 ms 1.761 6.204

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.690 0.714 0.922 3.119 21.282 30.963 32.512 20.360 30.249 6.953 6.392 ms 1.478 5.018

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.050 0.077 0.110 0.299 0.991 1.392 2.897 0.881 1.315 0.296 0.397 ms 2.709 9.745

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.183 0.318 0.443 0.873 1.698 2.278 3.100 1.255 1.960 0.400 0.947 µs 7.874 26.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -289.413 -288.498 -280.838 -137.146 -40.939 -39.627 -37.796 239.899 248.871 85.368 -147.370 ppb -28.67 103.9
Local Clock Time Offset -2.726 -1.822 -1.202 0.148 1.166 1.561 2.764 2.368 3.383 0.713 0.092 µs -3.686 9.96
Local RMS Frequency Jitter 159.000 198.000 239.000 337.000 469.000 538.000 667.000 230.000 340.000 71.782 343.806 10e-12 66.34 304.3
Local RMS Time Jitter 0.362 0.516 0.610 0.880 1.272 1.468 1.952 0.662 0.952 0.204 0.903 µs 51.18 220.8
Server Jitter 15.204.249.252 0.355 0.819 1.100 2.753 14.932 24.073 82.167 13.833 23.253 7.546 5.141 ms 6.093 61.72
Server Jitter 162.159.200.1 1.369 1.369 1.369 2.174 6.075 6.075 6.075 4.706 4.706 1.315 2.572 ms 5.479 18.15
Server Jitter 162.159.200.123 0.814 0.934 1.146 3.428 20.123 32.058 32.448 18.977 31.124 6.462 5.929 ms 1.926 7.109
Server Jitter 169.229.128.134 0.551 0.732 1.167 3.717 24.771 38.029 38.391 23.603 37.297 7.518 7.074 ms 1.891 7.256
Server Jitter 173.11.101.155 0.978 1.255 1.616 4.079 17.874 21.350 22.336 16.258 20.095 4.646 5.756 ms 2.425 7.384
Server Jitter 192.12.19.20 0.555 0.770 1.159 3.331 24.815 34.767 35.183 23.657 33.997 8.038 7.370 ms 1.292 3.945
Server Jitter 50.116.42.84 0.578 0.596 0.995 3.133 20.032 38.416 38.483 19.037 37.820 6.856 5.912 ms 1.975 8.328
Server Jitter 52.10.183.132 0.764 0.879 1.076 3.225 20.666 30.698 31.289 19.589 29.819 6.935 6.350 ms 1.587 5.401
Server Jitter 64.142.122.36 0.319 0.759 1.114 2.951 16.577 22.731 31.663 15.463 21.972 5.527 5.816 ms 1.761 6.204
Server Jitter 66.220.9.122 0.690 0.714 0.922 3.119 21.282 30.963 32.512 20.360 30.249 6.953 6.392 ms 1.478 5.018
Server Jitter SHM(0) 0.050 0.077 0.110 0.299 0.991 1.392 2.897 0.881 1.315 0.296 0.397 ms 2.709 9.745
Server Jitter SHM(1) 0.183 0.318 0.443 0.873 1.698 2.278 3.100 1.255 1.960 0.400 0.947 µs 7.874 26.68
Server Offset 15.204.249.252 3.144 3.189 3.738 4.554 6.989 10.000 13.899 3.251 6.811 1.354 4.982 ms 30.11 140.6
Server Offset 162.159.200.1 0.915 0.915 0.915 1.604 3.396 3.396 3.396 2.482 2.482 0.692 1.570 ms 7.504 25.68
Server Offset 162.159.200.123 -0.405 0.259 0.402 1.202 3.165 4.457 5.759 2.763 4.197 0.863 1.399 ms 4.025 15.53
Server Offset 169.229.128.134 -1.901 -0.754 1.601 2.378 3.241 5.458 5.574 1.640 6.212 0.752 2.395 ms 16.68 63.92
Server Offset 173.11.101.155 -7.520 -5.124 -4.189 -2.101 1.294 4.773 5.090 5.483 9.898 1.847 -1.806 ms -12.84 36.9
Server Offset 192.12.19.20 0.257 0.764 2.017 2.680 4.349 5.342 6.703 2.332 4.577 0.799 2.811 ms 24.76 98.61
Server Offset 50.116.42.84 0.629 0.932 1.329 2.243 4.228 6.179 6.631 2.898 5.248 0.928 2.453 ms 10.94 40.62
Server Offset 52.10.183.132 2.224 2.252 3.100 3.900 7.688 10.001 10.886 4.588 7.749 1.572 4.538 ms 13.95 51.12
Server Offset 64.142.122.36 0.440 0.517 1.571 2.131 3.287 6.614 6.634 1.716 6.097 0.773 2.223 ms 15.74 80.08
Server Offset 66.220.9.122 -8.637 -0.114 0.849 2.609 3.667 6.819 6.883 2.818 6.933 1.350 2.477 ms -0.4414 28.18
Server Offset SHM(0) -101.102 -100.241 -99.321 -96.742 -94.803 -94.266 -93.359 4.517 5.974 1.320 -96.834 ms -4.111e+05 3.057e+07
Server Offset SHM(1) -2.727 -1.823 -1.203 0.149 1.167 1.562 2.765 2.370 3.385 0.713 0.092 µs -3.686 9.953
TDOP 0.540 0.540 0.590 0.810 1.260 1.330 1.540 0.670 0.790 0.208 0.857 40.34 164.3
Temp ZONE0 46.160 46.160 47.236 48.312 49.926 49.926 50.464 2.690 3.766 0.983 48.484 °C
nSats 7.000 8.000 8.000 10.000 11.000 12.000 12.000 3.000 4.000 0.975 9.594 nSat 716.4 6571
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!