NTPsec

B-ntpsec-1-hour-stats

Report generated: Mon Sep 16 02:02:15 2019 UTC
Start Time: Mon Sep 16 01:01:47 2019 UTC
End Time: Mon Sep 16 02:02:15 2019 UTC
Report published: Sun Sep 15 19:02:24 2019 PDT
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 -817.000 -780.000 -595.000 -189.000 116.000 194.000 412.000 711.000 974.000 223.308 -209.642 ns -13.43 42.14
Local Clock Frequency Offset -5.691 -5.691 -5.689 -5.684 -5.680 -5.679 -5.679 0.0098 0.0112 0.0033 -5.684 ppm -5.188e+09 8.981e+12

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 161.000 168.000 175.000 261.000 355.000 385.000 394.000 180.000 217.000 56.466 256.819 ns 55.57 239.9

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 35.000 35.000 40.000 68.000 107.000 118.000 122.000 67.000 83.000 19.917 69.398 10e-12 23.25 82.43

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 -817.000 -780.000 -595.000 -189.000 116.000 194.000 412.000 711.000 974.000 223.308 -209.642 ns -13.43 42.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.691 -5.691 -5.689 -5.684 -5.680 -5.679 -5.679 0.0098 0.0112 0.0033 -5.684 ppm -5.188e+09 8.981e+12
Temp ZONE0 57.996 57.996 57.996 59.072 59.072 59.610 59.610 1.076 1.614 0.338 58.929 °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 10.000 10.000 11.000 11.000 12.000 12.000 12.000 1.000 2.000 0.568 11.333 nSat 6878 1.315e+05
TDOP 0.690 0.690 0.700 0.780 0.870 0.990 0.990 0.170 0.300 0.067 0.793 1288 1.426e+04

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 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 1.517 1.517 1.517 1.517 1.517 1.517 1.517 0.000 0.000 0.000 1.517 ms nan nan

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 162.213.2.253

peer offset 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.213.2.253 2.123 2.123 2.123 2.203 2.560 2.560 2.560 0.438 0.438 0.146 2.263 ms 3119 4.604e+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 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 2.101 2.101 2.101 2.502 2.616 2.616 2.616 0.516 0.516 0.157 2.426 ms 3038 4.439e+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 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.380 2.380 2.380 4.420 7.216 7.216 7.216 4.836 4.836 1.724 4.974 ms 12.23 34.79

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 -12.842 -12.842 5.664 46.179 81.888 87.000 87.000 76.224 99.842 23.230 44.858 µs 3.401 7.556

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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 -752.724 -752.724 -752.724 -6.940 221.283 221.283 221.283 974.007 974.007 293.274 -113.784 µs -7.812 23.5

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

peer offset 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.24 1.035 1.035 1.035 1.835 2.286 2.286 2.286 1.251 1.251 0.343 1.765 ms 82.89 391.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 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 2.019 2.019 2.019 2.520 2.925 2.925 2.925 0.907 0.907 0.248 2.480 ms 751.6 6995

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 -1.543 -1.543 -1.543 -0.709 1.814 1.814 1.814 3.357 3.357 0.914 -0.552 ms -7.351 16.63

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) -465.399 -433.413 -421.041 -401.799 -382.917 -374.490 -350.848 38.125 58.923 11.995 -401.892 ms -4.118e+04 1.425e+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 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) -818.000 -781.000 -596.000 -190.000 117.000 195.000 413.000 713.000 976.000 223.819 -210.252 ns -13.43 42.11

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 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 13.641 13.641 13.641 13.641 13.641 13.641 13.641 0.000 0.000 0.000 13.641 ms nan nan

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 162.213.2.253

peer jitter 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.213.2.253 1.531 1.531 1.531 4.330 4.744 4.744 4.744 3.213 3.213 1.267 3.495 ms 10.27 26.46

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 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 169.229.128.134 0.890 0.890 0.890 1.753 10.548 10.548 10.548 9.658 9.658 3.195 3.104 ms 1.709 4.227

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 1.397 1.397 1.397 7.437 9.077 9.077 9.077 7.680 7.680 2.759 6.616 ms 5.801 11.99

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.028 0.028 0.038 0.202 8.608 10.522 10.522 8.570 10.494 2.818 1.606 ms 0.6204 3.425

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 203.123.48.219

peer jitter 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 203.123.48.219 0.818 0.818 0.818 3.231 18.880 18.880 18.880 18.062 18.062 6.009 6.838 ms 1.431 3.319

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

