NTPsec

C-ntpsec-3-hour-stats

Report generated: Mon Dec 6 21:02:29 2021 UTC
Start Time: Mon Dec 6 18:02:29 2021 UTC
End Time: Mon Dec 6 21:02:29 2021 UTC
Report published: Mon Dec 06 13:02:38 2021 PST
Report Period: 0.1 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 -775.000 -493.000 -213.000 229.000 758.000 982.000 1,047.000 971.000 1,475.000 294.777 244.300 ns -0.4198 3.188
Local Clock Frequency Offset -5.017 -5.016 -5.014 -4.992 -4.975 -4.974 -4.973 0.039 0.042 0.0116 -4.993 ppm -7.985e+07 3.439e+10

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 112.000 123.000 141.000 192.000 279.000 359.000 455.000 138.000 236.000 45.630 199.233 ns 49.61 221.3

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 35.000 38.000 43.000 81.000 174.000 240.000 264.000 131.000 202.000 41.973 90.748 10e-12 6.423 21.36

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 -775.000 -493.000 -213.000 229.000 758.000 982.000 1,047.000 971.000 1,475.000 294.777 244.300 ns -0.4198 3.188

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 -5.017 -5.016 -5.014 -4.992 -4.975 -4.974 -4.973 0.039 0.042 0.0116 -4.993 ppm -7.985e+07 3.439e+10
Temp ZONE0 56.920 56.920 57.458 57.996 58.534 59.072 59.072 1.076 2.152 0.271 57.978 °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 6.000 7.000 9.000 9.000 10.000 10.000 2.000 4.000 0.830 8.372 nSat 776.2 7279
TDOP 0.660 0.670 0.690 0.790 1.510 1.740 1.790 0.820 1.070 0.284 0.972 22.35 81.23

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 162.159.200.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 2.613 2.613 2.619 2.884 3.132 3.310 3.310 0.513 0.697 0.158 2.876 ms 5152 8.959e+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 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.255 2.255 2.284 2.439 2.724 2.780 2.780 0.440 0.525 0.128 2.458 ms 6150 1.134e+05

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

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

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

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



Server Offset 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 -1.286 -1.286 -0.947 0.031 0.491 1.712 1.712 1.438 2.997 0.451 -0.020 ms -3.834 13.67

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

peer offset 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.10 63.968 65.694 99.498 144.339 215.308 228.906 231.139 115.810 163.212 33.798 150.830 µs 52.16 222.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 194.58.202.211

peer offset 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.211 7.178 7.178 7.180 7.331 7.562 7.595 7.595 0.381 0.416 0.111 7.333 ms 2.755e+05 1.793e+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 194.58.202.219

peer offset 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.219 5.094 5.094 5.238 5.417 5.754 5.790 5.790 0.517 0.696 0.145 5.431 ms 4.814e+04 1.754e+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 204.17.205.24

peer offset 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.24 1.291 1.291 1.300 1.745 2.278 2.597 2.597 0.978 1.305 0.270 1.787 ms 194.4 1202

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

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

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

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



Server Offset 216.218.254.202

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.254.202 2.515 2.515 2.518 2.713 2.864 2.926 2.926 0.347 0.411 0.106 2.692 ms 1.473e+04 3.621e+05

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

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

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

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



Server Offset 63.145.169.3

peer offset 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 63.145.169.3 -38.386 -38.386 -9.637 0.829 1.272 1.523 1.523 10.909 39.909 7.349 -1.077 ms -9.088 47.98

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) -65.237 -63.498 -61.076 -53.376 -48.968 -47.591 -45.524 12.108 15.907 4.043 -54.445 ms -3071 4.507e+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) -776.000 -494.000 -214.000 230.000 759.000 983.000 1,048.000 973.000 1,477.000 295.269 244.872 ns -0.4226 3.188

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

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

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

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



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.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.160 0.160 0.264 0.750 45.006 45.099 45.099 44.742 44.938 10.183 3.974 ms 1.573 8.244

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.183 0.183 0.222 1.113 3.216 3.410 3.410 2.994 3.227 0.794 1.232 ms 2.99 8.682

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.687 0.687 0.813 1.451 4.178 11.677 11.677 3.364 10.989 1.743 1.874 ms 4.558 25.39

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

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 39.223 56.859 70.020 158.356 307.251 588.079 1,266.342 237.231 531.220 122.890 176.703 µs 6.588 52.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.



Server Jitter 194.58.202.211

peer jitter 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.211 0.177 0.177 0.298 1.027 1.491 1.531 1.531 1.194 1.354 0.390 0.925 ms 6.496 15.73

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 194.58.202.219

peer jitter 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.219 0.228 0.228 0.309 0.913 4.967 8.406 8.406 4.659 8.178 1.469 1.272 ms 3.179 14.82

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.17.205.24

peer jitter 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.24 0.220 0.220 0.282 0.757 2.650 24.782 24.782 2.368 24.562 4.252 1.622 ms 3.111 17.96

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.189 0.189 0.252 0.820 2.512 2.612 2.612 2.260 2.423 0.628 0.973 ms 2.963 8.272

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 63.145.169.3

