NTPsec

A-ntpsec-24-hour-stats

Report generated: Wed Aug 17 18:11:13 2022 UTC
Start Time: Tue Aug 16 18:11:11 2022 UTC
End Time: Wed Aug 17 18:11:11 2022 UTC
Report published: Wed Aug 17 11:11:29 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 -68.056 -3.054 -1.653 0.019 1.640 2.434 16.905 3.293 5.488 1.152 -0.002 µs -9.508 335.9
Local Clock Frequency Offset -448.822 -299.149 -172.318 -44.342 -12.726 -7.706 84.793 159.592 291.443 62.555 -75.463 ppb -18.96 74.68

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.268 0.383 0.477 1.125 2.216 3.592 33.175 1.739 3.209 0.782 1.208 µs 12.02 319.4

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.000 0.579 0.725 1.723 3.514 5.832 47.112 2.789 5.253 1.272 1.856 ppb 10.21 220.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 -68.056 -3.054 -1.653 0.019 1.640 2.434 16.905 3.293 5.488 1.152 -0.002 µs -9.508 335.9

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 -448.822 -299.149 -172.318 -44.342 -12.726 -7.706 84.793 159.592 291.443 62.555 -75.463 ppb -18.96 74.68
Temp ZONE0 53.154 53.692 53.692 56.920 60.148 61.762 64.990 6.456 8.070 2.207 57.149 °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 11.000 12.000 12.000 3.000 5.000 1.012 9.593 nSat 635.8 5614
TDOP 0.500 0.540 0.580 0.810 1.260 1.510 2.100 0.680 0.970 0.211 0.854 38.95 165

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 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 0.373 0.373 2.334 3.023 3.884 5.914 5.914 1.550 5.541 0.768 3.073 ms 36.35 146.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 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 1.991 2.243 2.586 3.265 3.957 4.982 5.705 1.371 2.738 0.468 3.275 ms 234.4 1535

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 -2.089 1.697 1.947 2.368 2.923 3.226 9.369 0.975 1.529 0.564 2.407 ms 49.42 335.1

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 -16.511 -3.105 -2.281 -0.348 0.534 1.331 2.660 2.815 4.437 1.234 -0.554 ms -14.49 148.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 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 -18.789 -18.789 -13.728 1.083 1.992 2.050 2.050 15.720 20.838 4.280 -0.319 ms -7.637 34.19

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 -0.783 -0.369 -0.172 0.174 0.516 0.729 37.134 0.688 1.098 0.891 0.192 ms 30.74 1213

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

peer offset 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.23 0.364 0.364 0.691 1.420 3.804 4.479 4.479 3.113 4.115 0.823 1.516 ms 5.151 19.24

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 0.761 0.965 1.471 2.328 2.824 3.213 3.496 1.353 2.249 0.407 2.270 ms 108.7 553.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 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 -11.504 -1.182 1.438 2.358 2.972 3.737 4.960 1.534 4.919 1.109 2.247 ms -4.7 79.29

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 45.33.37.82

peer offset 45.33.37.82 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.33.37.82 -0.157 1.748 1.938 2.554 3.153 3.850 5.833 1.216 2.101 0.441 2.567 ms 127.1 711.2

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) -0.088 -0.055 -0.054 -0.049 -0.044 -0.043 13.687 0.009 0.012 0.133 -0.048 s 96.81 1.015e+04

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

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

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

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



Server Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -0.000 -0.000 -0.000 0.000 0.000 0.000 66.076 0.000 0.000 0.333 0.002 s 182.2 3.572e+04

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

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

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

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



Server 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 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.000 0.000 0.000 1.556 8.179 9.940 9.940 8.179 9.940 2.895 2.719 ms 1.106 2.888

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.000 0.000 0.592 1.929 12.945 27.896 28.480 12.353 27.896 5.228 4.174 ms 1.946 8.679

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.000 0.000 0.474 1.345 9.927 17.060 17.462 9.453 17.060 3.247 2.680 ms 1.944 7.929

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.000 0.000 1.040 2.215 14.186 22.516 27.616 13.146 22.516 4.517 3.992 ms 2.216 8.767

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 178.62.68.79

peer jitter 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.62.68.79 0.000 0.000 0.000 2.012 19.019 20.239 20.239 19.019 20.239 6.366 5.203 ms 0.8688 2.574

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 0.000 0.230 0.355 1.051 9.538 18.290 139.557 9.182 18.061 6.008 2.521 ms 12.28 260.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 204.17.205.23

peer jitter 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.23 0.000 0.000 0.000 2.002 14.012 14.674 14.674 14.012 14.674 3.825 3.804 ms 1.603 4.746

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.000 0.000 0.441 1.517 12.050 14.442 18.932 11.608 14.442 3.358 2.788 ms 1.885 7.136

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.000 0.000 0.443 1.523 9.921 13.596 16.311 9.478 13.596 2.997 2.613 ms 2.118 8.074

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 45.33.37.82

