NTPsec

B-ntpsec-3-hour-stats

Report generated: Sun Aug 18 19:03:46 2019 UTC
Start Time: Sun Aug 18 16:03:44 2019 UTC
End Time: Sun Aug 18 19:03:44 2019 UTC
Report published: Sun Aug 18 12:03:54 2019 PDT
Report Period: 0.1 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 -572.000 -460.000 -315.000 50.000 423.000 525.000 804.000 738.000 985.000 225.052 51.015 ns -2.816 6.716
Local Clock Frequency Offset -5.769 -5.769 -5.769 -5.767 -5.763 -5.762 -5.761 0.0057 0.0077 0.0015 -5.767 ppm -5.347e+10 2.015e+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 123.000 150.000 179.000 240.000 338.000 389.000 470.000 159.000 239.000 49.011 245.535 ns 77.36 373.4

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 32.000 37.000 51.000 83.000 96.000 110.000 46.000 64.000 13.424 54.315 10e-12 38.58 160.6

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 -572.000 -460.000 -315.000 50.000 423.000 525.000 804.000 738.000 985.000 225.052 51.015 ns -2.816 6.716

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.769 -5.769 -5.769 -5.767 -5.763 -5.762 -5.761 0.0057 0.0077 0.0015 -5.767 ppm -5.347e+10 2.015e+14
Temp ZONE0 57.996 57.996 59.072 59.072 59.610 60.148 60.148 0.538 2.152 0.225 59.108 °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 6.000 6.000 7.000 9.000 9.000 9.000 3.000 3.000 0.702 7.441 nSat 915.1 9075
TDOP 0.670 0.670 0.720 0.960 1.820 1.890 2.500 1.100 1.220 0.344 1.102 18.28 65.06

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 0.083 2.327 3.716 3.800 3.800 3.633 4.072 1.013 2.460 ms 6.312 14.85

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.996 1.996 1.996 2.216 2.688 2.688 2.688 0.692 0.692 0.181 2.234 ms 1483 1.719e+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.125 2.125 2.202 2.394 2.777 3.016 3.016 0.575 0.891 0.182 2.446 ms 1975 2.514e+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.703 -3.703 -2.601 1.655 6.137 7.189 7.189 8.738 10.892 2.859 1.338 ms -1.685 3.572

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 -28.788 -1.817 11.211 50.450 76.280 85.495 86.071 65.069 87.312 19.831 48.901 µs 6.781 16.99

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.666 0.666 0.900 1.106 1.437 1.495 1.495 0.537 0.829 0.171 1.137 ms 198.9 1225

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.341 1.341 1.353 1.745 2.211 2.283 2.283 0.858 0.942 0.242 1.758 ms 266.5 1799

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.143 2.481 2.910 2.946 2.946 0.767 0.867 0.176 2.474 ms 2262 3.004e+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 -2.110 -0.501 0.278 0.717 0.717 2.388 4.302 0.840 -0.666 ms -12.39 43.68

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) -104.838 -98.500 -93.640 -83.100 -73.050 -70.066 -64.822 20.590 28.435 6.357 -83.193 ms -2838 4.059e+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) -573.000 -461.000 -316.000 51.000 424.000 526.000 805.000 740.000 987.000 225.810 51.184 ns -2.818 6.712

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.336 0.336 0.504 1.723 125.505 125.728 125.728 125.000 125.392 37.424 17.974 ms 0.6428 3.619

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.857 0.857 0.857 3.377 8.923 8.923 8.923 8.066 8.066 2.286 3.705 ms 2.959 7.428

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.231 0.231 0.299 1.532 8.791 9.184 9.184 8.491 8.953 2.538 2.521 ms 1.467 4.187

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.540 0.540 0.599 3.091 10.155 13.456 13.456 9.556 12.916 3.345 4.440 ms 1.764 4.243

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.013 0.025 0.131 8.681 10.719 24.522 8.656 10.706 3.526 1.986 ms 1.129 9.29

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.227 0.988 5.874 9.501 9.501 5.647 9.288 1.887 1.418 ms 2.271 9.219

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.191 0.191 0.350 1.402 5.173 10.798 10.798 4.823 10.607 1.942 1.860 ms 2.857 13.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 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.289 0.289 0.371 0.768 12.319 12.357 12.357 11.948 12.068 2.918 2.203 ms 1.517 5.952

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 1.366 1.366 1.941 10.015 36.685 38.865 38.865 34.744 37.499 11.634 14.662 ms 1.399 3.065

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.825 3.832 7.156 13.100 16.010 23.295 9.268 13.185 2.843 7.636 ms 10.81 35.94

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) 71.000 100.000 127.000 230.000 416.000 503.000 600.000 289.000 403.000 88.731 244.632 ns 11.6 38.29

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.769 -5.769 -5.769 -5.767 -5.763 -5.762 -5.761 0.0057 0.0077 0.0015 -5.767 ppm -5.347e+10 2.015e+14
Local Clock Time Offset -572.000 -460.000 -315.000 50.000 423.000 525.000 804.000 738.000 985.000 225.052 51.015 ns -2.816 6.716
Local RMS Frequency Jitter 28.000 32.000 37.000 51.000 83.000 96.000 110.000 46.000 64.000 13.424 54.315 10e-12 38.58 160.6
Local RMS Time Jitter 123.000 150.000 179.000 240.000 338.000 389.000 470.000 159.000 239.000 49.011 245.535 ns 77.36 373.4
Server Jitter 104.131.155.175 0.336 0.336 0.504 1.723 125.505 125.728 125.728 125.000 125.392 37.424 17.974 ms 0.6428 3.619
Server Jitter 162.213.2.253 0.857 0.857 0.857 3.377 8.923 8.923 8.923 8.066 8.066 2.286 3.705 ms 2.959 7.428
Server Jitter 169.229.128.134 0.231 0.231 0.299 1.532 8.791 9.184 9.184 8.491 8.953 2.538 2.521 ms 1.467 4.187
Server Jitter 178.62.68.79 0.540 0.540 0.599 3.091 10.155 13.456 13.456 9.556 12.916 3.345 4.440 ms 1.764 4.243
Server Jitter 192.168.1.10 0.013 0.013 0.025 0.131 8.681 10.719 24.522 8.656 10.706 3.526 1.986 ms 1.129 9.29
Server Jitter 203.123.48.219 0.213 0.213 0.227 0.988 5.874 9.501 9.501 5.647 9.288 1.887 1.418 ms 2.271 9.219
Server Jitter 204.17.205.24 0.191 0.191 0.350 1.402 5.173 10.798 10.798 4.823 10.607 1.942 1.860 ms 2.857 13.2
Server Jitter 66.220.9.122 0.289 0.289 0.371 0.768 12.319 12.357 12.357 11.948 12.068 2.918 2.203 ms 1.517 5.952
Server Jitter 76.14.161.109 1.366 1.366 1.941 10.015 36.685 38.865 38.865 34.744 37.499 11.634 14.662 ms 1.399 3.065
Server Jitter SHM(0) 1.442 2.825 3.832 7.156 13.100 16.010 23.295 9.268 13.185 2.843 7.636 ms 10.81 35.94
Server Jitter SHM(1) 71.000 100.000 127.000 230.000 416.000 503.000 600.000 289.000 403.000 88.731 244.632 ns 11.6 38.29
Server Offset 104.131.155.175 -0.273 -0.273 0.083 2.327 3.716 3.800 3.800 3.633 4.072 1.013 2.460 ms 6.312 14.85
Server Offset 162.213.2.253 1.996 1.996 1.996 2.216 2.688 2.688 2.688 0.692 0.692 0.181 2.234 ms 1483 1.719e+04
Server Offset 169.229.128.134 2.125 2.125 2.202 2.394 2.777 3.016 3.016 0.575 0.891 0.182 2.446 ms 1975 2.514e+04
Server Offset 178.62.68.79 -3.703 -3.703 -2.601 1.655 6.137 7.189 7.189 8.738 10.892 2.859 1.338 ms -1.685 3.572
Server Offset 192.168.1.10 -28.788 -1.817 11.211 50.450 76.280 85.495 86.071 65.069 87.312 19.831 48.901 µs 6.781 16.99
Server Offset 203.123.48.219 0.666 0.666 0.900 1.106 1.437 1.495 1.495 0.537 0.829 0.171 1.137 ms 198.9 1225
Server Offset 204.17.205.24 1.341 1.341 1.353 1.745 2.211 2.283 2.283 0.858 0.942 0.242 1.758 ms 266.5 1799
Server Offset 66.220.9.122 2.079 2.079 2.143 2.481 2.910 2.946 2.946 0.767 0.867 0.176 2.474 ms 2262 3.004e+04
Server Offset 76.14.161.109 -3.584 -3.584 -2.110 -0.501 0.278 0.717 0.717 2.388 4.302 0.840 -0.666 ms -12.39 43.68
Server Offset SHM(0) -104.838 -98.500 -93.640 -83.100 -73.050 -70.066 -64.822 20.590 28.435 6.357 -83.193 ms -2838 4.059e+04
Server Offset SHM(1) -573.000 -461.000 -316.000 51.000 424.000 526.000 805.000 740.000 987.000 225.810 51.184 ns -2.818 6.712
TDOP 0.670 0.670 0.720 0.960 1.820 1.890 2.500 1.100 1.220 0.344 1.102 18.28 65.06
Temp ZONE0 57.996 57.996 59.072 59.072 59.610 60.148 60.148 0.538 2.152 0.225 59.108 °C
nSats 6.000 6.000 6.000 7.000 9.000 9.000 9.000 3.000 3.000 0.702 7.441 nSat 915.1 9075
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!