NTPsec

c-ntpsec-14-day-stats

Report generated: Sat Dec 7 13:14:16 2019 UTC
Start Time: Sat Nov 23 13:14:13 2019 UTC
End Time: Sat Dec 7 13:14:13 2019 UTC
Report published: Sat Dec 07 05:15:35 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,253.000 -575.000 -392.000 7.000 430.000 619.000 1,039.000 822.000 1,194.000 249.347 10.823 ns -3.686 9.364
Local Clock Frequency Offset -6.701 -6.692 -6.672 -6.617 -6.564 -6.546 -6.544 0.107 0.146 0.034 -6.618 ppm -7.802e+06 1.547e+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 58.000 103.000 121.000 178.000 333.000 444.000 624.000 212.000 341.000 67.021 193.577 ns 14.29 56.24

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 19.000 28.000 34.000 55.000 95.000 120.000 218.000 61.000 92.000 19.780 58.334 10e-12 14.46 52.28

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,253.000 -575.000 -392.000 7.000 430.000 619.000 1,039.000 822.000 1,194.000 249.347 10.823 ns -3.686 9.364

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 -6.701 -6.692 -6.672 -6.617 -6.564 -6.546 -6.544 0.107 0.146 0.034 -6.618 ppm -7.802e+06 1.547e+09
Temp ZONE0 60.686 61.224 62.300 64.990 66.604 66.604 67.142 4.304 5.380 1.169 64.824 °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.280 9.411 nSat 275.5 1872
TDOP 0.500 0.550 0.590 0.810 1.380 1.720 2.250 0.790 1.170 0.259 0.878 21.9 81.77

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 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -14.795 -14.279 -13.686 -7.013 -1.981 -1.245 -0.757 11.704 13.034 3.310 -7.536 ms -44.84 180.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 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -3.331 -0.853 -0.344 0.285 0.950 1.446 4.969 1.293 2.299 0.449 0.287 ms -0.8691 14.62

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.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 -65.840 22.474 51.311 93.596 122.520 134.875 207.003 71.209 112.401 23.153 91.206 µs 33.47 122.7

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) 1.830 3.608 3.858 4.280 4.852 5.341 6.076 0.994 1.733 0.320 4.305 ms 1970 2.504e+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 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 0.263 2.067 2.289 2.609 3.071 3.572 4.471 0.783 1.505 0.295 2.629 ms 519.8 4311

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 -5.391 -3.092 -2.794 -2.094 -1.255 -0.789 0.147 1.539 2.303 0.462 -2.084 ms -183.5 1106

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) -104.926 -54.966 -0.979 2.056 18.304 67.093 101.788 19.283 122.060 14.740 2.629 ms -2.694 23.31

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) -62.207 -53.605 -6.211 4.218 10.922 13.708 18.144 17.133 67.314 9.678 2.962 ms -6.834 40.41

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) -76.406 -69.563 -65.341 -55.702 -46.195 -43.768 -41.799 19.146 25.795 5.792 -55.880 ms -1239 1.354e+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,254.000 -576.000 -393.000 8.000 431.000 620.000 1,040.000 824.000 1,196.000 250.102 10.849 ns -3.687 9.353

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 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.153 0.234 0.356 1.863 9.508 13.695 57.774 9.152 13.461 3.903 3.211 ms 4.917 60.7

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 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.169 0.341 0.599 1.986 9.738 16.060 137.213 9.138 15.719 5.892 3.557 ms 13.33 280.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 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.004 0.015 0.023 0.097 8.646 9.210 180.865 8.622 9.195 3.211 1.174 ms 16.08 899.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: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.120 0.246 0.415 1.990 10.170 15.770 182.017 9.755 15.524 8.564 3.883 ms 13.22 254.7

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 204.123.2.5

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.077 0.183 0.340 1.886 9.161 12.384 14.545 8.821 12.201 2.955 3.037 ms 1.558 4.364

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.095 0.237 0.379 1.857 10.915 55.478 185.413 10.536 55.241 13.513 4.725 ms 7.286 83.79

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.133 0.245 0.384 2.166 26.487 80.286 214.381 26.102 80.041 17.764 7.028 ms 5.739 60.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 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.130 0.276 0.416 2.448 21.084 118.284 231.310 20.668 118.008 18.850 6.836 ms 5.634 54.74

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.080 0.311 0.579 2.539 6.918 8.627 12.654 6.339 8.316 2.048 3.040 ms 2.427 6.317

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) 33.000 72.000 98.000 207.000 459.000 614.000 1,190.000 361.000 542.000 115.824 233.829 ns 5.519 19.06

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 -6.701 -6.692 -6.672 -6.617 -6.564 -6.546 -6.544 0.107 0.146 0.034 -6.618 ppm -7.802e+06 1.547e+09
Local Clock Time Offset -1,253.000 -575.000 -392.000 7.000 430.000 619.000 1,039.000 822.000 1,194.000 249.347 10.823 ns -3.686 9.364
Local RMS Frequency Jitter 19.000 28.000 34.000 55.000 95.000 120.000 218.000 61.000 92.000 19.780 58.334 10e-12 14.46 52.28
Local RMS Time Jitter 58.000 103.000 121.000 178.000 333.000 444.000 624.000 212.000 341.000 67.021 193.577 ns 14.29 56.24
Server Jitter 162.159.200.1 0.153 0.234 0.356 1.863 9.508 13.695 57.774 9.152 13.461 3.903 3.211 ms 4.917 60.7
Server Jitter 173.11.101.155 0.169 0.341 0.599 1.986 9.738 16.060 137.213 9.138 15.719 5.892 3.557 ms 13.33 280.9
Server Jitter 192.168.1.10 0.004 0.015 0.023 0.097 8.646 9.210 180.865 8.622 9.195 3.211 1.174 ms 16.08 899.5
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.120 0.246 0.415 1.990 10.170 15.770 182.017 9.755 15.524 8.564 3.883 ms 13.22 254.7
Server Jitter 204.123.2.5 0.077 0.183 0.340 1.886 9.161 12.384 14.545 8.821 12.201 2.955 3.037 ms 1.558 4.364
Server Jitter 2405:fc00:0:1::123 0.095 0.237 0.379 1.857 10.915 55.478 185.413 10.536 55.241 13.513 4.725 ms 7.286 83.79
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.133 0.245 0.384 2.166 26.487 80.286 214.381 26.102 80.041 17.764 7.028 ms 5.739 60.16
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.130 0.276 0.416 2.448 21.084 118.284 231.310 20.668 118.008 18.850 6.836 ms 5.634 54.74
Server Jitter SHM(0) 0.080 0.311 0.579 2.539 6.918 8.627 12.654 6.339 8.316 2.048 3.040 ms 2.427 6.317
Server Jitter SHM(1) 33.000 72.000 98.000 207.000 459.000 614.000 1,190.000 361.000 542.000 115.824 233.829 ns 5.519 19.06
Server Offset 162.159.200.1 -14.795 -14.279 -13.686 -7.013 -1.981 -1.245 -0.757 11.704 13.034 3.310 -7.536 ms -44.84 180.1
Server Offset 173.11.101.155 -3.331 -0.853 -0.344 0.285 0.950 1.446 4.969 1.293 2.299 0.449 0.287 ms -0.8691 14.62
Server Offset 192.168.1.10 -65.840 22.474 51.311 93.596 122.520 134.875 207.003 71.209 112.401 23.153 91.206 µs 33.47 122.7
Server Offset 2001:470:e815::24 (pi4.rellim.com) 1.830 3.608 3.858 4.280 4.852 5.341 6.076 0.994 1.733 0.320 4.305 ms 1970 2.504e+04
Server Offset 204.123.2.5 0.263 2.067 2.289 2.609 3.071 3.572 4.471 0.783 1.505 0.295 2.629 ms 519.8 4311
Server Offset 2405:fc00:0:1::123 -5.391 -3.092 -2.794 -2.094 -1.255 -0.789 0.147 1.539 2.303 0.462 -2.084 ms -183.5 1106
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -104.926 -54.966 -0.979 2.056 18.304 67.093 101.788 19.283 122.060 14.740 2.629 ms -2.694 23.31
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -62.207 -53.605 -6.211 4.218 10.922 13.708 18.144 17.133 67.314 9.678 2.962 ms -6.834 40.41
Server Offset SHM(0) -76.406 -69.563 -65.341 -55.702 -46.195 -43.768 -41.799 19.146 25.795 5.792 -55.880 ms -1239 1.354e+04
Server Offset SHM(1) -1,254.000 -576.000 -393.000 8.000 431.000 620.000 1,040.000 824.000 1,196.000 250.102 10.849 ns -3.687 9.353
TDOP 0.500 0.550 0.590 0.810 1.380 1.720 2.250 0.790 1.170 0.259 0.878 21.9 81.77
Temp ZONE0 60.686 61.224 62.300 64.990 66.604 66.604 67.142 4.304 5.380 1.169 64.824 °C
nSats 6.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.280 9.411 nSat 275.5 1872
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!