NTPsec

C-ntpsec-6-hour-stats

Report generated: Thu Aug 5 10:01:29 2021 UTC
Start Time: Thu Aug 5 04:01:29 2021 UTC
End Time: Thu Aug 5 10:01:29 2021 UTC
Report published: Thu Aug 05 03:02:13 2021 PDT
Report Period: 0.2 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 -806.000 -568.000 -165.000 423.000 818.000 1,940.000 991.000 1,624.000 330.222 -125.493 ns -6.309 20.79
Local Clock Frequency Offset -4.917 -4.917 -4.913 -4.887 -4.870 -4.869 -4.869 0.044 0.047 0.0145 -4.889 ppm -3.888e+07 1.317e+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 104.000 118.000 138.000 196.000 319.000 783.000 1,676.000 181.000 665.000 117.247 216.979 ns 10.22 97.52

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 32.000 37.000 46.000 74.000 131.000 250.000 323.000 85.000 213.000 32.953 79.935 10e-12 10.59 57.14

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 -806.000 -568.000 -165.000 423.000 818.000 1,940.000 991.000 1,624.000 330.222 -125.493 ns -6.309 20.79

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 -4.917 -4.917 -4.913 -4.887 -4.870 -4.869 -4.869 0.044 0.047 0.0145 -4.889 ppm -3.888e+07 1.317e+10
Temp ZONE0 59.072 59.072 59.072 60.148 60.686 60.686 60.686 1.614 1.614 0.454 59.915 °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 10.000 12.000 12.000 13.000 4.000 5.000 1.129 9.639 nSat 450.8 3576
TDOP 0.470 0.520 0.550 0.750 1.180 1.380 1.850 0.630 0.860 0.194 0.787 39.38 174.4

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.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 2.643 2.643 2.702 3.045 3.492 4.070 4.070 0.791 1.426 0.250 3.062 ms 1463 1.692e+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 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 -0.494 -0.494 -0.355 0.180 0.760 2.628 2.628 1.115 3.122 0.516 0.234 ms 0.7426 8.48

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 32.161 73.867 113.935 188.256 246.767 261.050 269.232 132.832 187.183 37.981 186.370 µs 70.64 317.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 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 6.059 6.059 6.112 6.451 6.929 9.026 9.026 0.817 2.967 0.411 6.519 ms 3331 5.039e+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 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 6.514 6.514 6.524 6.843 7.170 7.263 7.263 0.647 0.748 0.179 6.870 ms 5.235e+04 1.961e+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 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.164 -1.164 -0.468 -0.131 6.928 7.171 7.171 7.395 8.335 1.959 0.417 ms 0.04807 4.575

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 3.390 3.390 3.626 4.014 4.287 5.365 5.365 0.661 1.976 0.269 4.023 ms 2755 3.91e+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 -0.269 -0.269 2.581 2.823 3.080 3.210 3.210 0.499 3.480 0.412 2.782 ms 202 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 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 -75.402 -75.402 -73.377 -24.004 0.691 2.765 2.765 74.067 78.167 30.739 -30.314 ms -13.98 42

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 2.458 2.458 2.513 2.811 3.084 3.121 3.121 0.571 0.662 0.161 2.803 ms 4458 7.391e+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 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 4.837 4.837 5.025 5.753 6.829 6.887 6.887 1.804 2.050 0.573 5.857 ms 814.1 7776

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 -3.700 -1.972 -0.354 0.397 20.468 20.468 2.369 24.168 2.606 -0.357 ms 2.141 34.21

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.332 -66.735 -64.359 -56.077 -49.201 -47.168 -45.013 15.158 19.567 4.545 -56.208 ms -2428 3.3e+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 -807.000 -569.000 -166.000 424.000 819.000 1,941.000 993.000 1,626.000 330.894 -125.866 ns -6.31 20.75

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.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.139 0.200 1.078 8.666 203.797 203.797 8.467 203.658 29.230 6.039 ms 3.705 27.86

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.602 2.014 13.745 18.791 18.791 13.143 18.791 4.511 3.764 ms 1.324 4.249

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.026 0.039 0.070 0.291 9.072 11.265 11.727 9.002 11.225 3.282 1.968 ms 0.3836 2.404

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.305 0.305 0.341 1.814 9.568 11.785 11.785 9.227 11.480 3.073 3.056 ms 1.373 3.65

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.221 0.221 0.290 1.395 9.186 14.280 14.280 8.896 14.059 3.003 2.397 ms 2.023 8.154

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.146 0.146 0.367 3.037 12.936 19.467 19.467 12.570 19.321 4.478 4.862 ms 1.554 5.096

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.174 0.174 0.288 1.211 8.777 10.741 10.741 8.489 10.566 2.866 2.595 ms 1.07 3.076

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.270 1.464 9.083 19.903 19.903 8.813 19.903 4.275 3.250 ms 1.601 6.57

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 3.857 40.673 76.157 87.622 87.622 72.301 87.622 26.379 38.505 ms 1.57 3.023

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.000 0.390 1.615 13.085 20.921 20.921 12.696 20.921 4.454 4.346 ms 1.253 4.391

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.331 1.250 12.432 20.543 20.543 12.101 20.543 4.154 3.203 ms 1.245 5.156

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 0.845 2.606 14.517 55.774 55.774 13.672 55.774 9.357 5.518 ms 3.062 16.99

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.196 0.338 1.017 3.198 5.878 8.727 2.860 5.682 1.048 1.300 ms 3.397 15.57

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.048 0.072 0.105 0.242 0.577 1.017 3.082 0.472 0.945 0.206 0.289 µs 6.301 58.11

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -4.917 -4.917 -4.913 -4.887 -4.870 -4.869 -4.869 0.044 0.047 0.0145 -4.889 ppm -3.888e+07 1.317e+10
Local Clock Time Offset -2,707.000 -806.000 -568.000 -165.000 423.000 818.000 1,940.000 991.000 1,624.000 330.222 -125.493 ns -6.309 20.79
Local RMS Frequency Jitter 32.000 37.000 46.000 74.000 131.000 250.000 323.000 85.000 213.000 32.953 79.935 10e-12 10.59 57.14
Local RMS Time Jitter 104.000 118.000 138.000 196.000 319.000 783.000 1,676.000 181.000 665.000 117.247 216.979 ns 10.22 97.52
Server Jitter 162.159.200.1 0.139 0.139 0.200 1.078 8.666 203.797 203.797 8.467 203.658 29.230 6.039 ms 3.705 27.86
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.602 2.014 13.745 18.791 18.791 13.143 18.791 4.511 3.764 ms 1.324 4.249
Server Jitter 192.168.1.10 0.026 0.039 0.070 0.291 9.072 11.265 11.727 9.002 11.225 3.282 1.968 ms 0.3836 2.404
Server Jitter 194.58.202.211 0.305 0.305 0.341 1.814 9.568 11.785 11.785 9.227 11.480 3.073 3.056 ms 1.373 3.65
Server Jitter 194.58.202.219 0.221 0.221 0.290 1.395 9.186 14.280 14.280 8.896 14.059 3.003 2.397 ms 2.023 8.154
Server Jitter 203.123.48.219 0.146 0.146 0.367 3.037 12.936 19.467 19.467 12.570 19.321 4.478 4.862 ms 1.554 5.096
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.174 0.174 0.288 1.211 8.777 10.741 10.741 8.489 10.566 2.866 2.595 ms 1.07 3.076
Server Jitter 216.218.192.202 0.000 0.000 0.270 1.464 9.083 19.903 19.903 8.813 19.903 4.275 3.250 ms 1.601 6.57
Server Jitter 63.145.169.3 0.000 0.000 3.857 40.673 76.157 87.622 87.622 72.301 87.622 26.379 38.505 ms 1.57 3.023
Server Jitter 64.62.153.210 0.000 0.000 0.390 1.615 13.085 20.921 20.921 12.696 20.921 4.454 4.346 ms 1.253 4.391
Server Jitter 64.62.194.189 0.000 0.000 0.331 1.250 12.432 20.543 20.543 12.101 20.543 4.154 3.203 ms 1.245 5.156
Server Jitter 73.158.5.1 0.000 0.000 0.845 2.606 14.517 55.774 55.774 13.672 55.774 9.357 5.518 ms 3.062 16.99
Server Jitter SHM(0) 0.098 0.196 0.338 1.017 3.198 5.878 8.727 2.860 5.682 1.048 1.300 ms 3.397 15.57
Server Jitter SHM(1) 0.048 0.072 0.105 0.242 0.577 1.017 3.082 0.472 0.945 0.206 0.289 µs 6.301 58.11
Server Offset 162.159.200.1 2.643 2.643 2.702 3.045 3.492 4.070 4.070 0.791 1.426 0.250 3.062 ms 1463 1.692e+04
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 -0.494 -0.494 -0.355 0.180 0.760 2.628 2.628 1.115 3.122 0.516 0.234 ms 0.7426 8.48
Server Offset 192.168.1.10 32.161 73.867 113.935 188.256 246.767 261.050 269.232 132.832 187.183 37.981 186.370 µs 70.64 317.5
Server Offset 194.58.202.211 6.059 6.059 6.112 6.451 6.929 9.026 9.026 0.817 2.967 0.411 6.519 ms 3331 5.039e+04
Server Offset 194.58.202.219 6.514 6.514 6.524 6.843 7.170 7.263 7.263 0.647 0.748 0.179 6.870 ms 5.235e+04 1.961e+06
Server Offset 203.123.48.219 -1.164 -1.164 -0.468 -0.131 6.928 7.171 7.171 7.395 8.335 1.959 0.417 ms 0.04807 4.575
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 3.390 3.390 3.626 4.014 4.287 5.365 5.365 0.661 1.976 0.269 4.023 ms 2755 3.91e+04
Server Offset 216.218.192.202 -0.269 -0.269 2.581 2.823 3.080 3.210 3.210 0.499 3.480 0.412 2.782 ms 202 1202
Server Offset 63.145.169.3 -75.402 -75.402 -73.377 -24.004 0.691 2.765 2.765 74.067 78.167 30.739 -30.314 ms -13.98 42
Server Offset 64.62.153.210 2.458 2.458 2.513 2.811 3.084 3.121 3.121 0.571 0.662 0.161 2.803 ms 4458 7.391e+04
Server Offset 64.62.194.189 4.837 4.837 5.025 5.753 6.829 6.887 6.887 1.804 2.050 0.573 5.857 ms 814.1 7776
Server Offset 73.158.5.1 -3.700 -3.700 -1.972 -0.354 0.397 20.468 20.468 2.369 24.168 2.606 -0.357 ms 2.141 34.21
Server Offset SHM(0) -68.332 -66.735 -64.359 -56.077 -49.201 -47.168 -45.013 15.158 19.567 4.545 -56.208 ms -2428 3.3e+04
Server Offset SHM(1) -2,708.000 -807.000 -569.000 -166.000 424.000 819.000 1,941.000 993.000 1,626.000 330.894 -125.866 ns -6.31 20.75
TDOP 0.470 0.520 0.550 0.750 1.180 1.380 1.850 0.630 0.860 0.194 0.787 39.38 174.4
Temp ZONE0 59.072 59.072 59.072 60.148 60.686 60.686 60.686 1.614 1.614 0.454 59.915 °C
nSats 7.000 7.000 8.000 10.000 12.000 12.000 13.000 4.000 5.000 1.129 9.639 nSat 450.8 3576
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!