NTPsec

B-ntpsec-1-hour-stats

Report generated: Thu May 23 01:01:05 2019 UTC
Start Time: Thu May 23 00:00:35 2019 UTC
End Time: Thu May 23 01:01:03 2019 UTC
Report published: Wed May 22 18:01:25 2019 PDT
Report Period: 0.0 days

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Local Clock Time Offset-3.386-1.623-1.0210.0170.925 1.3361.7641.9462.9590.612-0.001µs-4.568 13.74
Local Clock Frequency Offset-6.250-6.244-6.238-6.223-6.192 -6.180-6.1660.0470.0640.0139-6.220ppm-8.955e+074.006e+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%95%StdDev  MeanUnits nessosis
Local RMS Time Jitter0.3570.4500.5040.7181.102 1.3601.6960.5980.9100.1850.748µs 38.29 159.6

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%95%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter2.1442.7563.1964.5306.906 8.27010.0663.7105.5141.1134.693ppb 44.05 187.9

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%95%StdDev  MeanUnits nessosis
Local Clock Offset-3.386-1.623-1.0210.0170.925 1.3361.7641.9462.9590.612-0.001µs-4.568 13.74

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%95%StdDev  MeanUnits nessosis
Local Clock Frequency Offset-6.250-6.244-6.238-6.223-6.192 -6.180-6.1660.0470.0640.0139-6.220ppm-8.955e+074.006e+10
Temp ZONE047.23647.23647.23647.77448.312 48.31248.3121.0761.0760.31047.792°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%95%StdDev  MeanUnits nessosis
nSats6.0006.0007.0007.0008.000 9.0009.0001.0003.0000.6117.400nSat 14051.6e+04
TDOP0.6700.6700.9401.2801.350 1.6801.6800.4101.0100.1991.186 137.7 758.7

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.



Peer Offsets

peer offsets plot

The offset of all refclocks, peers 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.



Peer Offset 162.213.2.253

peer offset 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 162.213.2.253-1.212-1.212-1.212-1.076-0.913 -0.913-0.9130.2990.2990.099-1.086ms -17592.15e+04

The offset of a peer or 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 remote. 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 peer 80µs; 90% ranges for WAN servers 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.



Peer Offset 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 169.229.128.134-1.981-1.981-1.981-1.475-1.234 -1.234-1.2340.7470.7470.206-1.537ms -629 5549

The offset of a peer or 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 remote. 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 peer 80µs; 90% ranges for WAN servers 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.



Peer Offset 169.229.128.142

peer offset 169.229.128.142 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 169.229.128.142-1.930-1.930-1.930-1.349-1.116 -1.116-1.1160.8140.8140.209-1.384ms -467 3767

The offset of a peer or 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 remote. 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 peer 80µs; 90% ranges for WAN servers 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.



Peer Offset 192.168.1.41

peer offset 192.168.1.41 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 192.168.1.4183.31583.315121.303212.246252.579 276.178276.178131.276192.86337.334206.171µs 104.9 524.9

The offset of a peer or 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 remote. 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 peer 80µs; 90% ranges for WAN servers 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.



Peer Offset 76.14.161.109

peer offset 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 76.14.161.109-5.391-5.391-5.391-4.436-2.440 -2.440-2.4402.9512.9510.782-4.424ms -314 2204

The offset of a peer or 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 remote. 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 peer 80µs; 90% ranges for WAN servers 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.



Peer Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset SHM(0)-374.010-366.166-356.378-328.716-307.147 -299.657-283.25949.23166.50915.131-329.993ms-1.193e+042.738e+05

The offset of a peer or 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 remote. 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 peer 80µs; 90% ranges for WAN servers 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.



Peer Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset SHM(1)-3.387-1.624-1.0220.0180.925 1.3371.7651.9472.9610.613-0.001µs-4.567 13.72

The offset of a peer or 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 remote. 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 peer 80µs; 90% ranges for WAN servers 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.



Peer Jitters

peer jitters plot

The RMS Jitter of all refclocks, peers 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.



Peer Jitter 162.213.2.253

peer jitter 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 162.213.2.2530.2620.2620.2620.6358.845 8.8458.8458.5838.5833.1241.867ms0.5085 2.317

The RMS Jitter of a remote peer or 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.



Peer Jitter 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 169.229.128.1340.1330.1330.1330.4998.973 8.9738.9738.8408.8404.0593.419ms0.1178 1.132

