NTPsec

A-ntpsec-72-hour-stats

Report generated: Sat Dec 2 14:12:45 2023 UTC
Start Time: Wed Nov 29 14:12:43 2023 UTC
End Time: Sat Dec 2 14:12:43 2023 UTC
Report published: Sat Dec 02 06:12:59 AM 2023 PST
Report Period: 3.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 -6.660 -1.187 -0.860 -0.004 0.913 1.293 3.393 1.773 2.480 0.543 0.008 µs -3.875 10.64
Local Clock Frequency Offset -611.526 -606.827 -572.037 -392.426 -306.747 -297.195 -294.632 265.290 309.632 85.006 -414.327 ppb -220.9 1413

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 0.286 0.402 0.472 0.678 0.958 1.091 3.920 0.486 0.689 0.157 0.692 µs 51.87 262.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 103.000 156.000 181.000 255.000 347.000 393.000 1,561.000 166.000 237.000 57.988 259.014 10e-12 56.32 350.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%98%StdDev  MeanUnits nessosis
Local Clock Offset -6.660 -1.187 -0.860 -0.004 0.913 1.293 3.393 1.773 2.480 0.543 0.008 µs -3.875 10.64

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 -611.526 -606.827 -572.037 -392.426 -306.747 -297.195 -294.632 265.290 309.632 85.006 -414.327 ppb -220.9 1413
Temp ZONE0 44.008 44.008 45.084 46.160 47.236 47.774 48.312 2.152 3.766 0.888 46.286 °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 8.000 10.000 12.000 12.000 12.000 4.000 5.000 1.117 9.636 nSat 467.3 3749
TDOP 0.500 0.530 0.570 0.820 1.210 1.420 1.700 0.640 0.890 0.203 0.860 44.12 183

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 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 1.832 3.217 3.711 4.276 4.768 5.187 6.645 1.057 1.970 0.364 4.265 ms 1263 1.389e+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 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 -0.193 0.989 1.293 1.775 2.224 2.459 2.711 0.931 1.470 0.292 1.764 ms 142.5 792

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 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -15.872 -11.260 -2.592 0.468 2.649 3.649 4.523 5.242 14.909 2.332 0.143 ms -6.723 34.74

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.133 1.575 1.992 2.423 2.842 3.160 3.552 0.850 1.586 0.291 2.420 ms 410.6 3147

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 52.10.183.132

peer offset 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 52.10.183.132 2.731 3.085 3.590 5.288 6.131 6.569 7.150 2.541 3.485 0.744 5.156 ms 225.2 1429

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 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 1.096 1.532 1.904 2.446 2.879 3.100 3.744 0.975 1.567 0.300 2.429 ms 377.5 2826

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) -103.056 -101.551 -99.789 -96.847 -94.957 -94.102 -92.423 4.832 7.450 1.478 -97.052 ms -2.966e+05 1.979e+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 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) -6.661 -1.188 -0.861 -0.005 0.914 1.294 3.394 1.775 2.482 0.543 0.008 µs -3.875 10.63

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 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.200 0.333 0.585 1.414 5.491 11.113 22.203 4.906 10.780 1.910 1.950 ms 4.543 36.08

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 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 169.229.128.134 0.170 0.335 0.557 1.341 4.455 13.648 25.176 3.898 13.313 2.287 1.860 ms 5.413 44.86

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 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.757 1.054 1.434 2.978 13.063 23.413 29.295 11.628 22.360 4.031 4.389 ms 3.179 13.99

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.269 0.349 0.544 1.376 4.974 9.816 16.411 4.430 9.467 1.806 1.844 ms 4.196 25.67

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 52.10.183.132

