NTPsec

A-ntpsec-3-hour-stats

Report generated: Sun Sep 26 13:02:16 2021 UTC
Start Time: Sun Sep 26 10:02:16 2021 UTC
End Time: Sun Sep 26 13:02:16 2021 UTC
Report published: Sun Sep 26 06:02:20 2021 PDT
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 -48.643 -34.514 -7.974 0.920 2.564 2.971 3.353 10.538 37.485 5.860 -0.256 µs -9.367 60.36
Local Clock Frequency Offset -188.797 -188.278 -182.800 -158.676 -147.217 -145.157 -141.052 35.583 43.121 11.233 -161.434 ppb -3679 5.728e+04

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 0.261 0.284 0.339 0.574 9.789 13.765 16.608 9.450 13.481 3.090 2.074 µs 1.269 5.402

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 0.103 0.111 0.127 0.347 3.876 5.034 5.812 3.749 4.923 1.181 0.900 ppb 1.337 5.011

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 -48.643 -34.514 -7.974 0.920 2.564 2.971 3.353 10.538 37.485 5.860 -0.256 µs -9.367 60.36

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 -188.797 -188.278 -182.800 -158.676 -147.217 -145.157 -141.052 35.583 43.121 11.233 -161.434 ppb -3679 5.728e+04
Temp ZONE0 57.996 57.996 57.996 57.996 58.534 59.072 59.072 0.538 1.076 0.313 58.247 °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 7.000 9.000 9.000 10.000 10.000 2.000 3.000 0.636 8.528 nSat 1945 2.457e+04
TDOP 0.650 0.650 0.690 0.860 1.410 1.420 1.420 0.720 0.770 0.155 0.873 115 634.2

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 137.190.2.4

peer offset 137.190.2.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 137.190.2.4 1.510 1.510 1.534 1.699 1.911 2.055 2.055 0.376 0.545 0.118 1.722 ms 2558 3.537e+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 192.168.1.12

peer offset 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.12 -119.040 -16.131 106.249 250.334 346.184 387.073 387.695 239.935 403.204 82.356 238.528 µs 11.5 31.85

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.438 2.438 2.573 2.722 2.900 3.042 3.042 0.327 0.604 0.115 2.720 ms 1.178e+04 2.691e+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 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 2.545 2.545 2.587 2.744 2.937 2.939 2.939 0.350 0.394 0.103 2.744 ms 1.673e+04 4.291e+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 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 -1.025 -1.025 -0.969 -0.182 0.472 0.520 0.520 1.441 1.545 0.424 -0.240 ms -8.835 24.72

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) -60.077 -54.761 -52.778 -49.627 -47.207 -46.002 -44.395 5.571 8.759 1.761 -49.736 ms -2.512e+04 7.373e+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 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) -48.644 -34.515 -7.975 0.921 2.565 2.972 3.354 10.540 37.487 5.861 -0.256 µs -9.365 60.36

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 137.190.2.4

peer jitter 137.190.2.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 137.190.2.4 0.178 0.178 0.211 0.846 8.703 8.781 8.781 8.493 8.603 2.018 1.546 ms 1.727 6.805

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

peer jitter 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.12 0.100 0.111 0.130 0.412 19.943 23.229 26.543 19.813 23.119 6.755 4.601 ms 0.4556 2.609

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.135 0.135 0.137 0.898 1.565 3.362 3.362 1.428 3.227 0.653 0.825 ms 3.079 12.62

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 0.175 0.175 0.183 1.190 5.292 8.813 8.813 5.109 8.638 1.691 1.613 ms 2.593 10.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 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.915 0.915 1.034 2.304 9.484 9.607 9.607 8.449 8.692 3.359 4.581 ms 1.587 2.873

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.203 0.329 0.463 1.133 2.831 4.793 12.244 2.369 4.464 0.872 1.360 ms 4.338 22.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.091 0.154 0.213 0.440 17.146 32.372 48.680 16.933 32.218 6.145 2.432 µs 1.834 12.72

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -188.797 -188.278 -182.800 -158.676 -147.217 -145.157 -141.052 35.583 43.121 11.233 -161.434 ppb -3679 5.728e+04
Local Clock Time Offset -48.643 -34.514 -7.974 0.920 2.564 2.971 3.353 10.538 37.485 5.860 -0.256 µs -9.367 60.36
Local RMS Frequency Jitter 0.103 0.111 0.127 0.347 3.876 5.034 5.812 3.749 4.923 1.181 0.900 ppb 1.337 5.011
Local RMS Time Jitter 0.261 0.284 0.339 0.574 9.789 13.765 16.608 9.450 13.481 3.090 2.074 µs 1.269 5.402
Server Jitter 137.190.2.4 0.178 0.178 0.211 0.846 8.703 8.781 8.781 8.493 8.603 2.018 1.546 ms 1.727 6.805
Server Jitter 192.168.1.12 0.100 0.111 0.130 0.412 19.943 23.229 26.543 19.813 23.119 6.755 4.601 ms 0.4556 2.609
Server Jitter 216.218.254.202 0.135 0.135 0.137 0.898 1.565 3.362 3.362 1.428 3.227 0.653 0.825 ms 3.079 12.62
Server Jitter 66.220.9.122 0.175 0.175 0.183 1.190 5.292 8.813 8.813 5.109 8.638 1.691 1.613 ms 2.593 10.39
Server Jitter 73.158.5.1 0.915 0.915 1.034 2.304 9.484 9.607 9.607 8.449 8.692 3.359 4.581 ms 1.587 2.873
Server Jitter SHM(0) 0.203 0.329 0.463 1.133 2.831 4.793 12.244 2.369 4.464 0.872 1.360 ms 4.338 22.57
Server Jitter SHM(1) 0.091 0.154 0.213 0.440 17.146 32.372 48.680 16.933 32.218 6.145 2.432 µs 1.834 12.72
Server Offset 137.190.2.4 1.510 1.510 1.534 1.699 1.911 2.055 2.055 0.376 0.545 0.118 1.722 ms 2558 3.537e+04
Server Offset 192.168.1.12 -119.040 -16.131 106.249 250.334 346.184 387.073 387.695 239.935 403.204 82.356 238.528 µs 11.5 31.85
Server Offset 216.218.254.202 2.438 2.438 2.573 2.722 2.900 3.042 3.042 0.327 0.604 0.115 2.720 ms 1.178e+04 2.691e+05
Server Offset 66.220.9.122 2.545 2.545 2.587 2.744 2.937 2.939 2.939 0.350 0.394 0.103 2.744 ms 1.673e+04 4.291e+05
Server Offset 73.158.5.1 -1.025 -1.025 -0.969 -0.182 0.472 0.520 0.520 1.441 1.545 0.424 -0.240 ms -8.835 24.72
Server Offset SHM(0) -60.077 -54.761 -52.778 -49.627 -47.207 -46.002 -44.395 5.571 8.759 1.761 -49.736 ms -2.512e+04 7.373e+05
Server Offset SHM(1) -48.644 -34.515 -7.975 0.921 2.565 2.972 3.354 10.540 37.487 5.861 -0.256 µs -9.365 60.36
TDOP 0.650 0.650 0.690 0.860 1.410 1.420 1.420 0.720 0.770 0.155 0.873 115 634.2
Temp ZONE0 57.996 57.996 57.996 57.996 58.534 59.072 59.072 0.538 1.076 0.313 58.247 °C
nSats 7.000 7.000 7.000 9.000 9.000 10.000 10.000 2.000 3.000 0.636 8.528 nSat 1945 2.457e+04
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!