NTPsec

C-ntpsec-1-hour-stats

Report generated: Wed Nov 20 18:02:30 2019 UTC
Start Time: Wed Nov 20 17:02:02 2019 UTC
End Time: Wed Nov 20 18:02:30 2019 UTC
Report published: Wed Nov 20 10:03:39 2019 PST
Report Period: 0.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 -664.000 -630.000 -487.000 -116.000 179.000 276.000 318.000 666.000 906.000 202.266 -136.600 ns -9.943 28.83
Local Clock Frequency Offset -6.791 -6.790 -6.790 -6.786 -6.784 -6.783 -6.783 0.0062 0.0074 0.0020 -6.786 ppm -4.138e+10 1.431e+14

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 104.000 110.000 132.000 179.000 247.000 263.000 277.000 115.000 153.000 37.371 184.893 ns 73.65 343.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 26.000 27.000 34.000 52.000 96.000 102.000 105.000 62.000 75.000 18.461 56.604 10e-12 15.78 52.91

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 -664.000 -630.000 -487.000 -116.000 179.000 276.000 318.000 666.000 906.000 202.266 -136.600 ns -9.943 28.83

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.791 -6.790 -6.790 -6.786 -6.784 -6.783 -6.783 0.0062 0.0074 0.0020 -6.786 ppm -4.138e+10 1.431e+14
Temp ZONE0 63.376 63.376 63.376 64.452 64.452 64.452 64.452 1.076 1.076 0.405 64.111 °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 8.000 8.000 8.000 8.000 10.000 10.000 10.000 2.000 2.000 0.551 8.283 nSat 2816 4.022e+04
TDOP 0.670 0.670 0.870 1.390 1.470 1.490 1.490 0.600 0.820 0.234 1.279 101 497.7

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 -8.367 -8.367 -8.367 -8.161 -7.786 -7.786 -7.786 0.581 0.581 0.163 -8.126 ms -1.316e+05 6.696e+06

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 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 -491.546 -491.546 -491.546 46.878 495.762 495.762 495.762 987.308 987.308 360.148 98.145 µs -2.888 5.96

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 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 -2.387 -2.387 -2.387 0.420 0.420 0.420 0.420 2.807 2.807 1.404 -0.983 ms -10.02 26.71

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 -25.931 -25.931 63.936 101.966 118.274 138.378 138.378 54.338 164.309 23.650 97.293 µs 36.61 131.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) 3.893 3.893 3.893 4.199 4.684 4.684 4.684 0.790 0.790 0.217 4.193 ms 6236 1.155e+05

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 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 2.185 2.185 2.185 2.270 2.475 2.475 2.475 0.290 0.290 0.106 2.319 ms 9175 1.93e+05

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 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 -2.473 -2.473 -2.473 -2.154 -2.078 -2.078 -2.078 0.395 0.395 0.111 -2.202 ms -9066 1.899e+05

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 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.197 2.197 2.197 3.135 3.620 3.620 3.620 1.424 1.424 0.467 2.999 ms 175.3 1036

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) -56.250 -56.250 -55.965 -51.682 -45.597 -45.465 -45.465 10.368 10.785 3.544 -51.168 ms -3727 5.824e+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) -665.000 -631.000 -488.000 -117.000 180.000 277.000 319.000 668.000 908.000 202.846 -137.071 ns -9.941 28.8

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.138 0.138 0.138 1.414 8.801 8.801 8.801 8.663 8.663 2.829 2.261 ms 1.167 3.238

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.691 0.691 0.691 1.630 9.215 9.215 9.215 8.525 8.525 2.139 2.342 ms 2.765 9.281

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 178.62.68.79

