NTPsec

c-ntpsec-14-day-stats

Report generated: Thu Apr 2 04:12:23 2020 UTC
Start Time: Thu Mar 19 04:12:18 2020 UTC
End Time: Thu Apr 2 04:12:18 2020 UTC
Report published: Wed Apr 01 21:12:48 2020 PDT
Report Period: 14.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 -4,805.000 -567.000 -413.000 -4.000 447.000 639.000 1,807.000 860.000 1,206.000 262.026 2.670 ns -3.866 11.09
Local Clock Frequency Offset -5.669 -5.659 -5.631 -5.566 -5.513 -5.498 -5.488 0.118 0.160 0.035 -5.567 ppm -3.936e+06 6.214e+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 72.000 108.000 126.000 180.000 254.000 290.000 2,243.000 128.000 182.000 45.202 183.924 ns 46.59 548

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 0.020 0.029 0.035 0.057 0.101 0.129 10.403 0.066 0.100 0.110 0.063 ppb 59.87 4318

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 -4,805.000 -567.000 -413.000 -4.000 447.000 639.000 1,807.000 860.000 1,206.000 262.026 2.670 ns -3.866 11.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.669 -5.659 -5.631 -5.566 -5.513 -5.498 -5.488 0.118 0.160 0.035 -5.567 ppm -3.936e+06 6.214e+08
Temp ZONE0 62.300 63.376 63.914 65.528 66.604 67.142 67.680 2.690 3.766 0.845 65.397 °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 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.113 9.397 nSat 434.7 3406
TDOP 0.530 0.550 0.600 0.820 1.260 1.630 1.770 0.660 1.080 0.218 0.862 35.66 145.8

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 -8.979 -5.288 -1.126 2.879 4.259 5.400 8.016 5.386 10.687 1.769 2.560 ms -1.002 8.025

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

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -6.876 -5.667 -3.827 0.785 2.718 4.344 5.660 6.544 10.011 2.277 -0.092 ms -4.603 11.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 164.67.62.194

peer offset 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 164.67.62.194 -0.716 2.208 2.433 2.771 3.290 3.727 5.459 0.856 1.519 0.308 2.802 ms 555.5 4718

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

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

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

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



Server Offset 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -5.304 -1.730 -0.579 0.308 1.109 1.809 4.342 1.688 3.540 0.609 0.286 ms -2.644 17.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 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 -45.434 -5.374 0.654 5.716 10.151 13.139 17.047 9.497 18.513 3.926 5.398 ms -3.529 51.17

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 -109.598 -27.316 -2.795 87.432 140.288 148.746 223.583 143.083 176.062 46.979 79.220 µs 1.938 4.013

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 -8.961 -2.493 -2.131 -1.122 1.920 2.985 7.208 4.052 5.478 1.456 -0.556 ms -6.166 14.67

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

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

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

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



Server Offset 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 -4.160 1.878 2.299 2.654 3.361 5.224 27.878 1.062 3.346 1.052 2.765 ms 25.03 475.8

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

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

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

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



Server 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.196 1.291 1.568 2.016 3.005 3.635 11.438 1.437 2.344 0.546 2.105 ms 36.78 226.8

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

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

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

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



Server Offset 47.51.249.154

peer offset 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 47.51.249.154 -5.908 1.902 2.546 3.392 5.727 6.432 8.631 3.181 4.530 0.891 3.548 ms 36.54 154.8

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

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

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

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



Server 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) -73.141 -66.939 -64.137 -56.053 -47.395 -45.307 -43.239 16.742 21.632 4.976 -56.012 ms -1878 2.348e+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) -4,806.000 -569.000 -414.000 -5.000 448.000 641.000 2,141.000 862.000 1,210.000 263.570 2.770 ns -3.853 11.36

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.253 0.389 2.217 10.015 13.604 66.989 9.626 13.351 3.921 3.539 ms 4.886 64.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 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.000 0.199 0.309 1.762 9.397 14.638 246.678 9.087 14.439 7.668 3.326 ms 19.54 557.4

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 164.67.62.194

peer jitter 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 164.67.62.194 0.000 0.212 0.348 1.797 9.866 13.962 211.824 9.518 13.750 6.381 3.334 ms 20.26 627.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.000 0.349 0.650 2.090 10.245 17.065 246.881 9.596 16.715 8.434 3.848 ms 18.76 504.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 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.308 0.566 3.039 10.639 33.720 62.554 10.073 33.411 5.815 4.678 ms 4.229 33.47

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.000 0.019 0.035 0.143 8.653 9.420 155.428 8.618 9.401 3.630 1.268 ms 13.82 490.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 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.278 0.460 2.321 10.625 16.422 109.041 10.165 16.144 5.479 4.046 ms 7.123 98.17

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.123.2.5

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.763 9.115 14.258 254.490 9.115 14.258 11.185 3.403 ms 18.01 403.4

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.244 0.374 1.837 9.607 14.573 148.946 9.232 14.329 5.011 3.347 ms 12.91 347.6

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 47.51.249.154

