NTPsec

a-ntpsec-14-day-stats

Report generated: Sat Dec 7 13:12:34 2019 UTC
Start Time: Sat Nov 23 13:12:20 2019 UTC
End Time: Sat Dec 7 13:12:20 2019 UTC
Report published: Sat Dec 07 05:13:17 2019 PST
Report Period: 14.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 -1,248.000 -733.000 -550.000 41.000 519.000 685.000 1,139.000 1,069.000 1,418.000 329.923 15.801 ns -3.915 9.525
Local Clock Frequency Offset -829.330 -823.624 -801.498 -722.031 -541.962 -504.654 -499.985 259.536 318.970 75.269 -700.850 ppb -1127 1.192e+04

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 49.000 82.000 95.000 136.000 196.000 226.000 378.000 101.000 144.000 31.063 139.427 ns 53.64 235.2

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 15.000 23.000 28.000 72.000 191.000 250.000 393.000 163.000 227.000 52.270 85.235 10e-12 3.426 10.56

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 -1,248.000 -733.000 -550.000 41.000 519.000 685.000 1,139.000 1,069.000 1,418.000 329.923 15.801 ns -3.915 9.525

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 -829.330 -823.624 -801.498 -722.031 -541.962 -504.654 -499.985 259.536 318.970 75.269 -700.850 ppb -1127 1.192e+04
Temp ZONE0 59.072 60.148 60.686 62.300 63.376 63.376 64.452 2.690 3.228 0.855 62.357 °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 9.000 11.000 12.000 12.000 4.000 5.000 1.282 9.391 nSat 272 1842
TDOP 0.500 0.550 0.600 0.810 1.380 1.710 2.260 0.780 1.160 0.260 0.882 22.07 82.3

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

peer offset 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.11 -896.366 -47.593 -16.834 48.125 121.039 161.636 530.728 137.873 209.229 42.818 49.690 µs 0.08325 28.26

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 -145.707 -62.748 -41.812 7.234 64.112 88.411 184.642 105.924 151.159 32.536 8.390 µs -2.439 6.318

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.344 2.026 2.197 2.528 2.993 3.281 4.960 0.796 1.255 0.266 2.554 ms 661.8 5935

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) 2.959 3.571 3.859 4.300 4.815 5.246 9.087 0.956 1.675 0.329 4.321 ms 1829 2.274e+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 -0.058 1.720 2.165 2.503 2.956 3.399 4.101 0.791 1.679 0.298 2.520 ms 437.1 3426

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.668 2.822 3.184 3.874 4.920 9.155 11.864 1.736 6.333 0.937 4.013 ms 49.47 263.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 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) -114.158 -54.678 0.213 2.440 20.152 63.724 107.343 19.939 118.401 14.561 3.166 ms -2.328 22.99

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) -57.637 -48.860 -4.716 6.658 13.669 16.381 19.183 18.386 65.241 9.786 5.301 ms -5.59 31.03

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) -78.279 -63.566 -60.228 -52.437 -45.191 -43.401 -39.565 15.036 20.165 4.584 -52.410 ms -1959 2.484e+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) -1,249.000 -734.000 -550.000 42.000 520.000 686.000 1,140.000 1,070.000 1,420.000 330.711 15.889 ns -3.914 9.516

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