peer jitter 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 63.145.169.3 0.179 0.179 0.261 5.880 47.786 52.267 52.267 47.525 52.088 16.083 15.264 ms 0.7351 2.373

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.091 0.207 0.363 1.038 3.447 6.176 8.582 3.084 5.969 1.108 1.340 ms 3.5 16.14

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) 50.000 70.000 104.000 229.000 522.000 685.000 1,225.000 418.000 615.000 137.615 261.784 ns 5.192 21.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -5.017 -5.016 -5.014 -4.992 -4.975 -4.974 -4.973 0.039 0.042 0.0116 -4.993 ppm -7.985e+07 3.439e+10
Local Clock Time Offset -775.000 -493.000 -213.000 229.000 758.000 982.000 1,047.000 971.000 1,475.000 294.777 244.300 ns -0.4198 3.188
Local RMS Frequency Jitter 35.000 38.000 43.000 81.000 174.000 240.000 264.000 131.000 202.000 41.973 90.748 10e-12 6.423 21.36
Local RMS Time Jitter 112.000 123.000 141.000 192.000 279.000 359.000 455.000 138.000 236.000 45.630 199.233 ns 49.61 221.3
Server Jitter 162.159.200.123 0.160 0.160 0.264 0.750 45.006 45.099 45.099 44.742 44.938 10.183 3.974 ms 1.573 8.244
Server Jitter 169.229.128.134 0.183 0.183 0.222 1.113 3.216 3.410 3.410 2.994 3.227 0.794 1.232 ms 2.99 8.682
Server Jitter 173.11.101.155 0.687 0.687 0.813 1.451 4.178 11.677 11.677 3.364 10.989 1.743 1.874 ms 4.558 25.39
Server Jitter 192.168.1.10 39.223 56.859 70.020 158.356 307.251 588.079 1,266.342 237.231 531.220 122.890 176.703 µs 6.588 52.97
Server Jitter 194.58.202.211 0.177 0.177 0.298 1.027 1.491 1.531 1.531 1.194 1.354 0.390 0.925 ms 6.496 15.73
Server Jitter 194.58.202.219 0.228 0.228 0.309 0.913 4.967 8.406 8.406 4.659 8.178 1.469 1.272 ms 3.179 14.82
Server Jitter 204.17.205.24 0.220 0.220 0.282 0.757 2.650 24.782 24.782 2.368 24.562 4.252 1.622 ms 3.111 17.96
Server Jitter 216.218.254.202 0.189 0.189 0.252 0.820 2.512 2.612 2.612 2.260 2.423 0.628 0.973 ms 2.963 8.272
Server Jitter 63.145.169.3 0.179 0.179 0.261 5.880 47.786 52.267 52.267 47.525 52.088 16.083 15.264 ms 0.7351 2.373
Server Jitter SHM(0) 0.091 0.207 0.363 1.038 3.447 6.176 8.582 3.084 5.969 1.108 1.340 ms 3.5 16.14
Server Jitter SHM(1) 50.000 70.000 104.000 229.000 522.000 685.000 1,225.000 418.000 615.000 137.615 261.784 ns 5.192 21.16
Server Offset 162.159.200.123 2.613 2.613 2.619 2.884 3.132 3.310 3.310 0.513 0.697 0.158 2.876 ms 5152 8.959e+04
Server Offset 169.229.128.134 2.255 2.255 2.284 2.439 2.724 2.780 2.780 0.440 0.525 0.128 2.458 ms 6150 1.134e+05
Server Offset 173.11.101.155 -1.286 -1.286 -0.947 0.031 0.491 1.712 1.712 1.438 2.997 0.451 -0.020 ms -3.834 13.67
Server Offset 192.168.1.10 63.968 65.694 99.498 144.339 215.308 228.906 231.139 115.810 163.212 33.798 150.830 µs 52.16 222.2
Server Offset 194.58.202.211 7.178 7.178 7.180 7.331 7.562 7.595 7.595 0.381 0.416 0.111 7.333 ms 2.755e+05 1.793e+07
Server Offset 194.58.202.219 5.094 5.094 5.238 5.417 5.754 5.790 5.790 0.517 0.696 0.145 5.431 ms 4.814e+04 1.754e+06
Server Offset 204.17.205.24 1.291 1.291 1.300 1.745 2.278 2.597 2.597 0.978 1.305 0.270 1.787 ms 194.4 1202
Server Offset 216.218.254.202 2.515 2.515 2.518 2.713 2.864 2.926 2.926 0.347 0.411 0.106 2.692 ms 1.473e+04 3.621e+05
Server Offset 63.145.169.3 -38.386 -38.386 -9.637 0.829 1.272 1.523 1.523 10.909 39.909 7.349 -1.077 ms -9.088 47.98
Server Offset SHM(0) -65.237 -63.498 -61.076 -53.376 -48.968 -47.591 -45.524 12.108 15.907 4.043 -54.445 ms -3071 4.507e+04
Server Offset SHM(1) -776.000 -494.000 -214.000 230.000 759.000 983.000 1,048.000 973.000 1,477.000 295.269 244.872 ns -0.4226 3.188
TDOP 0.660 0.670 0.690 0.790 1.510 1.740 1.790 0.820 1.070 0.284 0.972 22.35 81.23
Temp ZONE0 56.920 56.920 57.458 57.996 58.534 59.072 59.072 1.076 2.152 0.271 57.978 °C
nSats 6.000 6.000 7.000 9.000 9.000 10.000 10.000 2.000 4.000 0.830 8.372 nSat 776.2 7279
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!