peer jitter 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 47.51.249.154 0.000 0.556 0.964 3.227 11.116 32.614 83.844 10.152 32.059 5.404 4.714 ms 5.516 53.45

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.000 0.294 0.545 2.370 6.805 8.426 13.625 6.261 8.133 2.019 2.906 ms 2.316 6.018

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) 0.000 73.000 100.000 201.000 428.000 550.000 3,914.000 328.000 477.000 109.068 224.968 ns 8.188 103.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -5.669 -5.659 -5.631 -5.566 -5.513 -5.498 -5.488 0.118 0.160 0.035 -5.567 ppm -3.936e+06 6.214e+08
Local Clock Time Offset -4,805.000 -567.000 -413.000 -4.000 447.000 639.000 1,807.000 860.000 1,206.000 262.026 2.670 ns -3.866 11.09
Local RMS Frequency Jitter 0.020 0.029 0.035 0.057 0.101 0.129 10.403 0.066 0.100 0.110 0.063 ppb 59.87 4318
Local RMS Time Jitter 72.000 108.000 126.000 180.000 254.000 290.000 2,243.000 128.000 182.000 45.202 183.924 ns 46.59 548
Server Jitter 104.131.155.175 0.000 0.253 0.389 2.217 10.015 13.604 66.989 9.626 13.351 3.921 3.539 ms 4.886 64.3
Server Jitter 162.159.200.1 0.000 0.199 0.309 1.762 9.397 14.638 246.678 9.087 14.439 7.668 3.326 ms 19.54 557.4
Server Jitter 164.67.62.194 0.000 0.212 0.348 1.797 9.866 13.962 211.824 9.518 13.750 6.381 3.334 ms 20.26 627.7
Server Jitter 173.11.101.155 0.000 0.349 0.650 2.090 10.245 17.065 246.881 9.596 16.715 8.434 3.848 ms 18.76 504.2
Server Jitter 178.62.68.79 0.000 0.308 0.566 3.039 10.639 33.720 62.554 10.073 33.411 5.815 4.678 ms 4.229 33.47
Server Jitter 192.168.1.10 0.000 0.019 0.035 0.143 8.653 9.420 155.428 8.618 9.401 3.630 1.268 ms 13.82 490.2
Server Jitter 203.123.48.219 0.000 0.278 0.460 2.321 10.625 16.422 109.041 10.165 16.144 5.479 4.046 ms 7.123 98.17
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.763 9.115 14.258 254.490 9.115 14.258 11.185 3.403 ms 18.01 403.4
Server Jitter 204.17.205.24 0.000 0.244 0.374 1.837 9.607 14.573 148.946 9.232 14.329 5.011 3.347 ms 12.91 347.6
Server Jitter 47.51.249.154 0.000 0.556 0.964 3.227 11.116 32.614 83.844 10.152 32.059 5.404 4.714 ms 5.516 53.45
Server Jitter SHM(0) 0.000 0.294 0.545 2.370 6.805 8.426 13.625 6.261 8.133 2.019 2.906 ms 2.316 6.018
Server Jitter SHM(1) 0.000 73.000 100.000 201.000 428.000 550.000 3,914.000 328.000 477.000 109.068 224.968 ns 8.188 103.2
Server Offset 104.131.155.175 -8.979 -5.288 -1.126 2.879 4.259 5.400 8.016 5.386 10.687 1.769 2.560 ms -1.002 8.025
Server Offset 162.159.200.1 -6.876 -5.667 -3.827 0.785 2.718 4.344 5.660 6.544 10.011 2.277 -0.092 ms -4.603 11.34
Server Offset 164.67.62.194 -0.716 2.208 2.433 2.771 3.290 3.727 5.459 0.856 1.519 0.308 2.802 ms 555.5 4718
Server Offset 173.11.101.155 -5.304 -1.730 -0.579 0.308 1.109 1.809 4.342 1.688 3.540 0.609 0.286 ms -2.644 17.1
Server Offset 178.62.68.79 -45.434 -5.374 0.654 5.716 10.151 13.139 17.047 9.497 18.513 3.926 5.398 ms -3.529 51.17
Server Offset 192.168.1.10 -109.598 -27.316 -2.795 87.432 140.288 148.746 223.583 143.083 176.062 46.979 79.220 µs 1.938 4.013
Server Offset 203.123.48.219 -8.961 -2.493 -2.131 -1.122 1.920 2.985 7.208 4.052 5.478 1.456 -0.556 ms -6.166 14.67
Server Offset 204.123.2.5 -4.160 1.878 2.299 2.654 3.361 5.224 27.878 1.062 3.346 1.052 2.765 ms 25.03 475.8
Server Offset 204.17.205.24 -1.196 1.291 1.568 2.016 3.005 3.635 11.438 1.437 2.344 0.546 2.105 ms 36.78 226.8
Server Offset 47.51.249.154 -5.908 1.902 2.546 3.392 5.727 6.432 8.631 3.181 4.530 0.891 3.548 ms 36.54 154.8
Server Offset SHM(0) -73.141 -66.939 -64.137 -56.053 -47.395 -45.307 -43.239 16.742 21.632 4.976 -56.012 ms -1878 2.348e+04
Server Offset SHM(1) -4,806.000 -569.000 -414.000 -5.000 448.000 641.000 2,141.000 862.000 1,210.000 263.570 2.770 ns -3.853 11.36
TDOP 0.530 0.550 0.600 0.820 1.260 1.630 1.770 0.660 1.080 0.218 0.862 35.66 145.8
Temp ZONE0 62.300 63.376 63.914 65.528 66.604 67.142 67.680 2.690 3.766 0.845 65.397 °C
nSats 6.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.113 9.397 nSat 434.7 3406
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!