peer jitter 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 52.10.183.132 0.186 0.400 0.576 1.404 5.653 12.861 17.057 5.078 12.461 2.186 2.010 ms 3.671 19.38

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 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 0.178 0.368 0.557 1.404 5.420 10.182 15.387 4.863 9.814 1.785 1.873 ms 3.924 21.72

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.031 0.069 0.099 0.307 0.992 1.416 2.845 0.893 1.347 0.298 0.399 ms 2.672 9.335

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) 0.120 0.264 0.352 0.659 1.242 1.552 8.232 0.890 1.288 0.286 0.711 µs 9.844 57.49

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 -611.526 -606.827 -572.037 -392.426 -306.747 -297.195 -294.632 265.290 309.632 85.006 -414.327 ppb -220.9 1413
Local Clock Time Offset -6.660 -1.187 -0.860 -0.004 0.913 1.293 3.393 1.773 2.480 0.543 0.008 µs -3.875 10.64
Local RMS Frequency Jitter 103.000 156.000 181.000 255.000 347.000 393.000 1,561.000 166.000 237.000 57.988 259.014 10e-12 56.32 350.9
Local RMS Time Jitter 0.286 0.402 0.472 0.678 0.958 1.091 3.920 0.486 0.689 0.157 0.692 µs 51.87 262.2
Server Jitter 162.159.200.1 0.200 0.333 0.585 1.414 5.491 11.113 22.203 4.906 10.780 1.910 1.950 ms 4.543 36.08
Server Jitter 169.229.128.134 0.170 0.335 0.557 1.341 4.455 13.648 25.176 3.898 13.313 2.287 1.860 ms 5.413 44.86
Server Jitter 173.11.101.155 0.757 1.054 1.434 2.978 13.063 23.413 29.295 11.628 22.360 4.031 4.389 ms 3.179 13.99
Server Jitter 216.218.254.202 0.269 0.349 0.544 1.376 4.974 9.816 16.411 4.430 9.467 1.806 1.844 ms 4.196 25.67
Server Jitter 52.10.183.132 0.186 0.400 0.576 1.404 5.653 12.861 17.057 5.078 12.461 2.186 2.010 ms 3.671 19.38
Server Jitter 66.220.9.122 0.178 0.368 0.557 1.404 5.420 10.182 15.387 4.863 9.814 1.785 1.873 ms 3.924 21.72
Server Jitter SHM(0) 0.031 0.069 0.099 0.307 0.992 1.416 2.845 0.893 1.347 0.298 0.399 ms 2.672 9.335
Server Jitter SHM(1) 0.120 0.264 0.352 0.659 1.242 1.552 8.232 0.890 1.288 0.286 0.711 µs 9.844 57.49
Server Offset 162.159.200.1 1.832 3.217 3.711 4.276 4.768 5.187 6.645 1.057 1.970 0.364 4.265 ms 1263 1.389e+04
Server Offset 169.229.128.134 -0.193 0.989 1.293 1.775 2.224 2.459 2.711 0.931 1.470 0.292 1.764 ms 142.5 792
Server Offset 173.11.101.155 -15.872 -11.260 -2.592 0.468 2.649 3.649 4.523 5.242 14.909 2.332 0.143 ms -6.723 34.74
Server Offset 216.218.254.202 0.133 1.575 1.992 2.423 2.842 3.160 3.552 0.850 1.586 0.291 2.420 ms 410.6 3147
Server Offset 52.10.183.132 2.731 3.085 3.590 5.288 6.131 6.569 7.150 2.541 3.485 0.744 5.156 ms 225.2 1429
Server Offset 66.220.9.122 1.096 1.532 1.904 2.446 2.879 3.100 3.744 0.975 1.567 0.300 2.429 ms 377.5 2826
Server Offset SHM(0) -103.056 -101.551 -99.789 -96.847 -94.957 -94.102 -92.423 4.832 7.450 1.478 -97.052 ms -2.966e+05 1.979e+07
Server Offset SHM(1) -6.661 -1.188 -0.861 -0.005 0.914 1.294 3.394 1.775 2.482 0.543 0.008 µs -3.875 10.63
TDOP 0.500 0.530 0.570 0.820 1.210 1.420 1.700 0.640 0.890 0.203 0.860 44.12 183
Temp ZONE0 44.008 44.008 45.084 46.160 47.236 47.774 48.312 2.152 3.766 0.888 46.286 °C
nSats 6.000 7.000 8.000 10.000 12.000 12.000 12.000 4.000 5.000 1.117 9.636 nSat 467.3 3749
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!