peer jitter 45.33.37.82 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.33.37.82 0.000 0.000 0.470 1.562 9.997 17.125 22.020 9.527 17.125 3.368 2.782 ms 2.279 10.16

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.000 0.000 0.000 0.001 0.002 0.003 13.738 0.002 0.003 0.214 0.006 s 42.8 2232

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.000 0.257 0.367 1.030 2.765 4.577 67.896 2.398 4.320 1.039 1.245 µs 12.76 528.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -448.822 -299.149 -172.318 -44.342 -12.726 -7.706 84.793 159.592 291.443 62.555 -75.463 ppb -18.96 74.68
Local Clock Time Offset -68.056 -3.054 -1.653 0.019 1.640 2.434 16.905 3.293 5.488 1.152 -0.002 µs -9.508 335.9
Local RMS Frequency Jitter 0.000 0.579 0.725 1.723 3.514 5.832 47.112 2.789 5.253 1.272 1.856 ppb 10.21 220.4
Local RMS Time Jitter 0.268 0.383 0.477 1.125 2.216 3.592 33.175 1.739 3.209 0.782 1.208 µs 12.02 319.4
Server Jitter 104.131.155.175 0.000 0.000 0.000 1.556 8.179 9.940 9.940 8.179 9.940 2.895 2.719 ms 1.106 2.888
Server Jitter 162.159.200.1 0.000 0.000 0.592 1.929 12.945 27.896 28.480 12.353 27.896 5.228 4.174 ms 1.946 8.679
Server Jitter 169.229.128.134 0.000 0.000 0.474 1.345 9.927 17.060 17.462 9.453 17.060 3.247 2.680 ms 1.944 7.929
Server Jitter 173.11.101.155 0.000 0.000 1.040 2.215 14.186 22.516 27.616 13.146 22.516 4.517 3.992 ms 2.216 8.767
Server Jitter 178.62.68.79 0.000 0.000 0.000 2.012 19.019 20.239 20.239 19.019 20.239 6.366 5.203 ms 0.8688 2.574
Server Jitter 192.168.1.11 0.000 0.230 0.355 1.051 9.538 18.290 139.557 9.182 18.061 6.008 2.521 ms 12.28 260.3
Server Jitter 204.17.205.23 0.000 0.000 0.000 2.002 14.012 14.674 14.674 14.012 14.674 3.825 3.804 ms 1.603 4.746
Server Jitter 216.218.192.202 0.000 0.000 0.441 1.517 12.050 14.442 18.932 11.608 14.442 3.358 2.788 ms 1.885 7.136
Server Jitter 216.218.254.202 0.000 0.000 0.443 1.523 9.921 13.596 16.311 9.478 13.596 2.997 2.613 ms 2.118 8.074
Server Jitter 45.33.37.82 0.000 0.000 0.470 1.562 9.997 17.125 22.020 9.527 17.125 3.368 2.782 ms 2.279 10.16
Server Jitter SHM(0) 0.000 0.000 0.000 0.001 0.002 0.003 13.738 0.002 0.003 0.214 0.006 s 42.8 2232
Server Jitter SHM(1) 0.000 0.257 0.367 1.030 2.765 4.577 67.896 2.398 4.320 1.039 1.245 µs 12.76 528.7
Server Offset 104.131.155.175 0.373 0.373 2.334 3.023 3.884 5.914 5.914 1.550 5.541 0.768 3.073 ms 36.35 146.9
Server Offset 162.159.200.1 1.991 2.243 2.586 3.265 3.957 4.982 5.705 1.371 2.738 0.468 3.275 ms 234.4 1535
Server Offset 169.229.128.134 -2.089 1.697 1.947 2.368 2.923 3.226 9.369 0.975 1.529 0.564 2.407 ms 49.42 335.1
Server Offset 173.11.101.155 -16.511 -3.105 -2.281 -0.348 0.534 1.331 2.660 2.815 4.437 1.234 -0.554 ms -14.49 148.8
Server Offset 178.62.68.79 -18.789 -18.789 -13.728 1.083 1.992 2.050 2.050 15.720 20.838 4.280 -0.319 ms -7.637 34.19
Server Offset 192.168.1.11 -0.783 -0.369 -0.172 0.174 0.516 0.729 37.134 0.688 1.098 0.891 0.192 ms 30.74 1213
Server Offset 204.17.205.23 0.364 0.364 0.691 1.420 3.804 4.479 4.479 3.113 4.115 0.823 1.516 ms 5.151 19.24
Server Offset 216.218.192.202 0.761 0.965 1.471 2.328 2.824 3.213 3.496 1.353 2.249 0.407 2.270 ms 108.7 553.6
Server Offset 216.218.254.202 -11.504 -1.182 1.438 2.358 2.972 3.737 4.960 1.534 4.919 1.109 2.247 ms -4.7 79.29
Server Offset 45.33.37.82 -0.157 1.748 1.938 2.554 3.153 3.850 5.833 1.216 2.101 0.441 2.567 ms 127.1 711.2
Server Offset SHM(0) -0.088 -0.055 -0.054 -0.049 -0.044 -0.043 13.687 0.009 0.012 0.133 -0.048 s 96.81 1.015e+04
Server Offset SHM(1) -0.000 -0.000 -0.000 0.000 0.000 0.000 66.076 0.000 0.000 0.333 0.002 s 182.2 3.572e+04
TDOP 0.500 0.540 0.580 0.810 1.260 1.510 2.100 0.680 0.970 0.211 0.854 38.95 165
Temp ZONE0 53.154 53.692 53.692 56.920 60.148 61.762 64.990 6.456 8.070 2.207 57.149 °C
nSats 6.000 7.000 8.000 10.000 11.000 12.000 12.000 3.000 5.000 1.012 9.593 nSat 635.8 5614
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!