NTPsec

ntpsec-24-hour-stats

Report generated: Thu May 23 00:05:14 2019 UTC
Start Time: Wed May 22 00:04:34 2019 UTC
End Time: Thu May 23 00:04:34 2019 UTC
Report published: Wed May 22 17:07:20 2019 PDT
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%95%StdDev  MeanUnits nessosis
Local Clock Time Offset-5.442-1.056-0.6190.0250.541 0.7695.1061.1601.8250.366-0.000µs-4.639 17.21
Local Clock Frequency Offset-771.179-707.062-701.065-668.015-631.317 -627.838-619.08069.74879.22422.503-666.251ppb-2.877e+048.832e+05

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 Jitter156.000255.000301.000448.000697.000 878.0002,990.000396.000623.000132.949467.413ns 25.9 127.7

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 Jitter0.9411.5461.8002.6264.114 5.14322.4792.3143.5970.7982.752ppb 25.81 165.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-5.442-1.056-0.6190.0250.541 0.7695.1061.1601.8250.366-0.000µs-4.639 17.21

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-771.179-707.062-701.065-668.015-631.317 -627.838-619.08069.74879.22422.503-666.251ppb-2.877e+048.832e+05
Temp ZONE056.92056.92057.45859.07259.610 60.14860.1482.1523.2280.69058.717°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.0007.0007.00010.00012.000 12.00012.0005.0005.0001.4509.652nSat 198 1217
TDOP0.4900.5600.5900.8101.400 1.7602.0200.8101.2000.2590.877 22.25 86.71

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 192.168.1.11

peer offset 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 192.168.1.11-117.417-23.5655.60180.741192.565 235.080278.144186.964258.64555.20682.788µs 2.142 6.063

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 199.102.46.72

peer offset 199.102.46.72 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 199.102.46.72-138.031-55.44046.567511.318819.515 933.2701,051.898772.948988.710218.379487.700µs 5.164 12.37

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 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 204.123.2.5-1.607-1.573-1.470-1.016-0.754 -0.678-0.6390.7170.8950.208-1.059ms-245.9 1625

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 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 216.218.192.202-2.138-2.108-1.970-1.526-1.254 -1.106-0.9620.7161.0030.212-1.563ms-616.3 5395

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 216.218.254.202

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 216.218.254.202-1.742-1.627-1.454-1.026-0.754 -0.679-0.6070.7000.9490.212-1.062ms-237.1 1551

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 63.145.169.3

peer offset 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 63.145.169.3-4.198-4.090-3.779-3.409-3.142 -3.006-2.9700.6361.0840.197-3.426ms -62401.156e+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(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)-76.868-65.802-62.824-54.806-47.549 -44.362-41.75515.27521.4404.879-54.995ms -18852.359e+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 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)-5.443-1.057-0.6200.0260.542 0.7705.1071.1621.8270.367-0.000µs-4.636 17.16

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 192.168.1.11

peer jitter 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 192.168.1.110.0000.0220.0410.1148.659 9.06930.9298.6189.0472.8171.159ms 1.471 15.59

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 199.102.46.72

peer jitter 199.102.46.72 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 199.102.46.720.1370.1770.2260.4798.923 16.86716.9678.69716.6903.4852.253ms0.7994 4.07

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 204.123.2.5

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 204.123.2.50.1290.1550.2200.56012.322 65.20499.75012.10265.05010.3664.204ms 4.968 45

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 216.218.192.202

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 216.218.192.2020.1360.1460.2370.5238.923 12.559142.5138.68612.41312.2063.445ms 7.967 92.64

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 216.218.254.202

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 216.218.254.2020.1770.1860.2280.49910.670 35.344100.65710.44235.15810.0183.671ms 5.665 56.69

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 63.145.169.3

peer jitter 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 63.145.169.30.1040.1590.2440.4808.753 10.99694.6268.51010.8376.1722.465ms 9.406 143.6

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)0.1160.3220.4771.2993.536 5.92915.4033.0595.6071.1061.591ms 3.707 17.61

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.0650.1580.2180.4340.905 1.2706.7710.6871.1120.2360.484µs 7.226 57.05

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-771.179-707.062-701.065-668.015-631.317 -627.838-619.08069.74879.22422.503-666.251ppb-2.877e+048.832e+05
Local Clock Time Offset-5.442-1.056-0.6190.0250.541 0.7695.1061.1601.8250.366-0.000µs-4.639 17.21
Local RMS Frequency Jitter0.9411.5461.8002.6264.114 5.14322.4792.3143.5970.7982.752ppb 25.81 165.9
Local RMS Time Jitter156.000255.000301.000448.000697.000 878.0002,990.000396.000623.000132.949467.413ns 25.9 127.7
Peer Jitter 192.168.1.110.0000.0220.0410.1148.659 9.06930.9298.6189.0472.8171.159ms 1.471 15.59
Peer Jitter 199.102.46.720.1370.1770.2260.4798.923 16.86716.9678.69716.6903.4852.253ms0.7994 4.07
Peer Jitter 204.123.2.50.1290.1550.2200.56012.322 65.20499.75012.10265.05010.3664.204ms 4.968 45
Peer Jitter 216.218.192.2020.1360.1460.2370.5238.923 12.559142.5138.68612.41312.2063.445ms 7.967 92.64
Peer Jitter 216.218.254.2020.1770.1860.2280.49910.670 35.344100.65710.44235.15810.0183.671ms 5.665 56.69
Peer Jitter 63.145.169.30.1040.1590.2440.4808.753 10.99694.6268.51010.8376.1722.465ms 9.406 143.6
Peer Jitter SHM(0)0.1160.3220.4771.2993.536 5.92915.4033.0595.6071.1061.591ms 3.707 17.61
Peer Jitter SHM(1)0.0650.1580.2180.4340.905 1.2706.7710.6871.1120.2360.484µs 7.226 57.05
Peer Offset 192.168.1.11-117.417-23.5655.60180.741192.565 235.080278.144186.964258.64555.20682.788µs 2.142 6.063
Peer Offset 199.102.46.72-138.031-55.44046.567511.318819.515 933.2701,051.898772.948988.710218.379487.700µs 5.164 12.37
Peer Offset 204.123.2.5-1.607-1.573-1.470-1.016-0.754 -0.678-0.6390.7170.8950.208-1.059ms-245.9 1625
Peer Offset 216.218.192.202-2.138-2.108-1.970-1.526-1.254 -1.106-0.9620.7161.0030.212-1.563ms-616.3 5395
Peer Offset 216.218.254.202-1.742-1.627-1.454-1.026-0.754 -0.679-0.6070.7000.9490.212-1.062ms-237.1 1551
Peer Offset 63.145.169.3-4.198-4.090-3.779-3.409-3.142 -3.006-2.9700.6361.0840.197-3.426ms -62401.156e+05
Peer Offset SHM(0)-76.868-65.802-62.824-54.806-47.549 -44.362-41.75515.27521.4404.879-54.995ms -18852.359e+04
Peer Offset SHM(1)-5.443-1.057-0.6200.0260.542 0.7705.1071.1621.8270.367-0.000µs-4.636 17.16
TDOP0.4900.5600.5900.8101.400 1.7602.0200.8101.2000.2590.877 22.25 86.71
Temp ZONE056.92056.92057.45859.07259.610 60.14860.1482.1523.2280.69058.717°C
nSats6.0007.0007.00010.00012.000 12.00012.0005.0005.0001.4509.652nSat 198 1217
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!