NTPsec

b-ntpsec-5-day-stats

Report generated: Wed Nov 20 16:15:50 2019 UTC
Start Time: Fri Nov 15 16:15:22 2019 UTC
End Time: Wed Nov 20 16:15:22 2019 UTC
Report published: Wed Nov 20 08:17:14 2019 PST
Report Period: 5.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 -2,859.000 -562.000 -394.000 2.000 390.000 550.000 925.000 784.000 1,112.000 240.512 1.546 ns -4.098 11.23
Local Clock Frequency Offset -5.679 -5.678 -5.673 -5.650 -5.614 -5.594 -5.591 0.058 0.085 0.0187 -5.647 ppm -2.783e+07 8.433e+09

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 105.000 150.000 173.000 248.000 349.000 397.000 1,428.000 176.000 247.000 57.319 253.282 ns 52.46 269.4

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 24.000 33.000 38.000 55.000 85.000 108.000 2,059.000 47.000 75.000 43.639 58.764 10e-12 27.02 893.6

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 -2,859.000 -562.000 -394.000 2.000 390.000 550.000 925.000 784.000 1,112.000 240.512 1.546 ns -4.098 11.23

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.679 -5.678 -5.673 -5.650 -5.614 -5.594 -5.591 0.058 0.085 0.0187 -5.647 ppm -2.783e+07 8.433e+09
Temp ZONE0 57.996 59.072 59.072 59.610 60.148 60.686 60.686 1.076 1.614 0.460 59.741 °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 5.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.245 9.268 nSat 286.9 1973
TDOP 0.500 0.570 0.600 0.840 1.410 1.730 4.350 0.810 1.160 0.268 0.899 21.5 84.87

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 -1,952.733 -74.589 -41.004 32.162 66.301 123.523 1,440.984 107.305 198.112 60.228 24.562 µs -4.536 302.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 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) 0.677 1.436 1.919 2.462 3.288 4.074 6.192 1.369 2.638 0.462 2.520 ms 103.7 558.2

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) 0.541 3.110 3.566 4.184 5.161 6.410 8.842 1.595 3.300 0.583 4.261 ms 271.6 1884

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 -1.936 -1.316 -0.782 2.559 3.505 4.764 7.896 4.287 6.080 1.089 2.391 ms 3.599 10.47

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) -2.306 -0.104 1.094 2.303 3.488 4.399 6.866 2.394 4.503 0.780 2.290 ms 12.95 43.88

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.648 1.324 1.829 2.389 3.431 4.631 6.300 1.603 3.308 0.548 2.474 ms 56.29 271.6

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) -11.810 -6.355 -1.093 3.970 7.826 11.087 15.308 8.919 17.442 2.857 3.512 ms 0.0434 6.263

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 -8.745 -4.276 -2.388 -0.713 2.051 4.333 6.541 4.439 8.609 1.479 -0.568 ms -6.632 23.15

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) -441.957 -411.630 -401.256 -365.414 -325.760 -310.911 -269.653 75.496 100.719 23.332 -364.784 ms -4652 7.821e+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 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) -2,860.000 -563.000 -395.000 3.000 391.000 550.000 926.000 786.000 1,113.000 241.277 1.553 ns -4.097 11.21

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.000 0.029 0.082 0.940 7.817 56.734 274.798 7.735 56.705 8.458 2.810 ms 12.49 343.5

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.000 0.468 0.764 2.579 12.786 38.129 58.216 12.021 37.661 6.505 4.609 ms 3.901 27.54

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.000 0.407 0.704 2.882 14.194 56.571 227.070 13.490 56.164 11.174 5.454 ms 8.429 133.4

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.000 0.529 0.811 2.760 11.738 37.962 190.194 10.927 37.434 9.307 4.705 ms 10.55 188.6

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.000 0.506 0.737 2.824 16.312 44.882 100.855 15.575 44.375 8.149 5.243 ms 4.299 36.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 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.000 0.386 0.695 2.700 11.796 37.957 68.686 11.102 37.571 6.764 4.579 ms 4.498 34.25

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.000 0.478 0.852 3.158 14.430 56.911 190.467 13.578 56.433 11.622 5.733 ms 8.35 120.1

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 0.000 1.171 2.107 17.453 105.376 119.328 141.934 103.269 118.157 31.991 28.452 ms 1.297 3.939

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.000 4.685 6.230 11.650 22.961 29.967 68.007 16.730 25.283 5.327 12.767 ms 8.242 28.85

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.000 95.000 128.000 236.000 450.000 573.000 2,359.000 322.000 478.000 103.523 255.917 ns 9.553 49.63

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.679 -5.678 -5.673 -5.650 -5.614 -5.594 -5.591 0.058 0.085 0.0187 -5.647 ppm -2.783e+07 8.433e+09
Local Clock Time Offset -2,859.000 -562.000 -394.000 2.000 390.000 550.000 925.000 784.000 1,112.000 240.512 1.546 ns -4.098 11.23
Local RMS Frequency Jitter 24.000 33.000 38.000 55.000 85.000 108.000 2,059.000 47.000 75.000 43.639 58.764 10e-12 27.02 893.6
Local RMS Time Jitter 105.000 150.000 173.000 248.000 349.000 397.000 1,428.000 176.000 247.000 57.319 253.282 ns 52.46 269.4
Server Jitter 192.168.1.10 0.000 0.029 0.082 0.940 7.817 56.734 274.798 7.735 56.705 8.458 2.810 ms 12.49 343.5
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.000 0.468 0.764 2.579 12.786 38.129 58.216 12.021 37.661 6.505 4.609 ms 3.901 27.54
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.407 0.704 2.882 14.194 56.571 227.070 13.490 56.164 11.174 5.454 ms 8.429 133.4
Server Jitter 2405:fc00:0:1::123 0.000 0.529 0.811 2.760 11.738 37.962 190.194 10.927 37.434 9.307 4.705 ms 10.55 188.6
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.506 0.737 2.824 16.312 44.882 100.855 15.575 44.375 8.149 5.243 ms 4.299 36.72
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.000 0.386 0.695 2.700 11.796 37.957 68.686 11.102 37.571 6.764 4.579 ms 4.498 34.25
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.000 0.478 0.852 3.158 14.430 56.911 190.467 13.578 56.433 11.622 5.733 ms 8.35 120.1
Server Jitter 76.14.161.109 0.000 1.171 2.107 17.453 105.376 119.328 141.934 103.269 118.157 31.991 28.452 ms 1.297 3.939
Server Jitter SHM(0) 0.000 4.685 6.230 11.650 22.961 29.967 68.007 16.730 25.283 5.327 12.767 ms 8.242 28.85
Server Jitter SHM(1) 0.000 95.000 128.000 236.000 450.000 573.000 2,359.000 322.000 478.000 103.523 255.917 ns 9.553 49.63
Server Offset 192.168.1.10 -1,952.733 -74.589 -41.004 32.162 66.301 123.523 1,440.984 107.305 198.112 60.228 24.562 µs -4.536 302.1
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 0.677 1.436 1.919 2.462 3.288 4.074 6.192 1.369 2.638 0.462 2.520 ms 103.7 558.2
Server Offset 2001:470:e815::24 (pi4.rellim.com) 0.541 3.110 3.566 4.184 5.161 6.410 8.842 1.595 3.300 0.583 4.261 ms 271.6 1884
Server Offset 2405:fc00:0:1::123 -1.936 -1.316 -0.782 2.559 3.505 4.764 7.896 4.287 6.080 1.089 2.391 ms 3.599 10.47
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -2.306 -0.104 1.094 2.303 3.488 4.399 6.866 2.394 4.503 0.780 2.290 ms 12.95 43.88
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.648 1.324 1.829 2.389 3.431 4.631 6.300 1.603 3.308 0.548 2.474 ms 56.29 271.6
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -11.810 -6.355 -1.093 3.970 7.826 11.087 15.308 8.919 17.442 2.857 3.512 ms 0.0434 6.263
Server Offset 76.14.161.109 -8.745 -4.276 -2.388 -0.713 2.051 4.333 6.541 4.439 8.609 1.479 -0.568 ms -6.632 23.15
Server Offset SHM(0) -441.957 -411.630 -401.256 -365.414 -325.760 -310.911 -269.653 75.496 100.719 23.332 -364.784 ms -4652 7.821e+04
Server Offset SHM(1) -2,860.000 -563.000 -395.000 3.000 391.000 550.000 926.000 786.000 1,113.000 241.277 1.553 ns -4.097 11.21
TDOP 0.500 0.570 0.600 0.840 1.410 1.730 4.350 0.810 1.160 0.268 0.899 21.5 84.87
Temp ZONE0 57.996 59.072 59.072 59.610 60.148 60.686 60.686 1.076 1.614 0.460 59.741 °C
nSats 5.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.245 9.268 nSat 286.9 1973
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!