NTPsec

itchy

Report generated: Sat Jun 10 00:15:01 2023 UTC
Start Time: Fri Jun 9 00:15:01 2023 UTC
End Time: Sat Jun 10 00:15:01 2023 UTC
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%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -282.685 -282.685 -251.361 -42.506 192.289 269.865 269.865 443.650 552.550 127.204 -25.387 µs -5.169 12.49
Local Clock Frequency Offset 67.088 67.088 67.101 67.141 67.208 67.210 67.210 0.107 0.122 0.034 67.147 ppm 7.509e+09 1.47e+13

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 82.249 82.249 92.901 117.413 183.821 196.333 196.333 90.920 114.084 25.863 122.272 µs 64.24 299.3

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 8.320 8.320 9.406 13.750 16.583 17.740 17.740 7.177 9.420 2.138 13.351 ppb 159.6 916.7

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 -282.685 -282.685 -251.361 -42.506 192.289 269.865 269.865 443.650 552.550 127.204 -25.387 µs -5.169 12.49

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



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

peer offset 192.12.19.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.12.19.20 -180.755 -180.755 -141.354 59.717 289.581 478.203 478.203 430.935 658.958 133.481 69.589 µs -1.05 3.876

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 204.34.198.40

peer offset 204.34.198.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.34.198.40 -16.117 -16.117 -15.997 -15.670 -15.455 -15.452 -15.452 0.542 0.665 0.160 -15.696 ms -9.797e+05 9.732e+07

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 2600:3c03::f03c:91ff:fe0c:601c (scratchy.podsix.net)

peer offset 2600:3c03::f03c:91ff:fe0c:601c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c03::f03c:91ff:fe0c:601c (scratchy.podsix.net) -2.537 -2.537 -1.786 -1.193 -0.583 -0.518 -0.518 1.203 2.019 0.389 -1.185 ms -78.79 377.1

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 2610:20:6f96:96::4 (time-d-b.nist.gov)

peer offset 2610:20:6f96:96::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2610:20:6f96:96::4 (time-d-b.nist.gov) -0.293 -0.293 -0.201 0.065 0.377 1.269 1.269 0.578 1.562 0.233 0.075 ms -0.04105 9.973

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

peer jitter 192.12.19.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.12.19.20 59.346 59.346 84.239 142.309 300.818 445.814 445.814 216.579 386.468 70.710 153.373 µs 6.942 26.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.



Server Jitter 204.34.198.40

peer jitter 204.34.198.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.34.198.40 61.658 61.658 71.948 153.401 394.664 431.000 431.000 322.716 369.342 89.599 179.726 µs 5.099 15.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.



Server Jitter 2600:3c03::f03c:91ff:fe0c:601c (scratchy.podsix.net)

peer jitter 2600:3c03::f03c:91ff:fe0c:601c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c03::f03c:91ff:fe0c:601c (scratchy.podsix.net) 0.043 0.043 0.064 0.232 1.046 2.281 2.281 0.981 2.238 0.390 0.427 ms 1.963 8.654

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 2610:20:6f96:96::4 (time-d-b.nist.gov)

peer jitter 2610:20:6f96:96::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2610:20:6f96:96::4 (time-d-b.nist.gov) 0.037 0.037 0.061 0.172 0.795 1.061 1.061 0.734 1.024 0.223 0.250 ms 2.313 7.148

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 67.088 67.088 67.101 67.141 67.208 67.210 67.210 0.107 0.122 0.034 67.147 ppm 7.509e+09 1.47e+13
Local Clock Time Offset -282.685 -282.685 -251.361 -42.506 192.289 269.865 269.865 443.650 552.550 127.204 -25.387 µs -5.169 12.49
Local RMS Frequency Jitter 8.320 8.320 9.406 13.750 16.583 17.740 17.740 7.177 9.420 2.138 13.351 ppb 159.6 916.7
Local RMS Time Jitter 82.249 82.249 92.901 117.413 183.821 196.333 196.333 90.920 114.084 25.863 122.272 µs 64.24 299.3
Server Jitter 192.12.19.20 59.346 59.346 84.239 142.309 300.818 445.814 445.814 216.579 386.468 70.710 153.373 µs 6.942 26.06
Server Jitter 204.34.198.40 61.658 61.658 71.948 153.401 394.664 431.000 431.000 322.716 369.342 89.599 179.726 µs 5.099 15.06
Server Jitter 2600:3c03::f03c:91ff:fe0c:601c (scratchy.podsix.net) 0.043 0.043 0.064 0.232 1.046 2.281 2.281 0.981 2.238 0.390 0.427 ms 1.963 8.654
Server Jitter 2610:20:6f96:96::4 (time-d-b.nist.gov) 0.037 0.037 0.061 0.172 0.795 1.061 1.061 0.734 1.024 0.223 0.250 ms 2.313 7.148
Server Offset 192.12.19.20 -180.755 -180.755 -141.354 59.717 289.581 478.203 478.203 430.935 658.958 133.481 69.589 µs -1.05 3.876
Server Offset 204.34.198.40 -16.117 -16.117 -15.997 -15.670 -15.455 -15.452 -15.452 0.542 0.665 0.160 -15.696 ms -9.797e+05 9.732e+07
Server Offset 2600:3c03::f03c:91ff:fe0c:601c (scratchy.podsix.net) -2.537 -2.537 -1.786 -1.193 -0.583 -0.518 -0.518 1.203 2.019 0.389 -1.185 ms -78.79 377.1
Server Offset 2610:20:6f96:96::4 (time-d-b.nist.gov) -0.293 -0.293 -0.201 0.065 0.377 1.269 1.269 0.578 1.562 0.233 0.075 ms -0.04105 9.973
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!