NTPsec

B-ntpsec-6-hour-stats

Report generated: Sun Aug 18 19:05:18 2019 UTC
Start Time: Sun Aug 18 13:05:16 2019 UTC
End Time: Sun Aug 18 19:05:16 2019 UTC
Report published: Sun Aug 18 12:05:28 2019 PDT
Report Period: 0.2 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 -621.000 -455.000 -296.000 58.000 442.000 588.000 825.000 738.000 1,043.000 226.701 64.365 ns -2.443 5.961
Local Clock Frequency Offset -5.782 -5.782 -5.781 -5.769 -5.765 -5.762 -5.761 0.0160 0.0194 0.0052 -5.771 ppm -1.387e+09 1.547e+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 123.000 154.000 179.000 246.000 342.000 397.000 470.000 163.000 243.000 49.534 251.051 ns 80.24 388.8

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 28.000 34.000 38.000 53.000 85.000 97.000 110.000 47.000 63.000 13.685 55.820 10e-12 39.44 163.3

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 -621.000 -455.000 -296.000 58.000 442.000 588.000 825.000 738.000 1,043.000 226.701 64.365 ns -2.443 5.961

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.782 -5.782 -5.781 -5.769 -5.765 -5.762 -5.761 0.0160 0.0194 0.0052 -5.771 ppm -1.387e+09 1.547e+12
Temp ZONE0 57.996 58.534 59.072 59.072 59.610 60.148 60.148 0.538 1.614 0.260 59.157 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 5.000 6.000 6.000 8.000 11.000 11.000 11.000 5.000 5.000 1.252 7.840 nSat 162.2 953
TDOP 0.610 0.610 0.620 1.070 2.210 2.760 2.910 1.590 2.150 0.470 1.192 9.435 31.67

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 -0.273 -0.273 1.428 3.263 4.129 4.699 4.699 2.701 4.972 0.903 2.984 ms 17.8 53.26

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 1.972 1.972 1.996 2.213 2.499 2.688 2.688 0.502 0.717 0.168 2.234 ms 1911 2.403e+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 1.970 1.970 2.153 2.385 2.691 3.016 3.016 0.538 1.046 0.170 2.399 ms 2316 3.101e+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 -3.713 -3.713 -3.501 -1.153 4.938 7.189 7.189 8.439 10.902 2.817 -0.169 ms -3.611 7.171

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 -53.379 -1.817 12.277 49.385 75.863 83.836 96.455 63.586 85.653 20.322 47.625 µs 5.59 14.34

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.589 0.589 0.837 1.088 1.366 1.495 1.495 0.529 0.906 0.166 1.086 ms 187.1 1132

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.277 1.277 1.353 1.699 2.139 2.283 2.283 0.786 1.007 0.216 1.706 ms 347.2 2545

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 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 2.079 2.079 2.231 2.472 2.709 2.946 2.946 0.478 0.867 0.152 2.469 ms 3581 5.527e+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 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 -3.584 -3.584 -1.882 -0.536 0.717 2.934 2.934 2.599 6.519 0.922 -0.556 ms -8.373 24.92

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) -110.878 -103.426 -97.764 -84.869 -74.001 -70.641 -62.770 23.763 32.785 7.188 -85.188 ms -2162 2.829e+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) -622.000 -456.000 -297.000 59.000 443.000 589.000 826.000 740.000 1,045.000 227.443 64.555 ns -2.446 5.959

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.256 0.256 0.336 1.041 33.309 125.728 125.728 32.973 125.472 26.682 9.265 ms 1.615 9.211

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.401 0.401 0.520 3.377 8.923 9.069 9.069 8.402 8.668 2.979 3.923 ms 1.562 3.266

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.202 0.202 0.252 0.862 8.782 9.184 9.184 8.530 8.982 2.877 2.401 ms 0.8329 2.598

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.261 0.261 0.467 2.044 9.331 13.456 13.456 8.864 13.194 3.168 3.433 ms 1.312 3.534

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.013 0.015 0.031 0.121 8.634 8.711 24.522 8.603 8.697 2.953 1.539 ms 1.292 11.21

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.213 0.213 0.282 0.973 8.626 9.501 9.501 8.344 9.288 2.168 1.584 ms 1.957 6.942

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.130 0.130 0.255 1.372 8.835 10.798 10.798 8.580 10.668 2.533 2.183 ms 1.5 4.871

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 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 0.156 0.156 0.261 0.936 10.689 12.357 12.357 10.428 12.201 2.869 2.260 ms 1.441 5.35

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.744 0.744 1.270 9.679 36.829 38.865 38.865 35.558 38.121 11.911 13.669 ms 1.174 2.767

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.442 2.961 3.920 7.336 13.551 16.797 23.295 9.630 13.836 2.973 7.867 ms 10.36 34.2

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

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

