NTPsec

A-ntpsec-12-hour-stats

Report generated: Thu Aug 13 04:01:36 2020 UTC
Start Time: Wed Aug 12 16:01:35 2020 UTC
End Time: Thu Aug 13 04:01:35 2020 UTC
Report published: Wed Aug 12 21:01:41 2020 PDT
Report Period: 0.5 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 -2.014 -1.184 -0.881 -0.223 0.378 0.668 0.977 1.259 1.852 0.385 -0.236 µs -9.216 26.96
Local Clock Frequency Offset -412.292 -412.018 -409.958 -294.510 -250.381 -248.993 -248.611 159.577 163.025 59.228 -314.198 ppb -270 1831

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 169.000 205.000 241.000 366.000 574.000 667.000 796.000 333.000 462.000 101.227 379.126 ns 29.7 114.1

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 37.000 46.000 54.000 94.000 188.000 234.000 287.000 134.000 188.000 40.514 102.847 10e-12 9.517 32.25

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 -2.014 -1.184 -0.881 -0.223 0.378 0.668 0.977 1.259 1.852 0.385 -0.236 µs -9.216 26.96

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 -412.292 -412.018 -409.958 -294.510 -250.381 -248.993 -248.611 159.577 163.025 59.228 -314.198 ppb -270 1831
Temp ZONE0 57.996 57.996 58.534 60.148 61.224 61.762 61.762 2.690 3.766 1.015 59.928 °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 6.000 7.000 7.000 10.000 11.000 12.000 12.000 4.000 5.000 1.226 9.529 nSat 330.4 2373
TDOP 0.520 0.540 0.610 0.830 1.400 1.450 1.760 0.790 0.910 0.228 0.884 33.45 132.4

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 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 -79.880 -30.864 6.123 61.568 110.565 141.503 220.860 104.442 172.367 32.674 61.519 µs 3.267 10.35

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 2001:1948:210:2::4

peer offset 2001:1948:210:2::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:1948:210:2::4 0.155 0.383 0.515 1.385 6.180 6.442 6.779 5.665 6.059 1.630 1.909 ms 2.416 6.725

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 2001:470:0:50::2 (clock.fmt.he.net)

peer offset 2001:470:0:50::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 1.558 2.124 2.218 2.598 3.134 3.351 3.401 0.917 1.226 0.271 2.627 ms 685.9 6203

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 0.252 0.721 2.209 2.620 3.089 3.364 3.486 0.880 2.643 0.407 2.567 ms 162.9 925.4

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 -2.043 -1.586 -0.897 0.278 1.391 2.121 2.404 2.287 3.706 0.706 0.264 ms -2.268 6.794

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) -77.341 -59.591 -56.975 -50.427 -42.272 -40.381 -38.718 14.703 19.210 4.395 -50.002 ms -1933 2.439e+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 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) -2.015 -1.185 -0.882 -0.224 0.379 0.669 0.978 1.261 1.854 0.386 -0.236 µs -9.215 26.93

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 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.011 0.015 0.027 0.142 8.673 9.006 12.526 8.646 8.991 2.435 1.110 ms 0.7914 4.588

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 2001:1948:210:2::4

peer jitter 2001:1948:210:2::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:1948:210:2::4 0.363 0.399 0.696 3.238 24.826 200.537 201.764 24.130 200.138 27.977 10.579 ms 3.851 27.26

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 2001:470:0:50::2 (clock.fmt.he.net)

peer jitter 2001:470:0:50::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.292 0.443 0.564 2.451 16.264 18.106 21.272 15.700 17.663 5.191 5.108 ms 1.123 3.097

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.215 0.248 0.661 2.061 9.168 10.642 11.547 8.507 10.393 3.042 3.422 ms 1.572 3.618

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 0.687 0.690 1.122 2.514 10.307 19.382 19.771 9.185 18.692 3.425 3.950 ms 2.406 8.964

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.137 0.347 0.521 1.328 3.440 6.083 19.359 2.919 5.736 1.086 1.609 ms 4.195 24.51

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) 82.000 125.000 173.000 342.000 708.000 909.000 1,374.000 535.000 784.000 167.830 378.239 ns 6.983 23.45

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 -412.292 -412.018 -409.958 -294.510 -250.381 -248.993 -248.611 159.577 163.025 59.228 -314.198 ppb -270 1831
Local Clock Time Offset -2.014 -1.184 -0.881 -0.223 0.378 0.668 0.977 1.259 1.852 0.385 -0.236 µs -9.216 26.96
Local RMS Frequency Jitter 37.000 46.000 54.000 94.000 188.000 234.000 287.000 134.000 188.000 40.514 102.847 10e-12 9.517 32.25
Local RMS Time Jitter 169.000 205.000 241.000 366.000 574.000 667.000 796.000 333.000 462.000 101.227 379.126 ns 29.7 114.1
Server Jitter 192.168.1.12 0.011 0.015 0.027 0.142 8.673 9.006 12.526 8.646 8.991 2.435 1.110 ms 0.7914 4.588
Server Jitter 2001:1948:210:2::4 0.363 0.399 0.696 3.238 24.826 200.537 201.764 24.130 200.138 27.977 10.579 ms 3.851 27.26
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.292 0.443 0.564 2.451 16.264 18.106 21.272 15.700 17.663 5.191 5.108 ms 1.123 3.097
Server Jitter 216.218.254.202 0.215 0.248 0.661 2.061 9.168 10.642 11.547 8.507 10.393 3.042 3.422 ms 1.572 3.618
Server Jitter 73.158.5.1 0.687 0.690 1.122 2.514 10.307 19.382 19.771 9.185 18.692 3.425 3.950 ms 2.406 8.964
Server Jitter SHM(0) 0.137 0.347 0.521 1.328 3.440 6.083 19.359 2.919 5.736 1.086 1.609 ms 4.195 24.51
Server Jitter SHM(1) 82.000 125.000 173.000 342.000 708.000 909.000 1,374.000 535.000 784.000 167.830 378.239 ns 6.983 23.45
Server Offset 192.168.1.12 -79.880 -30.864 6.123 61.568 110.565 141.503 220.860 104.442 172.367 32.674 61.519 µs 3.267 10.35
Server Offset 2001:1948:210:2::4 0.155 0.383 0.515 1.385 6.180 6.442 6.779 5.665 6.059 1.630 1.909 ms 2.416 6.725
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 1.558 2.124 2.218 2.598 3.134 3.351 3.401 0.917 1.226 0.271 2.627 ms 685.9 6203
Server Offset 216.218.254.202 0.252 0.721 2.209 2.620 3.089 3.364 3.486 0.880 2.643 0.407 2.567 ms 162.9 925.4
Server Offset 73.158.5.1 -2.043 -1.586 -0.897 0.278 1.391 2.121 2.404 2.287 3.706 0.706 0.264 ms -2.268 6.794
Server Offset SHM(0) -77.341 -59.591 -56.975 -50.427 -42.272 -40.381 -38.718 14.703 19.210 4.395 -50.002 ms -1933 2.439e+04
Server Offset SHM(1) -2.015 -1.185 -0.882 -0.224 0.379 0.669 0.978 1.261 1.854 0.386 -0.236 µs -9.215 26.93
TDOP 0.520 0.540 0.610 0.830 1.400 1.450 1.760 0.790 0.910 0.228 0.884 33.45 132.4
Temp ZONE0 57.996 57.996 58.534 60.148 61.224 61.762 61.762 2.690 3.766 1.015 59.928 °C
nSats 6.000 7.000 7.000 10.000 11.000 12.000 12.000 4.000 5.000 1.226 9.529 nSat 330.4 2373
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!