NTPsec

C-ntpsec-24-hour-stats

Report generated: Thu Aug 5 10:03:15 2021 UTC
Start Time: Wed Aug 4 10:03:14 2021 UTC
End Time: Thu Aug 5 10:03:14 2021 UTC
Report published: Thu Aug 05 03:04:01 2021 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 -2,707.000 -841.000 -632.000 -62.000 616.000 957.000 1,940.000 1,248.000 1,798.000 384.404 -46.513 ns -4.538 11.67
Local Clock Frequency Offset -5.002 -5.000 -4.997 -4.912 -4.871 -4.862 -4.860 0.126 0.138 0.044 -4.925 ppm -1.455e+06 1.648e+08

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 95.000 117.000 137.000 198.000 308.000 386.000 1,676.000 171.000 269.000 74.088 208.971 ns 18.89 195.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 29.000 38.000 47.000 82.000 159.000 222.000 346.000 112.000 184.000 37.989 90.021 10e-12 8.655 35.73

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,707.000 -841.000 -632.000 -62.000 616.000 957.000 1,940.000 1,248.000 1,798.000 384.404 -46.513 ns -4.538 11.67

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.002 -5.000 -4.997 -4.912 -4.871 -4.862 -4.860 0.126 0.138 0.044 -4.925 ppm -1.455e+06 1.648e+08
Temp ZONE0 57.996 57.996 57.996 59.072 60.148 60.686 60.686 2.152 2.690 0.717 59.390 °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 7.000 8.000 9.000 11.000 12.000 13.000 3.000 5.000 1.110 9.370 nSat 434.5 3409
TDOP 0.470 0.530 0.590 0.830 1.290 1.490 1.850 0.700 0.960 0.216 0.866 37.07 151.1

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 2.498 2.498 2.498 2.498 2.498 2.498 2.498 0.000 0.000 0.000 2.498 ms nan nan

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.390 2.026 2.463 2.892 3.269 3.504 4.070 0.807 1.478 0.286 2.881 ms 770.2 7214

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 3.692 3.692 3.692 3.692 3.692 3.692 3.692 0.000 0.000 0.000 3.692 ms nan nan

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 -3.857 -2.727 -0.475 0.057 0.725 510.213 560.083 1.199 512.940 58.295 6.454 ms 5.611 55.23

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 0.479 0.479 0.479 1.348 1.590 1.590 1.590 1.110 1.110 0.366 1.138 ms 15.21 44.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 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 -37.454 37.115 79.421 176.185 236.039 267.247 311.471 156.618 230.132 49.139 168.326 µs 20.97 67.69

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 3.988 5.305 5.863 6.349 7.976 9.026 10.266 2.113 3.721 0.738 6.567 ms 517 4311

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 4.198 4.678 4.919 5.785 9.174 9.322 9.436 4.255 4.644 1.460 6.325 ms 47.8 203.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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 -1.204 -1.164 -0.740 -0.241 0.132 6.928 7.171 0.871 8.092 1.041 -0.118 ms 1.398 22.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 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 -1.294 -1.294 -1.294 2.717 4.641 4.641 4.641 5.935 5.935 1.490 2.307 ms 0.6694 3.866

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 2.610 3.054 3.390 3.853 4.237 4.374 5.365 0.847 1.320 0.282 3.834 ms 2035 2.611e+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 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 -1.157 0.514 2.304 2.701 3.043 3.136 3.210 0.739 2.622 0.431 2.651 ms 147.3 797.3

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 -78.676 -74.214 -69.641 -0.129 0.671 2.765 3.186 70.312 76.979 28.468 -22.072 ms -11.57 35.13

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

peer offset 64.62.153.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.62.153.210 -3.413 0.369 2.389 2.775 3.103 3.226 3.429 0.714 2.857 0.498 2.714 ms 92.88 456.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 64.62.194.189

peer offset 64.62.194.189 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.62.194.189 2.355 3.268 3.517 5.798 13.185 13.498 539.755 9.668 10.229 34.063 9.610 ms 12.8 197.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 73.158.5.1

peer offset 73.158.5.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 73.158.5.1 -3.700 -2.750 -1.891 -0.564 0.346 1.091 20.468 2.237 3.842 1.521 -0.577 ms 3.316 99.5

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) -68.370 -65.990 -63.206 -55.545 -48.106 -46.045 -42.470 15.100 19.945 4.471 -55.488 ms -2453 3.345e+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) -2,708.000 -842.000 -633.000 -63.000 617.000 958.000 1,941.000 1,250.000 1,800.000 385.167 -46.633 ns -4.539 11.66

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 2.811 2.811 2.811 2.811 2.811 2.811 2.811 0.000 0.000 0.000 2.811 ms nan nan

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.139 0.188 0.269 1.342 8.639 10.806 203.797 8.370 10.618 13.594 3.165 ms 11.48 170.2

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 3.152 3.152 3.152 3.152 3.152 3.152 3.152 0.000 0.000 0.000 3.152 ms nan nan

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 0.711 1.776 13.906 346.664 550.259 13.194 346.664 47.516 8.954 ms 6.409 67.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 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 1.397 1.397 1.397 8.813 10.876 10.876 10.876 9.479 9.479 3.957 6.894 ms 2.131 3.603

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 0.025 0.040 0.075 0.226 8.715 9.574 16.417 8.640 9.534 2.890 1.573 ms 0.5778 3.358

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.148 0.222 0.325 1.712 9.468 14.147 45.495 9.143 13.925 4.873 3.180 ms 4.544 39.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 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.136 0.201 0.306 1.664 9.662 14.280 18.574 9.355 14.079 3.440 3.027 ms 1.553 5.685

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 203.123.48.219

