NTPsec

tock

Report generated: Tue Feb 18 11:15:44 2020 UTC
Start Time: Tue Feb 11 11:15:44 2020 UTC
End Time: Tue Feb 18 11:15:44 2020 UTC
Report Period: 7.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 -1,979.000 -750.000 -428.000 15.000 429.000 721.000 1,547.000 857.000 1,471.000 267.648 10.440 ns -4.035 12.79
Local Clock Frequency Offset -21.726 -21.716 -21.669 -21.504 -21.393 -21.384 -21.382 0.276 0.332 0.078 -21.516 ppm -2.147e+07 5.968e+09

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 89.000 118.000 138.000 195.000 272.000 312.000 427.000 134.000 194.000 41.177 198.764 ns 68.06 313.9

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 18.000 25.000 29.000 44.000 142.000 254.000 718.000 113.000 229.000 45.572 58.600 10e-12 5.285 38.97

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 -1,979.000 -750.000 -428.000 15.000 429.000 721.000 1,547.000 857.000 1,471.000 267.648 10.440 ns -4.035 12.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 -21.726 -21.716 -21.669 -21.504 -21.393 -21.384 -21.382 0.276 0.332 0.078 -21.516 ppm -2.147e+07 5.968e+09
Temp ZONE0 49.660 50.147 51.121 52.582 53.556 54.043 55.017 2.435 3.896 0.849 52.409 °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.028 6.712 nSat 185.4 1120
TDOP 1.010 1.070 1.180 1.640 3.900 6.630 10.190 2.720 5.560 1.113 1.982 6.209 32.08

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 -73.004 -57.814 -51.359 -34.433 25.430 34.270 43.032 76.789 92.084 22.952 -27.395 µs -15.91 44.8

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 -119.574 -88.226 -81.607 -67.992 -55.878 -50.900 -41.070 25.729 37.326 7.631 -68.481 µs -1023 1.051e+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) -1,980.000 -751.000 -429.000 16.000 430.000 722.000 1,548.000 859.000 1,473.000 268.350 10.497 ns -4.033 12.76

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) -24.040 -13.827 -10.015 2.795 15.465 19.358 26.313 25.480 33.185 7.797 2.760 ms -2.227 5.167

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 2.713 5.324 7.635 21.626 65.315 75.790 122.061 57.680 70.466 16.873 25.388 µs 3.034 9.224

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 2.291 5.672 8.246 18.054 32.138 45.319 517.832 23.892 39.647 9.270 18.787 µs 22.06 1009

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) 30.000 77.000 101.000 192.000 373.000 480.000 877.000 272.000 403.000 85.606 208.929 ns 8.533 29.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 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.576 1.367 1.979 4.095 7.692 9.750 16.949 5.714 8.383 1.790 4.391 ms 8.376 27.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -21.726 -21.716 -21.669 -21.504 -21.393 -21.384 -21.382 0.276 0.332 0.078 -21.516 ppm -2.147e+07 5.968e+09
Local Clock Time Offset -1,979.000 -750.000 -428.000 15.000 429.000 721.000 1,547.000 857.000 1,471.000 267.648 10.440 ns -4.035 12.79
Local RMS Frequency Jitter 18.000 25.000 29.000 44.000 142.000 254.000 718.000 113.000 229.000 45.572 58.600 10e-12 5.285 38.97
Local RMS Time Jitter 89.000 118.000 138.000 195.000 272.000 312.000 427.000 134.000 194.000 41.177 198.764 ns 68.06 313.9
Server Jitter 10.4.2.51 2.713 5.324 7.635 21.626 65.315 75.790 122.061 57.680 70.466 16.873 25.388 µs 3.034 9.224
Server Jitter 10.4.2.53 2.291 5.672 8.246 18.054 32.138 45.319 517.832 23.892 39.647 9.270 18.787 µs 22.06 1009
Server Jitter PPS(0) 30.000 77.000 101.000 192.000 373.000 480.000 877.000 272.000 403.000 85.606 208.929 ns 8.533 29.2
Server Jitter SHM(0) 0.576 1.367 1.979 4.095 7.692 9.750 16.949 5.714 8.383 1.790 4.391 ms 8.376 27.06
Server Offset 10.4.2.51 -73.004 -57.814 -51.359 -34.433 25.430 34.270 43.032 76.789 92.084 22.952 -27.395 µs -15.91 44.8
Server Offset 10.4.2.53 -119.574 -88.226 -81.607 -67.992 -55.878 -50.900 -41.070 25.729 37.326 7.631 -68.481 µs -1023 1.051e+04
Server Offset PPS(0) -1,980.000 -751.000 -429.000 16.000 430.000 722.000 1,548.000 859.000 1,473.000 268.350 10.497 ns -4.033 12.76
Server Offset SHM(0) -24.040 -13.827 -10.015 2.795 15.465 19.358 26.313 25.480 33.185 7.797 2.760 ms -2.227 5.167
TDOP 1.010 1.070 1.180 1.640 3.900 6.630 10.190 2.720 5.560 1.113 1.982 6.209 32.08
Temp ZONE0 49.660 50.147 51.121 52.582 53.556 54.043 55.017 2.435 3.896 0.849 52.409 °C
nSats 5.000 5.000 5.000 7.000 8.000 9.000 9.000 3.000 4.000 1.028 6.712 nSat 185.4 1120
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!