NTPsec

B-ntpsec-3-hour-stats

Report generated: Sun Jan 26 15:01:24 2020 UTC
Start Time: Sun Jan 26 12:01:24 2020 UTC
End Time: Sun Jan 26 15:01:24 2020 UTC
Report published: Sun Jan 26 07:01:29 2020 PST
Report Period: 0.1 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 -525.000 -325.000 -184.000 221.000 625.000 825.000 993.000 809.000 1,150.000 250.569 229.218 ns -0.2061 2.738
Local Clock Frequency Offset -5.752 -5.752 -5.751 -5.729 -5.715 -5.714 -5.714 0.037 0.038 0.0124 -5.731 ppm -1.003e+08 4.662e+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 167.000 178.000 213.000 283.000 372.000 416.000 445.000 159.000 238.000 47.935 287.823 ns 140.7 786.9

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 35.000 38.000 45.000 79.000 121.000 145.000 155.000 76.000 107.000 23.843 79.804 10e-12 20.36 69.71

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 -525.000 -325.000 -184.000 221.000 625.000 825.000 993.000 809.000 1,150.000 250.569 229.218 ns -0.2061 2.738

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 -5.752 -5.752 -5.751 -5.729 -5.715 -5.714 -5.714 0.037 0.038 0.0124 -5.731 ppm -1.003e+08 4.662e+10
Temp ZONE0 61.224 61.224 61.224 61.762 62.300 62.300 62.300 1.076 1.076 0.394 61.828 °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 8.000 10.000 10.000 10.000 3.000 3.000 1.052 8.179 nSat 330.8 2381
TDOP 0.620 0.620 0.630 0.940 1.970 1.990 2.090 1.340 1.370 0.502 1.209 7.454 19.84

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. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



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

peer offset 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.10 26.818 47.072 58.873 96.081 122.437 133.250 138.081 63.564 86.178 18.323 95.361 µs 86.29 411.5

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) 2.115 2.115 2.144 2.520 2.835 2.846 2.846 0.691 0.731 0.196 2.527 ms 1715 2.081e+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 2001:470:e815::24 (pi4.rellim.com)

peer offset 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.866 3.866 3.875 4.325 4.692 4.695 4.695 0.817 0.830 0.224 4.291 ms 6018 1.101e+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 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.275 2.275 2.275 2.621 3.228 3.228 3.228 0.954 0.954 0.218 2.603 ms 1352 1.524e+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 2405:fc00:0:1::123

peer offset 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00:0:1::123 8.911 8.911 9.147 9.456 9.794 9.868 9.868 0.647 0.958 0.185 9.459 ms 1.256e+05 6.295e+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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.170 0.170 1.056 1.655 2.725 2.946 2.946 1.669 2.776 0.552 1.777 ms 17.63 57.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 Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu)

peer offset 2607:f140:ffff:8000:0:8006:0:a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.000 0.000 2.210 2.461 2.680 2.964 2.964 0.470 2.964 0.435 2.416 ms 103.4 495.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 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com)

peer offset 2a03:b0c0:1:d0::1f9:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -2.531 -2.531 -1.259 3.534 4.260 4.573 4.573 5.519 7.104 1.379 3.189 ms 3.313 9.321

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 76.14.161.109

peer offset 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 76.14.161.109 -1.791 -1.791 -1.755 -0.808 1.052 1.816 1.816 2.807 3.607 0.846 -0.685 ms -10.51 27.69

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) -394.882 -377.304 -368.792 -338.694 -306.054 -298.049 -271.397 62.738 79.256 19.056 -338.133 ms -6641 1.255e+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) -525.000 -325.000 -185.000 222.000 626.000 826.000 994.000 811.000 1,151.000 251.038 229.832 ns -0.2091 2.739

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

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 0.017 0.019 0.033 0.135 8.647 8.786 8.788 8.615 8.767 2.424 1.124 ms 0.7496 4.296

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.321 0.321 0.331 0.941 5.428 5.507 5.507 5.097 5.186 1.460 1.562 ms 1.892 5.548

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:e815::24 (pi4.rellim.com)

peer jitter 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.234 0.234 0.272 1.369 22.647 22.660 22.660 22.375 22.426 6.117 4.491 ms 1.045 4.19

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.249 0.249 0.249 2.724 7.488 7.488 7.488 7.240 7.240 2.627 3.489 ms 1.4 2.715

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 2405:fc00:0:1::123

peer jitter 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2405:fc00:0:1::123 0.357 0.357 0.370 3.125 12.626 14.576 14.576 12.256 14.218 4.006 4.348 ms 1.482 3.78

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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer jitter 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.272 0.272 0.342 1.066 9.295 12.176 12.176 8.953 11.903 2.923 2.336 ms 1.248 4.229

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 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu)

peer jitter 2607:f140:ffff:8000:0:8006:0:a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.312 0.312 0.421 2.239 9.293 9.299 9.299 8.872 8.987 2.676 2.891 ms 1.683 4.419

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 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com)

peer jitter 2a03:b0c0:1:d0::1f9:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.281 0.281 0.383 1.447 9.525 39.220 39.220 9.142 38.940 6.691 4.288 ms 2.631 15.05

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 76.14.161.109