peer jitter 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 203.123.48.219 0.131 0.177 0.277 1.642 9.839 12.936 19.467 9.562 12.759 3.506 3.174 ms 1.492 5.573

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

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.045 3.070 3.070 3.070 3.070 3.070 0.950 1.028 ms 0.9938 3.173

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.169 0.177 0.319 1.418 9.747 12.539 12.662 9.428 12.362 3.378 3.228 ms 1.011 2.798

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.243 1.225 9.453 19.482 19.903 9.210 19.482 3.808 2.995 ms 1.397 5.846

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.000 0.000 5.882 44.416 72.467 82.684 87.622 66.585 82.684 23.049 40.244 ms 2.533 4.973

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

peer jitter 64.62.153.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.62.153.210 0.000 0.167 0.259 1.412 8.909 13.085 20.921 8.650 12.918 3.286 2.827 ms 1.443 5.797

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

peer jitter 64.62.194.189 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.62.194.189 0.000 0.000 0.251 1.118 9.473 20.543 517.428 9.222 20.543 40.696 6.111 ms 8.057 97.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.



Server Jitter 73.158.5.1

peer jitter 73.158.5.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.158.5.1 0.000 0.000 1.027 2.155 9.570 24.168 55.774 8.542 24.168 5.505 3.725 ms 5.752 53.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.



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.098 0.208 0.340 0.977 3.141 5.916 9.259 2.801 5.707 1.040 1.266 ms 3.424 15.93

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) 43.000 75.000 104.000 235.000 536.000 769.000 3,082.000 432.000 694.000 156.634 270.104 ns 6.256 54.84

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.002 -5.000 -4.997 -4.912 -4.871 -4.862 -4.860 0.126 0.138 0.044 -4.925 ppm -1.455e+06 1.648e+08
Local Clock Time Offset -2,707.000 -841.000 -632.000 -62.000 616.000 957.000 1,940.000 1,248.000 1,798.000 384.404 -46.513 ns -4.538 11.67
Local RMS Frequency Jitter 29.000 38.000 47.000 82.000 159.000 222.000 346.000 112.000 184.000 37.989 90.021 10e-12 8.655 35.73
Local RMS Time Jitter 95.000 117.000 137.000 198.000 308.000 386.000 1,676.000 171.000 269.000 74.088 208.971 ns 18.89 195.7
Server Jitter 104.131.155.175 2.811 2.811 2.811 2.811 2.811 2.811 2.811 0.000 0.000 0.000 2.811 ms nan nan
Server Jitter 162.159.200.1 0.139 0.188 0.269 1.342 8.639 10.806 203.797 8.370 10.618 13.594 3.165 ms 11.48 170.2
Server Jitter 162.159.200.123 3.152 3.152 3.152 3.152 3.152 3.152 3.152 0.000 0.000 0.000 3.152 ms nan nan
Server Jitter 173.11.101.155 0.000 0.000 0.711 1.776 13.906 346.664 550.259 13.194 346.664 47.516 8.954 ms 6.409 67.7
Server Jitter 178.62.68.79 1.397 1.397 1.397 8.813 10.876 10.876 10.876 9.479 9.479 3.957 6.894 ms 2.131 3.603
Server Jitter 192.168.1.10 0.025 0.040 0.075 0.226 8.715 9.574 16.417 8.640 9.534 2.890 1.573 ms 0.5778 3.358
Server Jitter 194.58.202.211 0.148 0.222 0.325 1.712 9.468 14.147 45.495 9.143 13.925 4.873 3.180 ms 4.544 39.48
Server Jitter 194.58.202.219 0.136 0.201 0.306 1.664 9.662 14.280 18.574 9.355 14.079 3.440 3.027 ms 1.553 5.685
Server Jitter 203.123.48.219 0.131 0.177 0.277 1.642 9.839 12.936 19.467 9.562 12.759 3.506 3.174 ms 1.492 5.573
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.045 3.070 3.070 3.070 3.070 3.070 0.950 1.028 ms 0.9938 3.173
Server Jitter 204.17.205.24 0.169 0.177 0.319 1.418 9.747 12.539 12.662 9.428 12.362 3.378 3.228 ms 1.011 2.798
Server Jitter 216.218.192.202 0.000 0.000 0.243 1.225 9.453 19.482 19.903 9.210 19.482 3.808 2.995 ms 1.397 5.846
Server Jitter 63.145.169.3 0.000 0.000 5.882 44.416 72.467 82.684 87.622 66.585 82.684 23.049 40.244 ms 2.533 4.973
Server Jitter 64.62.153.210 0.000 0.167 0.259 1.412 8.909 13.085 20.921 8.650 12.918 3.286 2.827 ms 1.443 5.797
Server Jitter 64.62.194.189 0.000 0.000 0.251 1.118 9.473 20.543 517.428 9.222 20.543 40.696 6.111 ms 8.057 97.06
Server Jitter 73.158.5.1 0.000 0.000 1.027 2.155 9.570 24.168 55.774 8.542 24.168 5.505 3.725 ms 5.752 53.06
Server Jitter SHM(0) 0.098 0.208 0.340 0.977 3.141 5.916 9.259 2.801 5.707 1.040 1.266 ms 3.424 15.93
Server Jitter SHM(1) 43.000 75.000 104.000 235.000 536.000 769.000 3,082.000 432.000 694.000 156.634 270.104 ns 6.256 54.84
Server Offset 104.131.155.175 2.498 2.498 2.498 2.498 2.498 2.498 2.498 0.000 0.000 0.000 2.498 ms nan nan
Server Offset 162.159.200.1 1.390 2.026 2.463 2.892 3.269 3.504 4.070 0.807 1.478 0.286 2.881 ms 770.2 7214
Server Offset 162.159.200.123 3.692 3.692 3.692 3.692 3.692 3.692 3.692 0.000 0.000 0.000 3.692 ms nan nan
Server Offset 173.11.101.155 -3.857 -2.727 -0.475 0.057 0.725 510.213 560.083 1.199 512.940 58.295 6.454 ms 5.611 55.23
Server Offset 178.62.68.79 0.479 0.479 0.479 1.348 1.590 1.590 1.590 1.110 1.110 0.366 1.138 ms 15.21 44.15
Server Offset 192.168.1.10 -37.454 37.115 79.421 176.185 236.039 267.247 311.471 156.618 230.132 49.139 168.326 µs 20.97 67.69
Server Offset 194.58.202.211 3.988 5.305 5.863 6.349 7.976 9.026 10.266 2.113 3.721 0.738 6.567 ms 517 4311
Server Offset 194.58.202.219 4.198 4.678 4.919 5.785 9.174 9.322 9.436 4.255 4.644 1.460 6.325 ms 47.8 203.1
Server Offset 203.123.48.219 -1.204 -1.164 -0.740 -0.241 0.132 6.928 7.171 0.871 8.092 1.041 -0.118 ms 1.398 22.67
Server Offset 204.123.2.5 -1.294 -1.294 -1.294 2.717 4.641 4.641 4.641 5.935 5.935 1.490 2.307 ms 0.6694 3.866
Server Offset 204.17.205.24 2.610 3.054 3.390 3.853 4.237 4.374 5.365 0.847 1.320 0.282 3.834 ms 2035 2.611e+04
Server Offset 216.218.192.202 -1.157 0.514 2.304 2.701 3.043 3.136 3.210 0.739 2.622 0.431 2.651 ms 147.3 797.3
Server Offset 63.145.169.3 -78.676 -74.214 -69.641 -0.129 0.671 2.765 3.186 70.312 76.979 28.468 -22.072 ms -11.57 35.13
Server Offset 64.62.153.210 -3.413 0.369 2.389 2.775 3.103 3.226 3.429 0.714 2.857 0.498 2.714 ms 92.88 456.4
Server Offset 64.62.194.189 2.355 3.268 3.517 5.798 13.185 13.498 539.755 9.668 10.229 34.063 9.610 ms 12.8 197.9
Server Offset 73.158.5.1 -3.700 -2.750 -1.891 -0.564 0.346 1.091 20.468 2.237 3.842 1.521 -0.577 ms 3.316 99.5
Server Offset SHM(0) -68.370 -65.990 -63.206 -55.545 -48.106 -46.045 -42.470 15.100 19.945 4.471 -55.488 ms -2453 3.345e+04
Server Offset SHM(1) -2,708.000 -842.000 -633.000 -63.000 617.000 958.000 1,941.000 1,250.000 1,800.000 385.167 -46.633 ns -4.539 11.66
TDOP 0.470 0.530 0.590 0.830 1.290 1.490 1.850 0.700 0.960 0.216 0.866 37.07 151.1
Temp ZONE0 57.996 57.996 57.996 59.072 60.148 60.686 60.686 2.152 2.690 0.717 59.390 °C
nSats 7.000 7.000 8.000 9.000 11.000 12.000 13.000 3.000 5.000 1.110 9.370 nSat 434.5 3409
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!