The RMS Jitter of a remote peer or 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.



Peer Jitter 169.229.128.142

peer jitter 169.229.128.142 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 169.229.128.1420.2650.2650.2650.49811.712 11.71211.71211.44711.4473.6032.055ms0.5701 2.834

The RMS Jitter of a remote peer or 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.



Peer Jitter 192.168.1.41

peer jitter 192.168.1.41 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 192.168.1.410.0150.0150.0410.1046.538 8.6088.6086.4968.5922.3181.065ms 0.558 3.717

The RMS Jitter of a remote peer or 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.



Peer Jitter 76.14.161.109

peer jitter 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 76.14.161.1090.7080.7080.7083.21225.984 25.98425.98425.27625.2768.8047.637ms 1.01 2.656

The RMS Jitter of a remote peer or 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.



Peer Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter SHM(0)2.4074.5905.78911.35522.547 26.64338.79516.75822.0535.03612.328ms 8.415 27.22

The RMS Jitter of a remote peer or 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.



Peer Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter SHM(1)0.1760.2790.3760.7481.509 2.0653.6661.1331.7860.3770.825µs 6.809 25.72

The RMS Jitter of a remote peer or 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%95%StdDev  MeanUnits nessosis
Local Clock Frequency Offset-6.250-6.244-6.238-6.223-6.192 -6.180-6.1660.0470.0640.0139-6.220ppm-8.955e+074.006e+10
Local Clock Time Offset-3.386-1.623-1.0210.0170.925 1.3361.7641.9462.9590.612-0.001µs-4.568 13.74
Local RMS Frequency Jitter2.1442.7563.1964.5306.906 8.27010.0663.7105.5141.1134.693ppb 44.05 187.9
Local RMS Time Jitter0.3570.4500.5040.7181.102 1.3601.6960.5980.9100.1850.748µs 38.29 159.6
Peer Jitter 162.213.2.2530.2620.2620.2620.6358.845 8.8458.8458.5838.5833.1241.867ms0.5085 2.317
Peer Jitter 169.229.128.1340.1330.1330.1330.4998.973 8.9738.9738.8408.8404.0593.419ms0.1178 1.132
Peer Jitter 169.229.128.1420.2650.2650.2650.49811.712 11.71211.71211.44711.4473.6032.055ms0.5701 2.834
Peer Jitter 192.168.1.410.0150.0150.0410.1046.538 8.6088.6086.4968.5922.3181.065ms 0.558 3.717
Peer Jitter 76.14.161.1090.7080.7080.7083.21225.984 25.98425.98425.27625.2768.8047.637ms 1.01 2.656
Peer Jitter SHM(0)2.4074.5905.78911.35522.547 26.64338.79516.75822.0535.03612.328ms 8.415 27.22
Peer Jitter SHM(1)0.1760.2790.3760.7481.509 2.0653.6661.1331.7860.3770.825µs 6.809 25.72
Peer Offset 162.213.2.253-1.212-1.212-1.212-1.076-0.913 -0.913-0.9130.2990.2990.099-1.086ms -17592.15e+04
Peer Offset 169.229.128.134-1.981-1.981-1.981-1.475-1.234 -1.234-1.2340.7470.7470.206-1.537ms -629 5549
Peer Offset 169.229.128.142-1.930-1.930-1.930-1.349-1.116 -1.116-1.1160.8140.8140.209-1.384ms -467 3767
Peer Offset 192.168.1.4183.31583.315121.303212.246252.579 276.178276.178131.276192.86337.334206.171µs 104.9 524.9
Peer Offset 76.14.161.109-5.391-5.391-5.391-4.436-2.440 -2.440-2.4402.9512.9510.782-4.424ms -314 2204
Peer Offset SHM(0)-374.010-366.166-356.378-328.716-307.147 -299.657-283.25949.23166.50915.131-329.993ms-1.193e+042.738e+05
Peer Offset SHM(1)-3.387-1.624-1.0220.0180.925 1.3371.7651.9472.9610.613-0.001µs-4.567 13.72
TDOP0.6700.6700.9401.2801.350 1.6801.6800.4101.0100.1991.186 137.7 758.7
Temp ZONE047.23647.23647.23647.77448.312 48.31248.3121.0761.0760.31047.792°C
nSats6.0006.0007.0007.0008.000 9.0009.0001.0003.0000.6117.400nSat 14051.6e+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 Peer 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 remote clock 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!