peer jitter 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.24 1.449 1.449 1.449 3.906 8.928 8.928 8.928 7.479 7.479 2.348 3.864 ms 3.444 9.316

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

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.611 0.611 0.611 1.619 4.077 4.077 4.077 3.466 3.466 0.946 1.700 ms 3.845 10.77

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 8.344 8.344 8.344 39.980 107.830 107.830 107.830 99.486 99.486 33.932 42.120 ms 1.755 3.988

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) 3.015 4.514 6.082 11.244 22.572 31.158 49.035 16.490 26.644 5.556 12.508 ms 7.493 29.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) 85.000 98.000 134.000 248.000 441.000 539.000 565.000 307.000 441.000 95.124 259.712 ns 11.21 36.23

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.691 -5.691 -5.689 -5.684 -5.680 -5.679 -5.679 0.0098 0.0112 0.0033 -5.684 ppm -5.188e+09 8.981e+12
Local Clock Time Offset -817.000 -780.000 -595.000 -189.000 116.000 194.000 412.000 711.000 974.000 223.308 -209.642 ns -13.43 42.14
Local RMS Frequency Jitter 35.000 35.000 40.000 68.000 107.000 118.000 122.000 67.000 83.000 19.917 69.398 10e-12 23.25 82.43
Local RMS Time Jitter 161.000 168.000 175.000 261.000 355.000 385.000 394.000 180.000 217.000 56.466 256.819 ns 55.57 239.9
Server Jitter 104.131.155.175 13.641 13.641 13.641 13.641 13.641 13.641 13.641 0.000 0.000 0.000 13.641 ms nan nan
Server Jitter 162.213.2.253 1.531 1.531 1.531 4.330 4.744 4.744 4.744 3.213 3.213 1.267 3.495 ms 10.27 26.46
Server Jitter 169.229.128.134 0.890 0.890 0.890 1.753 10.548 10.548 10.548 9.658 9.658 3.195 3.104 ms 1.709 4.227
Server Jitter 178.62.68.79 1.397 1.397 1.397 7.437 9.077 9.077 9.077 7.680 7.680 2.759 6.616 ms 5.801 11.99
Server Jitter 192.168.1.10 0.028 0.028 0.038 0.202 8.608 10.522 10.522 8.570 10.494 2.818 1.606 ms 0.6204 3.425
Server Jitter 203.123.48.219 0.818 0.818 0.818 3.231 18.880 18.880 18.880 18.062 18.062 6.009 6.838 ms 1.431 3.319
Server Jitter 204.17.205.24 1.449 1.449 1.449 3.906 8.928 8.928 8.928 7.479 7.479 2.348 3.864 ms 3.444 9.316
Server Jitter 216.218.192.202 0.611 0.611 0.611 1.619 4.077 4.077 4.077 3.466 3.466 0.946 1.700 ms 3.845 10.77
Server Jitter 76.14.161.109 8.344 8.344 8.344 39.980 107.830 107.830 107.830 99.486 99.486 33.932 42.120 ms 1.755 3.988
Server Jitter SHM(0) 3.015 4.514 6.082 11.244 22.572 31.158 49.035 16.490 26.644 5.556 12.508 ms 7.493 29.3
Server Jitter SHM(1) 85.000 98.000 134.000 248.000 441.000 539.000 565.000 307.000 441.000 95.124 259.712 ns 11.21 36.23
Server Offset 104.131.155.175 1.517 1.517 1.517 1.517 1.517 1.517 1.517 0.000 0.000 0.000 1.517 ms nan nan
Server Offset 162.213.2.253 2.123 2.123 2.123 2.203 2.560 2.560 2.560 0.438 0.438 0.146 2.263 ms 3119 4.604e+04
Server Offset 169.229.128.134 2.101 2.101 2.101 2.502 2.616 2.616 2.616 0.516 0.516 0.157 2.426 ms 3038 4.439e+04
Server Offset 178.62.68.79 2.380 2.380 2.380 4.420 7.216 7.216 7.216 4.836 4.836 1.724 4.974 ms 12.23 34.79
Server Offset 192.168.1.10 -12.842 -12.842 5.664 46.179 81.888 87.000 87.000 76.224 99.842 23.230 44.858 µs 3.401 7.556
Server Offset 203.123.48.219 -752.724 -752.724 -752.724 -6.940 221.283 221.283 221.283 974.007 974.007 293.274 -113.784 µs -7.812 23.5
Server Offset 204.17.205.24 1.035 1.035 1.035 1.835 2.286 2.286 2.286 1.251 1.251 0.343 1.765 ms 82.89 391.2
Server Offset 216.218.192.202 2.019 2.019 2.019 2.520 2.925 2.925 2.925 0.907 0.907 0.248 2.480 ms 751.6 6995
Server Offset 76.14.161.109 -1.543 -1.543 -1.543 -0.709 1.814 1.814 1.814 3.357 3.357 0.914 -0.552 ms -7.351 16.63
Server Offset SHM(0) -465.399 -433.413 -421.041 -401.799 -382.917 -374.490 -350.848 38.125 58.923 11.995 -401.892 ms -4.118e+04 1.425e+06
Server Offset SHM(1) -818.000 -781.000 -596.000 -190.000 117.000 195.000 413.000 713.000 976.000 223.819 -210.252 ns -13.43 42.11
TDOP 0.690 0.690 0.700 0.780 0.870 0.990 0.990 0.170 0.300 0.067 0.793 1288 1.426e+04
Temp ZONE0 57.996 57.996 57.996 59.072 59.072 59.610 59.610 1.076 1.614 0.338 58.929 °C
nSats 10.000 10.000 11.000 11.000 12.000 12.000 12.000 1.000 2.000 0.568 11.333 nSat 6878 1.315e+05
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!