peer jitter 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.62.68.79 2.091 2.091 2.091 3.746 3.746 3.746 3.746 1.655 1.655 0.828 2.918 ms 23.71 80.07

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.020 0.020 0.026 0.109 8.599 8.645 8.645 8.573 8.626 2.537 1.172 ms 0.4923 3.483

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.297 0.297 0.297 0.583 4.221 4.221 4.221 3.924 3.924 1.447 1.299 ms 0.9772 2.247

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.376 0.376 0.376 1.408 5.495 5.495 5.495 5.119 5.119 2.264 2.725 ms 0.9654 1.735

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.392 0.392 0.392 9.282 12.195 12.195 12.195 11.803 11.803 4.875 6.176 ms 0.7411 1.581

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.277 0.277 0.277 8.669 12.339 12.339 12.339 12.062 12.062 4.818 6.719 ms 1.168 2.221

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.368 0.368 0.463 2.588 6.407 7.373 7.373 5.945 7.005 1.894 2.590 ms 1.789 4.22

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) 73.000 76.000 104.000 190.000 379.000 450.000 528.000 275.000 374.000 86.238 212.018 ns 8.371 25.86

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.791 -6.790 -6.790 -6.786 -6.784 -6.783 -6.783 0.0062 0.0074 0.0020 -6.786 ppm -4.138e+10 1.431e+14
Local Clock Time Offset -664.000 -630.000 -487.000 -116.000 179.000 276.000 318.000 666.000 906.000 202.266 -136.600 ns -9.943 28.83
Local RMS Frequency Jitter 26.000 27.000 34.000 52.000 96.000 102.000 105.000 62.000 75.000 18.461 56.604 10e-12 15.78 52.91
Local RMS Time Jitter 104.000 110.000 132.000 179.000 247.000 263.000 277.000 115.000 153.000 37.371 184.893 ns 73.65 343.2
Server Jitter 162.159.200.1 0.138 0.138 0.138 1.414 8.801 8.801 8.801 8.663 8.663 2.829 2.261 ms 1.167 3.238
Server Jitter 173.11.101.155 0.691 0.691 0.691 1.630 9.215 9.215 9.215 8.525 8.525 2.139 2.342 ms 2.765 9.281
Server Jitter 178.62.68.79 2.091 2.091 2.091 3.746 3.746 3.746 3.746 1.655 1.655 0.828 2.918 ms 23.71 80.07
Server Jitter 192.168.1.10 0.020 0.020 0.026 0.109 8.599 8.645 8.645 8.573 8.626 2.537 1.172 ms 0.4923 3.483
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.297 0.297 0.297 0.583 4.221 4.221 4.221 3.924 3.924 1.447 1.299 ms 0.9772 2.247
Server Jitter 204.123.2.5 0.376 0.376 0.376 1.408 5.495 5.495 5.495 5.119 5.119 2.264 2.725 ms 0.9654 1.735
Server Jitter 2405:fc00:0:1::123 0.392 0.392 0.392 9.282 12.195 12.195 12.195 11.803 11.803 4.875 6.176 ms 0.7411 1.581
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.277 0.277 0.277 8.669 12.339 12.339 12.339 12.062 12.062 4.818 6.719 ms 1.168 2.221
Server Jitter SHM(0) 0.368 0.368 0.463 2.588 6.407 7.373 7.373 5.945 7.005 1.894 2.590 ms 1.789 4.22
Server Jitter SHM(1) 73.000 76.000 104.000 190.000 379.000 450.000 528.000 275.000 374.000 86.238 212.018 ns 8.371 25.86
Server Offset 162.159.200.1 -8.367 -8.367 -8.367 -8.161 -7.786 -7.786 -7.786 0.581 0.581 0.163 -8.126 ms -1.316e+05 6.696e+06
Server Offset 173.11.101.155 -491.546 -491.546 -491.546 46.878 495.762 495.762 495.762 987.308 987.308 360.148 98.145 µs -2.888 5.96
Server Offset 178.62.68.79 -2.387 -2.387 -2.387 0.420 0.420 0.420 0.420 2.807 2.807 1.404 -0.983 ms -10.02 26.71
Server Offset 192.168.1.10 -25.931 -25.931 63.936 101.966 118.274 138.378 138.378 54.338 164.309 23.650 97.293 µs 36.61 131.7
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.893 3.893 3.893 4.199 4.684 4.684 4.684 0.790 0.790 0.217 4.193 ms 6236 1.155e+05
Server Offset 204.123.2.5 2.185 2.185 2.185 2.270 2.475 2.475 2.475 0.290 0.290 0.106 2.319 ms 9175 1.93e+05
Server Offset 2405:fc00:0:1::123 -2.473 -2.473 -2.473 -2.154 -2.078 -2.078 -2.078 0.395 0.395 0.111 -2.202 ms -9066 1.899e+05
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 2.197 2.197 2.197 3.135 3.620 3.620 3.620 1.424 1.424 0.467 2.999 ms 175.3 1036
Server Offset SHM(0) -56.250 -56.250 -55.965 -51.682 -45.597 -45.465 -45.465 10.368 10.785 3.544 -51.168 ms -3727 5.824e+04
Server Offset SHM(1) -665.000 -631.000 -488.000 -117.000 180.000 277.000 319.000 668.000 908.000 202.846 -137.071 ns -9.941 28.8
TDOP 0.670 0.670 0.870 1.390 1.470 1.490 1.490 0.600 0.820 0.234 1.279 101 497.7
Temp ZONE0 63.376 63.376 63.376 64.452 64.452 64.452 64.452 1.076 1.076 0.405 64.111 °C
nSats 8.000 8.000 8.000 8.000 10.000 10.000 10.000 2.000 2.000 0.551 8.283 nSat 2816 4.022e+04
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!