NTPsec

A-ntpsec-1-hour-stats

Report generated: Mon Nov 30 05:01:04 2020 UTC
Start Time: Mon Nov 30 04:00:36 2020 UTC
End Time: Mon Nov 30 05:01:04 2020 UTC
Report published: Sun Nov 29 21:01:07 2020 PST
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 -895.000 -686.000 -560.000 -57.000 567.000 877.000 1,002.000 1,127.000 1,563.000 359.317 -34.876 ns -4.306 9.969
Local Clock Frequency Offset -224.640 -224.594 -224.503 -223.572 -221.207 -220.993 -220.978 3.296 3.601 1.294 -222.988 ppb -5.204e+06 9.019e+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 252.000 272.000 287.000 403.000 655.000 803.000 829.000 368.000 531.000 127.676 445.686 ns 23.59 84.93

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 47.000 48.000 53.000 88.000 129.000 141.000 146.000 76.000 93.000 22.704 86.788 10e-12 31.34 118.1

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 -895.000 -686.000 -560.000 -57.000 567.000 877.000 1,002.000 1,127.000 1,563.000 359.317 -34.876 ns -4.306 9.969

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 -224.640 -224.594 -224.503 -223.572 -221.207 -220.993 -220.978 3.296 3.601 1.294 -222.988 ppb -5.204e+06 9.019e+08
Temp ZONE0 57.996 57.996 57.996 58.534 59.072 59.072 59.072 1.076 1.076 0.360 58.569 °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 10.000 11.000 11.000 11.000 2.000 2.000 0.806 9.867 nSat 1457 1.678e+04
TDOP 0.610 0.610 0.620 0.820 0.880 0.890 0.890 0.260 0.280 0.103 0.773 294.3 2034

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.490 1.490 1.490 1.850 2.020 2.020 2.020 0.530 0.530 0.156 1.784 ms 1167 1.249e+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 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 10.869 10.869 78.153 137.041 176.314 182.218 182.218 98.161 171.349 35.128 131.401 µs 27.45 92.33

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.236 2.236 2.236 2.482 2.721 2.721 2.721 0.485 0.485 0.140 2.492 ms 4832 8.224e+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 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.177 2.177 2.177 2.451 2.640 2.640 2.640 0.463 0.463 0.153 2.377 ms 3117 4.596e+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 -401.407 -401.407 -401.407 116.963 917.084 917.084 917.084 1,318.491 1,318.491 380.809 146.437 µs -1.809 4.183

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) -63.613 -60.735 -56.604 -53.196 -48.037 -47.202 -45.460 8.567 13.534 2.693 -52.935 ms -8874 1.846e+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) -896.000 -687.000 -561.000 -58.000 568.000 878.000 1,003.000 1,129.000 1,565.000 360.133 -34.982 ns -4.307 9.965

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.226 0.226 0.226 1.242 9.083 9.083 9.083 8.857 8.857 3.394 2.582 ms 0.571 1.926

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.025 0.025 0.029 0.148 0.333 8.641 8.641 0.304 8.616 1.180 0.348 ms 4.128 30.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 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.586 0.586 0.586 1.106 8.927 8.927 8.927 8.341 8.341 3.510 3.103 ms 0.6621 1.652

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.676 0.676 0.676 4.648 10.131 10.131 10.131 9.455 9.455 4.099 4.952 ms 0.897 1.708

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.042 1.042 1.042 1.796 12.110 12.110 12.110 11.068 11.068 3.914 3.365 ms 1.329 3.271

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.187 0.306 0.417 1.066 3.209 6.423 9.475 2.792 6.117 1.189 1.499 ms 3.051 12.8

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.146 0.181 0.203 0.390 0.813 1.073 1.194 0.610 0.892 0.201 0.435 µs 6.262 19.87

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 -224.640 -224.594 -224.503 -223.572 -221.207 -220.993 -220.978 3.296 3.601 1.294 -222.988 ppb -5.204e+06 9.019e+08
Local Clock Time Offset -895.000 -686.000 -560.000 -57.000 567.000 877.000 1,002.000 1,127.000 1,563.000 359.317 -34.876 ns -4.306 9.969
Local RMS Frequency Jitter 47.000 48.000 53.000 88.000 129.000 141.000 146.000 76.000 93.000 22.704 86.788 10e-12 31.34 118.1
Local RMS Time Jitter 252.000 272.000 287.000 403.000 655.000 803.000 829.000 368.000 531.000 127.676 445.686 ns 23.59 84.93
Server Jitter 137.190.2.4 0.226 0.226 0.226 1.242 9.083 9.083 9.083 8.857 8.857 3.394 2.582 ms 0.571 1.926
Server Jitter 192.168.1.12 0.025 0.025 0.029 0.148 0.333 8.641 8.641 0.304 8.616 1.180 0.348 ms 4.128 30.72
Server Jitter 216.218.192.202 0.586 0.586 0.586 1.106 8.927 8.927 8.927 8.341 8.341 3.510 3.103 ms 0.6621 1.652
Server Jitter 216.218.254.202 0.676 0.676 0.676 4.648 10.131 10.131 10.131 9.455 9.455 4.099 4.952 ms 0.897 1.708
Server Jitter 73.158.5.1 1.042 1.042 1.042 1.796 12.110 12.110 12.110 11.068 11.068 3.914 3.365 ms 1.329 3.271
Server Jitter SHM(0) 0.187 0.306 0.417 1.066 3.209 6.423 9.475 2.792 6.117 1.189 1.499 ms 3.051 12.8
Server Jitter SHM(1) 0.146 0.181 0.203 0.390 0.813 1.073 1.194 0.610 0.892 0.201 0.435 µs 6.262 19.87
Server Offset 137.190.2.4 1.490 1.490 1.490 1.850 2.020 2.020 2.020 0.530 0.530 0.156 1.784 ms 1167 1.249e+04
Server Offset 192.168.1.12 10.869 10.869 78.153 137.041 176.314 182.218 182.218 98.161 171.349 35.128 131.401 µs 27.45 92.33
Server Offset 216.218.192.202 2.236 2.236 2.236 2.482 2.721 2.721 2.721 0.485 0.485 0.140 2.492 ms 4832 8.224e+04
Server Offset 216.218.254.202 2.177 2.177 2.177 2.451 2.640 2.640 2.640 0.463 0.463 0.153 2.377 ms 3117 4.596e+04
Server Offset 73.158.5.1 -401.407 -401.407 -401.407 116.963 917.084 917.084 917.084 1,318.491 1,318.491 380.809 146.437 µs -1.809 4.183
Server Offset SHM(0) -63.613 -60.735 -56.604 -53.196 -48.037 -47.202 -45.460 8.567 13.534 2.693 -52.935 ms -8874 1.846e+05
Server Offset SHM(1) -896.000 -687.000 -561.000 -58.000 568.000 878.000 1,003.000 1,129.000 1,565.000 360.133 -34.982 ns -4.307 9.965
TDOP 0.610 0.610 0.620 0.820 0.880 0.890 0.890 0.260 0.280 0.103 0.773 294.3 2034
Temp ZONE0 57.996 57.996 57.996 58.534 59.072 59.072 59.072 1.076 1.076 0.360 58.569 °C
nSats 9.000 9.000 9.000 10.000 11.000 11.000 11.000 2.000 2.000 0.806 9.867 nSat 1457 1.678e+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!