peer jitter 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 76.14.161.109 1.417 1.417 1.637 9.801 33.808 34.145 34.145 32.171 32.728 8.889 11.251 ms 1.917 5.349

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) 1.327 3.594 4.909 9.346 19.000 25.895 50.583 14.091 22.301 4.601 10.361 ms 7.287 27.14

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) 99.000 119.000 153.000 266.000 490.000 599.000 694.000 337.000 480.000 102.737 283.918 ns 11.8 39.62

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 -5.752 -5.752 -5.751 -5.729 -5.715 -5.714 -5.714 0.037 0.038 0.0124 -5.731 ppm -1.003e+08 4.662e+10
Local Clock Time Offset -525.000 -325.000 -184.000 221.000 625.000 825.000 993.000 809.000 1,150.000 250.569 229.218 ns -0.2061 2.738
Local RMS Frequency Jitter 35.000 38.000 45.000 79.000 121.000 145.000 155.000 76.000 107.000 23.843 79.804 10e-12 20.36 69.71
Local RMS Time Jitter 167.000 178.000 213.000 283.000 372.000 416.000 445.000 159.000 238.000 47.935 287.823 ns 140.7 786.9
Server Jitter 192.168.1.10 0.017 0.019 0.033 0.135 8.647 8.786 8.788 8.615 8.767 2.424 1.124 ms 0.7496 4.296
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.321 0.321 0.331 0.941 5.428 5.507 5.507 5.097 5.186 1.460 1.562 ms 1.892 5.548
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.234 0.234 0.272 1.369 22.647 22.660 22.660 22.375 22.426 6.117 4.491 ms 1.045 4.19
Server Jitter 216.218.254.202 0.249 0.249 0.249 2.724 7.488 7.488 7.488 7.240 7.240 2.627 3.489 ms 1.4 2.715
Server Jitter 2405:fc00:0:1::123 0.357 0.357 0.370 3.125 12.626 14.576 14.576 12.256 14.218 4.006 4.348 ms 1.482 3.78
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.272 0.272 0.342 1.066 9.295 12.176 12.176 8.953 11.903 2.923 2.336 ms 1.248 4.229
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.312 0.312 0.421 2.239 9.293 9.299 9.299 8.872 8.987 2.676 2.891 ms 1.683 4.419
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.281 0.281 0.383 1.447 9.525 39.220 39.220 9.142 38.940 6.691 4.288 ms 2.631 15.05
Server Jitter 76.14.161.109 1.417 1.417 1.637 9.801 33.808 34.145 34.145 32.171 32.728 8.889 11.251 ms 1.917 5.349
Server Jitter SHM(0) 1.327 3.594 4.909 9.346 19.000 25.895 50.583 14.091 22.301 4.601 10.361 ms 7.287 27.14
Server Jitter SHM(1) 99.000 119.000 153.000 266.000 490.000 599.000 694.000 337.000 480.000 102.737 283.918 ns 11.8 39.62
Server Offset 192.168.1.10 26.818 47.072 58.873 96.081 122.437 133.250 138.081 63.564 86.178 18.323 95.361 µs 86.29 411.5
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 2.115 2.115 2.144 2.520 2.835 2.846 2.846 0.691 0.731 0.196 2.527 ms 1715 2.081e+04
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.866 3.866 3.875 4.325 4.692 4.695 4.695 0.817 0.830 0.224 4.291 ms 6018 1.101e+05
Server Offset 216.218.254.202 2.275 2.275 2.275 2.621 3.228 3.228 3.228 0.954 0.954 0.218 2.603 ms 1352 1.524e+04
Server Offset 2405:fc00:0:1::123 8.911 8.911 9.147 9.456 9.794 9.868 9.868 0.647 0.958 0.185 9.459 ms 1.256e+05 6.295e+06
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.170 0.170 1.056 1.655 2.725 2.946 2.946 1.669 2.776 0.552 1.777 ms 17.63 57.63
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.000 0.000 2.210 2.461 2.680 2.964 2.964 0.470 2.964 0.435 2.416 ms 103.4 495.4
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -2.531 -2.531 -1.259 3.534 4.260 4.573 4.573 5.519 7.104 1.379 3.189 ms 3.313 9.321
Server Offset 76.14.161.109 -1.791 -1.791 -1.755 -0.808 1.052 1.816 1.816 2.807 3.607 0.846 -0.685 ms -10.51 27.69
Server Offset SHM(0) -394.882 -377.304 -368.792 -338.694 -306.054 -298.049 -271.397 62.738 79.256 19.056 -338.133 ms -6641 1.255e+05
Server Offset SHM(1) -525.000 -325.000 -185.000 222.000 626.000 826.000 994.000 811.000 1,151.000 251.038 229.832 ns -0.2091 2.739
TDOP 0.620 0.620 0.630 0.940 1.970 1.990 2.090 1.340 1.370 0.502 1.209 7.454 19.84
Temp ZONE0 61.224 61.224 61.224 61.762 62.300 62.300 62.300 1.076 1.076 0.394 61.828 °C
nSats 6.000 7.000 7.000 8.000 10.000 10.000 10.000 3.000 3.000 1.052 8.179 nSat 330.8 2381
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!