peer jitter 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.11 0.009 0.039 0.060 0.497 8.727 21.820 360.935 8.667 21.781 6.900 2.177 ms 15.51 667.2

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.007 0.025 0.039 0.108 8.634 9.163 17.344 8.595 9.138 2.621 1.171 ms 0.538 3.835

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.113 0.193 0.323 1.632 9.818 17.554 232.677 9.495 17.361 11.117 3.702 ms 11.55 191.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 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.159 0.283 0.413 1.811 10.433 34.080 194.541 10.020 33.797 13.636 4.497 ms 7.906 93.58

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.077 0.194 0.323 1.883 9.559 14.923 23.322 9.236 14.729 3.472 3.252 ms 1.678 6.544

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.118 0.236 0.403 1.924 10.519 18.820 189.701 10.117 18.584 10.827 4.161 ms 10.41 154.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 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.140 0.227 0.369 2.089 24.287 48.535 190.855 23.919 48.309 14.560 6.395 ms 6.062 67.47

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.116 0.279 0.434 2.340 17.207 47.935 189.895 16.773 47.657 10.326 5.353 ms 6.856 98.18

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.048 0.300 0.442 1.186 3.408 6.180 17.417 2.966 5.879 1.142 1.531 ms 3.554 18.3

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) 11.000 54.000 72.000 139.000 289.000 382.000 729.000 217.000 328.000 69.650 154.743 ns 6.864 23.76

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 -829.330 -823.624 -801.498 -722.031 -541.962 -504.654 -499.985 259.536 318.970 75.269 -700.850 ppb -1127 1.192e+04
Local Clock Time Offset -1,248.000 -733.000 -550.000 41.000 519.000 685.000 1,139.000 1,069.000 1,418.000 329.923 15.801 ns -3.915 9.525
Local RMS Frequency Jitter 15.000 23.000 28.000 72.000 191.000 250.000 393.000 163.000 227.000 52.270 85.235 10e-12 3.426 10.56
Local RMS Time Jitter 49.000 82.000 95.000 136.000 196.000 226.000 378.000 101.000 144.000 31.063 139.427 ns 53.64 235.2
Server Jitter 192.168.1.11 0.009 0.039 0.060 0.497 8.727 21.820 360.935 8.667 21.781 6.900 2.177 ms 15.51 667.2
Server Jitter 192.168.1.12 0.007 0.025 0.039 0.108 8.634 9.163 17.344 8.595 9.138 2.621 1.171 ms 0.538 3.835
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.113 0.193 0.323 1.632 9.818 17.554 232.677 9.495 17.361 11.117 3.702 ms 11.55 191.8
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.159 0.283 0.413 1.811 10.433 34.080 194.541 10.020 33.797 13.636 4.497 ms 7.906 93.58
Server Jitter 216.218.254.202 0.077 0.194 0.323 1.883 9.559 14.923 23.322 9.236 14.729 3.472 3.252 ms 1.678 6.544
Server Jitter 2405:fc00:0:1::123 0.118 0.236 0.403 1.924 10.519 18.820 189.701 10.117 18.584 10.827 4.161 ms 10.41 154.4
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.140 0.227 0.369 2.089 24.287 48.535 190.855 23.919 48.309 14.560 6.395 ms 6.062 67.47
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.116 0.279 0.434 2.340 17.207 47.935 189.895 16.773 47.657 10.326 5.353 ms 6.856 98.18
Server Jitter SHM(0) 0.048 0.300 0.442 1.186 3.408 6.180 17.417 2.966 5.879 1.142 1.531 ms 3.554 18.3
Server Jitter SHM(1) 11.000 54.000 72.000 139.000 289.000 382.000 729.000 217.000 328.000 69.650 154.743 ns 6.864 23.76
Server Offset 192.168.1.11 -896.366 -47.593 -16.834 48.125 121.039 161.636 530.728 137.873 209.229 42.818 49.690 µs 0.08325 28.26
Server Offset 192.168.1.12 -145.707 -62.748 -41.812 7.234 64.112 88.411 184.642 105.924 151.159 32.536 8.390 µs -2.439 6.318
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 0.344 2.026 2.197 2.528 2.993 3.281 4.960 0.796 1.255 0.266 2.554 ms 661.8 5935
Server Offset 2001:470:e815::24 (pi4.rellim.com) 2.959 3.571 3.859 4.300 4.815 5.246 9.087 0.956 1.675 0.329 4.321 ms 1829 2.274e+04
Server Offset 216.218.254.202 -0.058 1.720 2.165 2.503 2.956 3.399 4.101 0.791 1.679 0.298 2.520 ms 437.1 3426
Server Offset 2405:fc00:0:1::123 1.668 2.822 3.184 3.874 4.920 9.155 11.864 1.736 6.333 0.937 4.013 ms 49.47 263.2
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -114.158 -54.678 0.213 2.440 20.152 63.724 107.343 19.939 118.401 14.561 3.166 ms -2.328 22.99
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -57.637 -48.860 -4.716 6.658 13.669 16.381 19.183 18.386 65.241 9.786 5.301 ms -5.59 31.03
Server Offset SHM(0) -78.279 -63.566 -60.228 -52.437 -45.191 -43.401 -39.565 15.036 20.165 4.584 -52.410 ms -1959 2.484e+04
Server Offset SHM(1) -1,249.000 -734.000 -550.000 42.000 520.000 686.000 1,140.000 1,070.000 1,420.000 330.711 15.889 ns -3.914 9.516
TDOP 0.500 0.550 0.600 0.810 1.380 1.710 2.260 0.780 1.160 0.260 0.882 22.07 82.3
Temp ZONE0 59.072 60.148 60.686 62.300 63.376 63.376 64.452 2.690 3.228 0.855 62.357 °C
nSats 6.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.282 9.391 nSat 272 1842
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!