NTPsec

itchy

Report generated: Sat Jun 20 07:15:02 2026 UTC
Start Time: Fri Jun 19 07:15:02 2026 UTC
End Time: Sat Jun 20 07:15:02 2026 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 -494.137 -494.137 -367.155 58.435 484.970 682.125 682.125 852.125 1,176.262 265.627 51.587 µs -2.861 6.591
Local Clock Frequency Offset 17.927 17.927 17.967 18.034 18.108 18.116 18.116 0.141 0.189 0.041 18.033 ppm 8.475e+07 3.722e+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%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 194.567 194.567 212.306 328.108 488.882 550.820 550.820 276.576 356.253 78.145 335.955 µs 46.29 193.2

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 15.483 15.483 16.770 25.320 38.776 41.453 41.453 22.006 25.970 6.658 26.170 ppb 34.37 132.3

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 -494.137 -494.137 -367.155 58.435 484.970 682.125 682.125 852.125 1,176.262 265.627 51.587 µs -2.861 6.591

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 1.565 1.565 1.572 2.197 2.590 2.747 2.747 1.018 1.182 0.253 2.156 ms 449.7 3550

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 -13.967 -13.967 -13.497 -13.021 -12.616 -12.259 -12.259 0.881 1.708 0.303 -13.026 ms -8.501e+04 3.742e+06

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) 1.412 1.412 1.585 2.151 2.586 2.696 2.696 1.000 1.284 0.273 2.096 ms 316.2 2238

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 122.362 122.362 125.777 313.488 652.114 955.077 955.077 526.337 832.715 158.966 325.882 µs 5.793 20.22

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 0.133 0.133 0.206 0.360 2.284 2.558 2.558 2.077 2.426 0.615 0.583 ms 2.133 6.231

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) 85.113 85.113 111.183 220.312 606.784 712.330 712.330 495.601 627.217 152.445 282.505 µs 4.095 10.93

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 17.927 17.927 17.967 18.034 18.108 18.116 18.116 0.141 0.189 0.041 18.033 ppm 8.475e+07 3.722e+10
Local Clock Time Offset -494.137 -494.137 -367.155 58.435 484.970 682.125 682.125 852.125 1,176.262 265.627 51.587 µs -2.861 6.591
Local RMS Frequency Jitter 15.483 15.483 16.770 25.320 38.776 41.453 41.453 22.006 25.970 6.658 26.170 ppb 34.37 132.3
Local RMS Time Jitter 194.567 194.567 212.306 328.108 488.882 550.820 550.820 276.576 356.253 78.145 335.955 µs 46.29 193.2
Server Jitter 192.12.19.20 122.362 122.362 125.777 313.488 652.114 955.077 955.077 526.337 832.715 158.966 325.882 µs 5.793 20.22
Server Jitter 204.34.198.40 0.133 0.133 0.206 0.360 2.284 2.558 2.558 2.077 2.426 0.615 0.583 ms 2.133 6.231
Server Jitter 2610:20:6f96:96::4 (time-d-b.nist.gov) 85.113 85.113 111.183 220.312 606.784 712.330 712.330 495.601 627.217 152.445 282.505 µs 4.095 10.93
Server Offset 192.12.19.20 1.565 1.565 1.572 2.197 2.590 2.747 2.747 1.018 1.182 0.253 2.156 ms 449.7 3550
Server Offset 204.34.198.40 -13.967 -13.967 -13.497 -13.021 -12.616 -12.259 -12.259 0.881 1.708 0.303 -13.026 ms -8.501e+04 3.742e+06
Server Offset 2610:20:6f96:96::4 (time-d-b.nist.gov) 1.412 1.412 1.585 2.151 2.586 2.696 2.696 1.000 1.284 0.273 2.096 ms 316.2 2238
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!