NTPsec

b-ntpsec-7-day-stats

Report generated: Sun Jan 26 14:04:34 2020 UTC
Start Time: Sun Jan 19 14:04:21 2020 UTC
End Time: Sun Jan 26 14:04:21 2020 UTC
Report published: Sun Jan 26 06:05:09 2020 PST
Report Period: 7.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 -5.396 -1.027 -0.788 0.016 0.677 0.902 1.451 1.465 1.929 0.450 -0.013 µs -4.455 12.14
Local Clock Frequency Offset -5.884 -5.879 -5.852 -5.770 -5.603 -5.589 -5.585 0.249 0.290 0.078 -5.750 ppm -4.117e+05 3.064e+07

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 95.000 152.000 182.000 273.000 393.000 457.000 2,394.000 211.000 305.000 72.161 278.933 ns 36.49 259.6

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 27.000 38.000 45.000 89.000 190.000 229.000 4,900.000 145.000 191.000 91.983 103.632 10e-12 27.25 1092

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 -5.396 -1.027 -0.788 0.016 0.677 0.902 1.451 1.465 1.929 0.450 -0.013 µs -4.455 12.14

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.884 -5.879 -5.852 -5.770 -5.603 -5.589 -5.585 0.249 0.290 0.078 -5.750 ppm -4.117e+05 3.064e+07
Temp ZONE0 59.072 60.148 60.148 62.300 62.838 63.376 63.914 2.690 3.228 0.840 61.846 °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 12.000 12.000 12.000 5.000 5.000 1.345 9.400 nSat 232.7 1503
TDOP 0.510 0.580 0.610 0.870 1.480 1.710 2.310 0.870 1.130 0.272 0.921 22.08 83.19

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 -168.308 24.379 47.422 90.672 119.719 133.405 308.113 72.297 109.026 23.947 87.640 µs 26.13 93.12

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) -4.138 2.137 2.271 2.591 3.012 3.397 4.651 0.741 1.261 0.314 2.607 ms 401.8 3097

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.118 3.691 3.886 4.306 4.774 5.058 7.230 0.888 1.367 0.281 4.323 ms 3010 4.391e+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.891 2.095 2.258 2.548 2.912 3.116 3.295 0.654 1.021 0.212 2.564 ms 1406 1.6e+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 6.555 8.855 9.147 9.579 10.467 10.876 18.304 1.320 2.022 0.551 9.654 ms 4561 7.657e+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 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) -11.330 -10.501 -9.050 -1.453 3.471 3.906 4.740 12.521 14.407 3.542 -1.182 ms -7.108 20.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 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.055 2.055 2.215 2.515 2.925 3.265 6.106 0.711 1.210 0.255 2.536 ms 746.7 6996

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) -56.873 -54.040 -8.260 3.511 8.191 11.616 15.429 16.451 65.656 10.043 1.411 ms -7.552 42.58

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 -5.488 -3.493 -2.172 -0.693 0.960 2.662 22.104 3.132 6.155 1.157 -0.648 ms -4.267 73.35

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) -502.464 -419.411 -401.584 -359.490 -315.873 -299.312 -250.111 85.711 120.099 26.389 -359.399 ms -3169 4.697e+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) -5.397 -1.028 -0.789 0.017 0.678 0.903 1.452 1.467 1.931 0.451 -0.013 µs -4.453 12.12

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.022 0.040 0.174 8.655 10.246 243.103 8.615 10.224 4.839 1.748 ms 22.26 922.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.166 0.270 1.567 9.899 33.958 121.454 9.629 33.792 8.029 3.750 ms 7.339 89.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.



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.284 0.412 1.865 11.022 65.279 217.816 10.610 64.996 14.834 4.978 ms 7.016 78.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.



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.000 0.218 0.359 1.761 9.136 12.566 34.351 8.777 12.349 3.094 2.980 ms 2.47 16.69

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.263 0.396 2.742 10.896 20.741 224.102 10.501 20.478 10.858 4.852 ms 10.69 170.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 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.253 0.406 2.032 9.505 15.081 110.847 9.098 14.828 5.732 3.703 ms 10.16 177

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.192 0.304 1.712 9.891 15.950 164.082 9.587 15.758 9.240 3.761 ms 11.28 178

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.235 0.363 2.105 16.783 46.682 223.540 16.420 46.447 13.271 5.541 ms 7.656 106.9

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.128 1.664 9.876 39.878 67.113 234.251 38.213 65.985 16.403 15.108 ms 3.593 32.45

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.433 5.960 11.305 22.538 29.567 82.853 16.578 25.134 5.296 12.412 ms 7.86 28.16

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 100.000 135.000 254.000 490.000 628.000 4,524.000 355.000 528.000 123.011 276.144 ns 12.14 222.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -5.884 -5.879 -5.852 -5.770 -5.603 -5.589 -5.585 0.249 0.290 0.078 -5.750 ppm -4.117e+05 3.064e+07
Local Clock Time Offset -5.396 -1.027 -0.788 0.016 0.677 0.902 1.451 1.465 1.929 0.450 -0.013 µs -4.455 12.14
Local RMS Frequency Jitter 27.000 38.000 45.000 89.000 190.000 229.000 4,900.000 145.000 191.000 91.983 103.632 10e-12 27.25 1092
Local RMS Time Jitter 95.000 152.000 182.000 273.000 393.000 457.000 2,394.000 211.000 305.000 72.161 278.933 ns 36.49 259.6
Server Jitter 192.168.1.10 0.000 0.022 0.040 0.174 8.655 10.246 243.103 8.615 10.224 4.839 1.748 ms 22.26 922.5
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.000 0.166 0.270 1.567 9.899 33.958 121.454 9.629 33.792 8.029 3.750 ms 7.339 89.87
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.284 0.412 1.865 11.022 65.279 217.816 10.610 64.996 14.834 4.978 ms 7.016 78.63
Server Jitter 216.218.254.202 0.000 0.218 0.359 1.761 9.136 12.566 34.351 8.777 12.349 3.094 2.980 ms 2.47 16.69
Server Jitter 2405:fc00:0:1::123 0.000 0.263 0.396 2.742 10.896 20.741 224.102 10.501 20.478 10.858 4.852 ms 10.69 170.5
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.253 0.406 2.032 9.505 15.081 110.847 9.098 14.828 5.732 3.703 ms 10.16 177
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.000 0.192 0.304 1.712 9.891 15.950 164.082 9.587 15.758 9.240 3.761 ms 11.28 178
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.000 0.235 0.363 2.105 16.783 46.682 223.540 16.420 46.447 13.271 5.541 ms 7.656 106.9
Server Jitter 76.14.161.109 0.000 1.128 1.664 9.876 39.878 67.113 234.251 38.213 65.985 16.403 15.108 ms 3.593 32.45
Server Jitter SHM(0) 0.000 4.433 5.960 11.305 22.538 29.567 82.853 16.578 25.134 5.296 12.412 ms 7.86 28.16
Server Jitter SHM(1) 0.000 100.000 135.000 254.000 490.000 628.000 4,524.000 355.000 528.000 123.011 276.144 ns 12.14 222.2
Server Offset 192.168.1.10 -168.308 24.379 47.422 90.672 119.719 133.405 308.113 72.297 109.026 23.947 87.640 µs 26.13 93.12
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) -4.138 2.137 2.271 2.591 3.012 3.397 4.651 0.741 1.261 0.314 2.607 ms 401.8 3097
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.118 3.691 3.886 4.306 4.774 5.058 7.230 0.888 1.367 0.281 4.323 ms 3010 4.391e+04
Server Offset 216.218.254.202 0.891 2.095 2.258 2.548 2.912 3.116 3.295 0.654 1.021 0.212 2.564 ms 1406 1.6e+04
Server Offset 2405:fc00:0:1::123 6.555 8.855 9.147 9.579 10.467 10.876 18.304 1.320 2.022 0.551 9.654 ms 4561 7.657e+04
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -11.330 -10.501 -9.050 -1.453 3.471 3.906 4.740 12.521 14.407 3.542 -1.182 ms -7.108 20.99
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) -0.055 2.055 2.215 2.515 2.925 3.265 6.106 0.711 1.210 0.255 2.536 ms 746.7 6996
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -56.873 -54.040 -8.260 3.511 8.191 11.616 15.429 16.451 65.656 10.043 1.411 ms -7.552 42.58
Server Offset 76.14.161.109 -5.488 -3.493 -2.172 -0.693 0.960 2.662 22.104 3.132 6.155 1.157 -0.648 ms -4.267 73.35
Server Offset SHM(0) -502.464 -419.411 -401.584 -359.490 -315.873 -299.312 -250.111 85.711 120.099 26.389 -359.399 ms -3169 4.697e+04
Server Offset SHM(1) -5.397 -1.028 -0.789 0.017 0.678 0.903 1.452 1.467 1.931 0.451 -0.013 µs -4.453 12.12
TDOP 0.510 0.580 0.610 0.870 1.480 1.710 2.310 0.870 1.130 0.272 0.921 22.08 83.19
Temp ZONE0 59.072 60.148 60.148 62.300 62.838 63.376 63.914 2.690 3.228 0.840 61.846 °C
nSats 5.000 7.000 7.000 9.000 12.000 12.000 12.000 5.000 5.000 1.345 9.400 nSat 232.7 1503
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!