NTPsec

A-ntpsec-1-hour-stats

Report generated: Mon Oct 19 16:01:05 2020 UTC
Start Time: Mon Oct 19 15:00:36 2020 UTC
End Time: Mon Oct 19 16:01:04 2020 UTC
Report published: Mon Oct 19 09:01:08 2020 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%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -646.000 -559.000 -412.000 169.000 802.000 963.000 1,307.000 1,214.000 1,522.000 362.208 192.551 ns -1.435 3.892
Local Clock Frequency Offset -264.954 -264.786 -263.718 -256.561 -255.463 -254.471 -254.379 8.255 10.315 2.595 -257.860 ppb -1.011e+06 1.015e+08

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 285.000 299.000 318.000 421.000 541.000 581.000 633.000 223.000 282.000 66.123 426.000 ns 177.8 1064

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 52.000 54.000 61.000 88.000 145.000 154.000 160.000 84.000 100.000 27.868 97.617 10e-12 23.7 83.87

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 -646.000 -559.000 -412.000 169.000 802.000 963.000 1,307.000 1,214.000 1,522.000 362.208 192.551 ns -1.435 3.892

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 -264.954 -264.786 -263.718 -256.561 -255.463 -254.471 -254.379 8.255 10.315 2.595 -257.860 ppb -1.011e+06 1.015e+08
Temp ZONE0 57.996 57.996 57.996 59.072 59.072 59.072 59.072 1.076 1.076 0.405 58.760 °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 9.000 9.000 9.000 11.000 11.000 11.000 11.000 2.000 2.000 0.642 10.541 nSat 3710 5.786e+04
TDOP 0.680 0.680 0.690 0.740 1.190 1.220 1.220 0.500 0.540 0.171 0.847 73.98 350.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.471 1.471 1.471 1.700 2.355 2.355 2.355 0.883 0.883 0.214 1.789 ms 424.3 3320

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 90.958 90.958 101.520 153.989 190.208 202.107 202.107 88.688 111.149 27.572 151.374 µs 103.7 524

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

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 2.051 2.051 2.051 2.518 3.128 3.128 3.128 1.078 1.078 0.284 2.445 ms 466.1 3746

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.296 2.296 2.296 2.475 2.838 2.838 2.838 0.542 0.542 0.175 2.510 ms 2412 3.272e+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 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.382 -1.382 -1.382 -0.010 0.741 0.741 0.741 2.123 2.123 0.585 -0.136 ms -6.005 15.96

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) -57.034 -55.125 -53.652 -50.594 -46.918 -45.713 -44.562 6.735 9.412 2.013 -50.432 ms -1.776e+04 4.648e+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) -647.000 -560.000 -413.000 170.000 803.000 964.000 1,308.000 1,216.000 1,524.000 362.897 192.938 ns -1.438 3.893

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.406 0.406 0.406 2.662 9.825 9.825 9.825 9.419 9.419 3.041 3.450 ms 1.585 3.802

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.046 0.046 0.059 0.189 8.709 8.734 8.734 8.650 8.689 2.759 1.657 ms 0.5406 2.814

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

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.195 0.195 0.195 2.742 12.506 12.506 12.506 12.311 12.311 4.714 4.754 ms 0.7621 1.821

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.406 0.406 0.406 1.693 9.971 9.971 9.971 9.565 9.565 3.561 3.662 ms 0.9069 2.15

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 1.097 1.097 1.097 2.598 5.040 5.040 5.040 3.943 3.943 1.234 2.736 ms 5.951 15.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 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.124 0.334 0.517 1.171 2.713 3.988 9.914 2.196 3.655 0.735 1.320 ms 5.327 29.07

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) 161.000 185.000 233.000 419.000 708.000 820.000 1,020.000 475.000 635.000 145.284 433.789 ns 14.52 48.66

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 -264.954 -264.786 -263.718 -256.561 -255.463 -254.471 -254.379 8.255 10.315 2.595 -257.860 ppb -1.011e+06 1.015e+08
Local Clock Time Offset -646.000 -559.000 -412.000 169.000 802.000 963.000 1,307.000 1,214.000 1,522.000 362.208 192.551 ns -1.435 3.892
Local RMS Frequency Jitter 52.000 54.000 61.000 88.000 145.000 154.000 160.000 84.000 100.000 27.868 97.617 10e-12 23.7 83.87
Local RMS Time Jitter 285.000 299.000 318.000 421.000 541.000 581.000 633.000 223.000 282.000 66.123 426.000 ns 177.8 1064
Server Jitter 137.190.2.4 0.406 0.406 0.406 2.662 9.825 9.825 9.825 9.419 9.419 3.041 3.450 ms 1.585 3.802
Server Jitter 192.168.1.12 0.046 0.046 0.059 0.189 8.709 8.734 8.734 8.650 8.689 2.759 1.657 ms 0.5406 2.814
Server Jitter 216.218.192.202 0.195 0.195 0.195 2.742 12.506 12.506 12.506 12.311 12.311 4.714 4.754 ms 0.7621 1.821
Server Jitter 216.218.254.202 0.406 0.406 0.406 1.693 9.971 9.971 9.971 9.565 9.565 3.561 3.662 ms 0.9069 2.15
Server Jitter 73.158.5.1 1.097 1.097 1.097 2.598 5.040 5.040 5.040 3.943 3.943 1.234 2.736 ms 5.951 15.54
Server Jitter SHM(0) 0.124 0.334 0.517 1.171 2.713 3.988 9.914 2.196 3.655 0.735 1.320 ms 5.327 29.07
Server Jitter SHM(1) 161.000 185.000 233.000 419.000 708.000 820.000 1,020.000 475.000 635.000 145.284 433.789 ns 14.52 48.66
Server Offset 137.190.2.4 1.471 1.471 1.471 1.700 2.355 2.355 2.355 0.883 0.883 0.214 1.789 ms 424.3 3320
Server Offset 192.168.1.12 90.958 90.958 101.520 153.989 190.208 202.107 202.107 88.688 111.149 27.572 151.374 µs 103.7 524
Server Offset 216.218.192.202 2.051 2.051 2.051 2.518 3.128 3.128 3.128 1.078 1.078 0.284 2.445 ms 466.1 3746
Server Offset 216.218.254.202 2.296 2.296 2.296 2.475 2.838 2.838 2.838 0.542 0.542 0.175 2.510 ms 2412 3.272e+04
Server Offset 73.158.5.1 -1.382 -1.382 -1.382 -0.010 0.741 0.741 0.741 2.123 2.123 0.585 -0.136 ms -6.005 15.96
Server Offset SHM(0) -57.034 -55.125 -53.652 -50.594 -46.918 -45.713 -44.562 6.735 9.412 2.013 -50.432 ms -1.776e+04 4.648e+05
Server Offset SHM(1) -647.000 -560.000 -413.000 170.000 803.000 964.000 1,308.000 1,216.000 1,524.000 362.897 192.938 ns -1.438 3.893
TDOP 0.680 0.680 0.690 0.740 1.190 1.220 1.220 0.500 0.540 0.171 0.847 73.98 350.2
Temp ZONE0 57.996 57.996 57.996 59.072 59.072 59.072 59.072 1.076 1.076 0.405 58.760 °C
nSats 9.000 9.000 9.000 11.000 11.000 11.000 11.000 2.000 2.000 0.642 10.541 nSat 3710 5.786e+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!