RMS Jitter is field 8 in the peerstats log file.



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) 70.000 105.000 133.000 237.000 435.000 546.000 714.000 302.000 441.000 94.040 254.009 ns 11.11 37.75

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.782 -5.782 -5.781 -5.769 -5.765 -5.762 -5.761 0.0160 0.0194 0.0052 -5.771 ppm -1.387e+09 1.547e+12
Local Clock Time Offset -621.000 -455.000 -296.000 58.000 442.000 588.000 825.000 738.000 1,043.000 226.701 64.365 ns -2.443 5.961
Local RMS Frequency Jitter 28.000 34.000 38.000 53.000 85.000 97.000 110.000 47.000 63.000 13.685 55.820 10e-12 39.44 163.3
Local RMS Time Jitter 123.000 154.000 179.000 246.000 342.000 397.000 470.000 163.000 243.000 49.534 251.051 ns 80.24 388.8
Server Jitter 104.131.155.175 0.256 0.256 0.336 1.041 33.309 125.728 125.728 32.973 125.472 26.682 9.265 ms 1.615 9.211
Server Jitter 162.213.2.253 0.401 0.401 0.520 3.377 8.923 9.069 9.069 8.402 8.668 2.979 3.923 ms 1.562 3.266
Server Jitter 169.229.128.134 0.202 0.202 0.252 0.862 8.782 9.184 9.184 8.530 8.982 2.877 2.401 ms 0.8329 2.598
Server Jitter 178.62.68.79 0.261 0.261 0.467 2.044 9.331 13.456 13.456 8.864 13.194 3.168 3.433 ms 1.312 3.534
Server Jitter 192.168.1.10 0.013 0.015 0.031 0.121 8.634 8.711 24.522 8.603 8.697 2.953 1.539 ms 1.292 11.21
Server Jitter 203.123.48.219 0.213 0.213 0.282 0.973 8.626 9.501 9.501 8.344 9.288 2.168 1.584 ms 1.957 6.942
Server Jitter 204.17.205.24 0.130 0.130 0.255 1.372 8.835 10.798 10.798 8.580 10.668 2.533 2.183 ms 1.5 4.871
Server Jitter 66.220.9.122 0.156 0.156 0.261 0.936 10.689 12.357 12.357 10.428 12.201 2.869 2.260 ms 1.441 5.35
Server Jitter 76.14.161.109 0.744 0.744 1.270 9.679 36.829 38.865 38.865 35.558 38.121 11.911 13.669 ms 1.174 2.767
Server Jitter SHM(0) 1.442 2.961 3.920 7.336 13.551 16.797 23.295 9.630 13.836 2.973 7.867 ms 10.36 34.2
Server Jitter SHM(1) 70.000 105.000 133.000 237.000 435.000 546.000 714.000 302.000 441.000 94.040 254.009 ns 11.11 37.75
Server Offset 104.131.155.175 -0.273 -0.273 1.428 3.263 4.129 4.699 4.699 2.701 4.972 0.903 2.984 ms 17.8 53.26
Server Offset 162.213.2.253 1.972 1.972 1.996 2.213 2.499 2.688 2.688 0.502 0.717 0.168 2.234 ms 1911 2.403e+04
Server Offset 169.229.128.134 1.970 1.970 2.153 2.385 2.691 3.016 3.016 0.538 1.046 0.170 2.399 ms 2316 3.101e+04
Server Offset 178.62.68.79 -3.713 -3.713 -3.501 -1.153 4.938 7.189 7.189 8.439 10.902 2.817 -0.169 ms -3.611 7.171
Server Offset 192.168.1.10 -53.379 -1.817 12.277 49.385 75.863 83.836 96.455 63.586 85.653 20.322 47.625 µs 5.59 14.34
Server Offset 203.123.48.219 0.589 0.589 0.837 1.088 1.366 1.495 1.495 0.529 0.906 0.166 1.086 ms 187.1 1132
Server Offset 204.17.205.24 1.277 1.277 1.353 1.699 2.139 2.283 2.283 0.786 1.007 0.216 1.706 ms 347.2 2545
Server Offset 66.220.9.122 2.079 2.079 2.231 2.472 2.709 2.946 2.946 0.478 0.867 0.152 2.469 ms 3581 5.527e+04
Server Offset 76.14.161.109 -3.584 -3.584 -1.882 -0.536 0.717 2.934 2.934 2.599 6.519 0.922 -0.556 ms -8.373 24.92
Server Offset SHM(0) -110.878 -103.426 -97.764 -84.869 -74.001 -70.641 -62.770 23.763 32.785 7.188 -85.188 ms -2162 2.829e+04
Server Offset SHM(1) -622.000 -456.000 -297.000 59.000 443.000 589.000 826.000 740.000 1,045.000 227.443 64.555 ns -2.446 5.959
TDOP 0.610 0.610 0.620 1.070 2.210 2.760 2.910 1.590 2.150 0.470 1.192 9.435 31.67
Temp ZONE0 57.996 58.534 59.072 59.072 59.610 60.148 60.148 0.538 1.614 0.260 59.157 °C
nSats 5.000 6.000 6.000 8.000 11.000 11.000 11.000 5.000 5.000 1.252 7.840 nSat 162.2 953
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!