NTPsec

tock

Report generated: Sat Jan 25 17:15:42 2020 UTC
Start Time: Fri Jan 24 17:15:42 2020 UTC
End Time: Sat Jan 25 17:15:42 2020 UTC
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 -535.000 -334.000 -226.000 32.000 336.000 600.000 1,057.000 562.000 934.000 180.063 41.521 ns -2.072 6.722
Local Clock Frequency Offset -21.612 -21.611 -21.610 -21.559 -21.556 -21.556 -21.556 0.054 0.056 0.0178 -21.569 ppm -1.786e+09 2.167e+12

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 90.000 115.000 134.000 192.000 264.000 296.000 347.000 130.000 181.000 39.353 194.090 ns 72.97 340.8

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 20.000 24.000 27.000 38.000 67.000 138.000 190.000 40.000 114.000 18.596 41.779 10e-12 10.11 62.08

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 -535.000 -334.000 -226.000 32.000 336.000 600.000 1,057.000 562.000 934.000 180.063 41.521 ns -2.072 6.722

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 -21.612 -21.611 -21.610 -21.559 -21.556 -21.556 -21.556 0.054 0.056 0.0178 -21.569 ppm -1.786e+09 2.167e+12
Temp ZONE0 51.608 52.095 52.582 53.069 54.043 54.530 55.017 1.461 2.435 0.561 53.223 °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 5.000 5.000 5.000 7.000 8.000 9.000 9.000 3.000 4.000 1.039 6.711 nSat 179.5 1073
TDOP 1.010 1.070 1.180 1.660 4.150 6.620 9.980 2.970 5.550 1.156 2.016 5.937 30.13

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. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



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 10.4.2.51

peer offset 10.4.2.51 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.4.2.51 -61.164 -53.494 -49.955 -40.302 -1.124 26.506 33.089 48.831 80.000 14.623 -37.381 µs -52.61 205.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 10.4.2.53

peer offset 10.4.2.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.4.2.53 -117.390 -90.253 -83.868 -71.405 -59.143 -53.965 -44.754 24.725 36.288 7.593 -71.587 µs -1166 1.249e+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 PPS(0)

peer offset PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset PPS(0) -536.000 -335.000 -227.000 33.000 337.000 600.000 1,058.000 564.000 935.000 180.772 41.670 ns -2.081 6.709

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) -18.305 -12.825 -8.943 3.202 15.497 19.993 24.660 24.440 32.819 7.546 3.182 ms -1.909 4.539

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 10.4.2.51

peer jitter 10.4.2.51 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.4.2.51 3.246 4.695 7.525 21.479 47.715 64.173 92.333 40.190 59.478 12.880 22.555 µs 3.977 13.13

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 10.4.2.53

peer jitter 10.4.2.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.4.2.53 3.220 5.879 8.396 18.865 35.459 50.082 65.146 27.063 44.203 8.501 19.763 µs 7.69 27.54

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 PPS(0)

peer jitter PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter PPS(0) 46.000 76.000 102.000 186.000 354.000 438.000 636.000 252.000 362.000 77.833 199.681 ns 9.633 32.16

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.510 1.354 1.904 4.131 8.083 9.884 15.455 6.179 8.530 1.889 4.431 ms 7.409 23.32

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 -21.612 -21.611 -21.610 -21.559 -21.556 -21.556 -21.556 0.054 0.056 0.0178 -21.569 ppm -1.786e+09 2.167e+12
Local Clock Time Offset -535.000 -334.000 -226.000 32.000 336.000 600.000 1,057.000 562.000 934.000 180.063 41.521 ns -2.072 6.722
Local RMS Frequency Jitter 20.000 24.000 27.000 38.000 67.000 138.000 190.000 40.000 114.000 18.596 41.779 10e-12 10.11 62.08
Local RMS Time Jitter 90.000 115.000 134.000 192.000 264.000 296.000 347.000 130.000 181.000 39.353 194.090 ns 72.97 340.8
Server Jitter 10.4.2.51 3.246 4.695 7.525 21.479 47.715 64.173 92.333 40.190 59.478 12.880 22.555 µs 3.977 13.13
Server Jitter 10.4.2.53 3.220 5.879 8.396 18.865 35.459 50.082 65.146 27.063 44.203 8.501 19.763 µs 7.69 27.54
Server Jitter PPS(0) 46.000 76.000 102.000 186.000 354.000 438.000 636.000 252.000 362.000 77.833 199.681 ns 9.633 32.16
Server Jitter SHM(0) 0.510 1.354 1.904 4.131 8.083 9.884 15.455 6.179 8.530 1.889 4.431 ms 7.409 23.32
Server Offset 10.4.2.51 -61.164 -53.494 -49.955 -40.302 -1.124 26.506 33.089 48.831 80.000 14.623 -37.381 µs -52.61 205.3
Server Offset 10.4.2.53 -117.390 -90.253 -83.868 -71.405 -59.143 -53.965 -44.754 24.725 36.288 7.593 -71.587 µs -1166 1.249e+04
Server Offset PPS(0) -536.000 -335.000 -227.000 33.000 337.000 600.000 1,058.000 564.000 935.000 180.772 41.670 ns -2.081 6.709
Server Offset SHM(0) -18.305 -12.825 -8.943 3.202 15.497 19.993 24.660 24.440 32.819 7.546 3.182 ms -1.909 4.539
TDOP 1.010 1.070 1.180 1.660 4.150 6.620 9.980 2.970 5.550 1.156 2.016 5.937 30.13
Temp ZONE0 51.608 52.095 52.582 53.069 54.043 54.530 55.017 1.461 2.435 0.561 53.223 °C
nSats 5.000 5.000 5.000 7.000 8.000 9.000 9.000 3.000 4.000 1.039 6.711 nSat 179.5 1073
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!