NTPsec

b-ntpsec-72-hour-stats

Report generated: Mon Sep 16 01:05:50 2019 UTC
Start Time: Fri Sep 13 01:05:37 2019 UTC
End Time: Mon Sep 16 01:05:37 2019 UTC
Report published: Sun Sep 15 18:06:39 2019 PDT
Report Period: 3.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,298.000 -742.000 -491.000 19.000 502.000 693.000 1,063.000 993.000 1,435.000 300.945 15.093 ns -3.875 10.09
Local Clock Frequency Offset -5.760 -5.759 -5.752 -5.665 -5.638 -5.635 -5.634 0.113 0.123 0.042 -5.684 ppm -2.575e+06 3.53e+08

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 107.000 136.000 161.000 248.000 367.000 423.000 550.000 206.000 287.000 63.089 253.674 ns 37.16 147.7

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 24.000 31.000 38.000 61.000 129.000 158.000 219.000 91.000 127.000 27.923 68.562 10e-12 8.894 30.8

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,298.000 -742.000 -491.000 19.000 502.000 693.000 1,063.000 993.000 1,435.000 300.945 15.093 ns -3.875 10.09

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.760 -5.759 -5.752 -5.665 -5.638 -5.635 -5.634 0.113 0.123 0.042 -5.684 ppm -2.575e+06 3.53e+08
Temp ZONE0 54.768 54.768 55.306 57.996 60.148 60.148 60.686 4.842 5.380 1.488 57.914 °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 12.000 12.000 12.000 5.000 5.000 1.445 9.413 nSat 184.1 1109
TDOP 0.490 0.570 0.610 0.840 1.440 1.700 2.740 0.830 1.130 0.268 0.906 22.2 86.3

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 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 -19.940 -9.257 0.550 2.963 5.094 6.783 7.108 4.544 16.040 2.322 2.786 ms -5.232 50.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 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.090 0.772 1.385 2.200 2.611 2.883 2.973 1.226 2.111 0.451 2.142 ms 59.27 251.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 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 0.224 1.951 2.121 2.374 2.737 3.141 5.721 0.615 1.190 0.259 2.398 ms 594.5 5240

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 -50.986 -4.227 -2.260 3.019 7.268 7.705 8.374 9.529 11.933 4.443 2.657 ms -9.044 107.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 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 -70.592 -8.541 14.076 52.360 86.463 108.821 226.166 72.387 117.362 23.846 51.643 µs 4.982 14.13

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 -0.706 -0.426 -0.160 6.737 7.209 7.638 8.896 7.369 8.064 2.977 5.058 ms 1.373 2.424

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 -0.099 1.250 1.367 1.685 2.201 4.302 4.539 0.834 3.052 0.440 1.756 ms 39.63 203.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 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 -0.428 1.921 2.173 2.455 2.799 3.219 4.282 0.625 1.298 0.245 2.462 ms 768.1 7210

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 -4.877 -3.303 -2.243 -0.739 0.995 2.390 3.779 3.238 5.693 1.024 -0.703 ms -9.491 28.09

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) -490.485 -430.906 -413.335 -367.641 -325.491 -310.406 -269.561 87.843 120.500 27.407 -368.654 ms -3061 4.488e+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,299.000 -743.000 -492.000 20.000 503.000 694.000 1,064.000 995.000 1,437.000 301.699 15.147 ns -3.874 10.08

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 0.000 0.000 0.000 1.266 12.312 19.514 25.291 12.312 19.514 4.199 2.804 ms 1.381 6.792

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 0.113 0.134 0.291 1.687 9.359 22.290 52.878 9.068 22.156 5.345 3.257 ms 5.265 48.82

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.109 0.169 0.295 1.583 10.385 18.068 52.598 10.091 17.899 5.103 3.611 ms 4.03 37.13

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 0.000 0.000 0.990 3.126 14.260 27.987 58.278 13.270 27.987 6.182 5.025 ms 3.969 28.85

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.011 0.017 0.029 0.125 8.689 10.128 123.630 8.659 10.112 3.569 1.579 ms 10.52 355

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.000 0.228 0.407 1.960 11.257 13.333 15.943 10.850 13.105 3.566 3.758 ms 1.294 3.402

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 0.000 0.153 0.296 1.658 10.498 16.870 60.118 10.202 16.717 4.268 3.461 ms 3.473 37.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 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.101 0.149 0.265 1.537 9.018 13.331 133.691 8.754 13.182 5.643 2.864 ms 15.17 350.8

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.682 0.937 1.543 14.936 96.886 111.703 128.454 95.343 110.766 28.279 24.914 ms 1.365 4.44

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) 1.794 4.632 6.235 11.698 23.341 31.183 72.065 17.106 26.551 5.532 12.881 ms 7.824 28.84

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) 34.000 91.000 121.000 236.000 458.000 581.000 905.000 337.000 490.000 105.508 255.410 ns 8.254 27.36

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.760 -5.759 -5.752 -5.665 -5.638 -5.635 -5.634 0.113 0.123 0.042 -5.684 ppm -2.575e+06 3.53e+08
Local Clock Time Offset -1,298.000 -742.000 -491.000 19.000 502.000 693.000 1,063.000 993.000 1,435.000 300.945 15.093 ns -3.875 10.09
Local RMS Frequency Jitter 24.000 31.000 38.000 61.000 129.000 158.000 219.000 91.000 127.000 27.923 68.562 10e-12 8.894 30.8
Local RMS Time Jitter 107.000 136.000 161.000 248.000 367.000 423.000 550.000 206.000 287.000 63.089 253.674 ns 37.16 147.7
Server Jitter 104.131.155.175 0.000 0.000 0.000 1.266 12.312 19.514 25.291 12.312 19.514 4.199 2.804 ms 1.381 6.792
Server Jitter 162.213.2.253 0.113 0.134 0.291 1.687 9.359 22.290 52.878 9.068 22.156 5.345 3.257 ms 5.265 48.82
Server Jitter 169.229.128.134 0.109 0.169 0.295 1.583 10.385 18.068 52.598 10.091 17.899 5.103 3.611 ms 4.03 37.13
Server Jitter 178.62.68.79 0.000 0.000 0.990 3.126 14.260 27.987 58.278 13.270 27.987 6.182 5.025 ms 3.969 28.85
Server Jitter 192.168.1.10 0.011 0.017 0.029 0.125 8.689 10.128 123.630 8.659 10.112 3.569 1.579 ms 10.52 355
Server Jitter 203.123.48.219 0.000 0.228 0.407 1.960 11.257 13.333 15.943 10.850 13.105 3.566 3.758 ms 1.294 3.402
Server Jitter 204.17.205.24 0.000 0.153 0.296 1.658 10.498 16.870 60.118 10.202 16.717 4.268 3.461 ms 3.473 37.87
Server Jitter 216.218.192.202 0.101 0.149 0.265 1.537 9.018 13.331 133.691 8.754 13.182 5.643 2.864 ms 15.17 350.8
Server Jitter 76.14.161.109 0.682 0.937 1.543 14.936 96.886 111.703 128.454 95.343 110.766 28.279 24.914 ms 1.365 4.44
Server Jitter SHM(0) 1.794 4.632 6.235 11.698 23.341 31.183 72.065 17.106 26.551 5.532 12.881 ms 7.824 28.84
Server Jitter SHM(1) 34.000 91.000 121.000 236.000 458.000 581.000 905.000 337.000 490.000 105.508 255.410 ns 8.254 27.36
Server Offset 104.131.155.175 -19.940 -9.257 0.550 2.963 5.094 6.783 7.108 4.544 16.040 2.322 2.786 ms -5.232 50.35
Server Offset 162.213.2.253 -2.090 0.772 1.385 2.200 2.611 2.883 2.973 1.226 2.111 0.451 2.142 ms 59.27 251.2
Server Offset 169.229.128.134 0.224 1.951 2.121 2.374 2.737 3.141 5.721 0.615 1.190 0.259 2.398 ms 594.5 5240
Server Offset 178.62.68.79 -50.986 -4.227 -2.260 3.019 7.268 7.705 8.374 9.529 11.933 4.443 2.657 ms -9.044 107.1
Server Offset 192.168.1.10 -70.592 -8.541 14.076 52.360 86.463 108.821 226.166 72.387 117.362 23.846 51.643 µs 4.982 14.13
Server Offset 203.123.48.219 -0.706 -0.426 -0.160 6.737 7.209 7.638 8.896 7.369 8.064 2.977 5.058 ms 1.373 2.424
Server Offset 204.17.205.24 -0.099 1.250 1.367 1.685 2.201 4.302 4.539 0.834 3.052 0.440 1.756 ms 39.63 203.1
Server Offset 216.218.192.202 -0.428 1.921 2.173 2.455 2.799 3.219 4.282 0.625 1.298 0.245 2.462 ms 768.1 7210
Server Offset 76.14.161.109 -4.877 -3.303 -2.243 -0.739 0.995 2.390 3.779 3.238 5.693 1.024 -0.703 ms -9.491 28.09
Server Offset SHM(0) -490.485 -430.906 -413.335 -367.641 -325.491 -310.406 -269.561 87.843 120.500 27.407 -368.654 ms -3061 4.488e+04
Server Offset SHM(1) -1,299.000 -743.000 -492.000 20.000 503.000 694.000 1,064.000 995.000 1,437.000 301.699 15.147 ns -3.874 10.08
TDOP 0.490 0.570 0.610 0.840 1.440 1.700 2.740 0.830 1.130 0.268 0.906 22.2 86.3
Temp ZONE0 54.768 54.768 55.306 57.996 60.148 60.148 60.686 4.842 5.380 1.488 57.914 °C
nSats 6.000 7.000 7.000 9.000 12.000 12.000 12.000 5.000 5.000 1.445 9.413 nSat 184.1 1109
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!