NTPsec

C-ntpsec-1-hour-stats

Report generated: Wed Oct 23 21:02:39 2019 UTC
Start Time: Wed Oct 23 20:02:10 2019 UTC
End Time: Wed Oct 23 21:02:38 2019 UTC
Report published: Wed Oct 23 14:03:51 2019 PDT
Report Period: 0.0 days

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -621.000 -582.000 -447.000 -107.000 392.000 530.000 795.000 839.000 1,112.000 249.758 -71.178 ns -5.444 13.19
Local Clock Frequency Offset -7.196 -7.196 -7.196 -7.194 -7.192 -7.191 -7.191 0.0045 0.0049 0.0015 -7.194 ppm -1.02e+11 4.769e+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 131.000 135.000 151.000 205.000 269.000 276.000 283.000 118.000 141.000 35.722 206.124 ns 123 658.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 40.000 41.000 44.000 58.000 92.000 105.000 107.000 48.000 64.000 14.877 61.533 10e-12 41.31 172.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 -621.000 -582.000 -447.000 -107.000 392.000 530.000 795.000 839.000 1,112.000 249.758 -71.178 ns -5.444 13.19

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 -7.196 -7.196 -7.196 -7.194 -7.192 -7.191 -7.191 0.0045 0.0049 0.0015 -7.194 ppm -1.02e+11 4.769e+14
Temp ZONE0 63.376 63.376 63.376 63.914 64.452 64.990 64.990 1.076 1.614 0.432 64.040 °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 9.000 9.000 10.000 11.000 12.000 12.000 12.000 2.000 3.000 0.774 11.033 nSat 2369 3.193e+04
TDOP 0.570 0.570 0.580 0.630 0.860 0.980 0.980 0.280 0.410 0.097 0.662 215.2 1379

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 2.733 2.733 2.733 3.175 6.187 6.187 6.187 3.454 3.454 0.894 3.497 ms 35.86 158.4

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 -272.198 -272.198 -272.198 307.222 633.390 633.390 633.390 905.588 905.588 281.853 266.705 µs -0.6686 2.396

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 2.506 2.506 2.506 2.905 3.230 3.230 3.230 0.725 0.725 0.183 2.911 ms 3350 5.057e+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 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 0.119 0.119 0.119 0.610 1.341 1.341 1.341 1.222 1.222 0.401 0.618 ms 2.179 4.675

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

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

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

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



Server Offset 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 2.700 2.700 2.700 7.951 7.951 7.951 7.951 5.251 5.251 2.626 5.326 ms 4.173 8.464

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 43.472 43.472 146.954 275.867 383.433 509.129 509.129 236.479 465.657 76.704 273.694 µs 24.64 88.21

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 4.894 4.894 4.894 5.495 6.528 6.528 6.528 1.634 1.634 0.502 5.593 ms 1075 1.123e+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 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.590 1.590 1.590 2.053 2.872 2.872 2.872 1.281 1.281 0.332 2.101 ms 168.1 998.4

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) -67.792 -67.792 -66.869 -61.673 -55.609 -55.469 -55.469 11.260 12.323 3.903 -60.918 ms -4631 7.775e+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 -583.000 -448.000 -108.000 393.000 531.000 796.000 841.000 1,114.000 250.501 -71.489 ns -5.447 13.19

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 2.261 2.261 2.261 7.841 11.691 11.691 11.691 9.430 9.430 3.515 6.421 ms 3.164 6.412

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.634 0.634 0.634 1.923 9.591 9.591 9.591 8.957 8.957 3.559 4.140 ms 1.1 2.092

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.665 0.665 0.665 1.831 9.826 9.826 9.826 9.161 9.161 2.810 2.872 ms 1.85 4.661

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.473 0.473 0.473 5.140 16.836 16.836 16.836 16.362 16.362 6.818 7.807 ms 0.7886 1.646

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 2.341 2.341 2.341 4.038 4.038 4.038 4.038 1.698 1.698 0.849 3.189 ms 29.25 104.5

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.151 0.151 0.182 0.454 4.203 5.808 5.808 4.022 5.657 1.378 1.022 ms 1.593 5.554

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 1.237 1.237 1.237 2.317 4.057 4.057 4.057 2.820 2.820 0.775 2.284 ms 13.92 45.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.



Server Jitter 204.17.205.24

peer jitter 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.24 1.058 1.058 1.058 3.220 6.633 6.633 6.633 5.575 5.575 1.810 3.376 ms 3.893 9.517

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.907 0.907 1.044 3.223 6.976 7.402 7.402 5.932 6.495 1.802 3.500 ms 4.163 10.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 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) 83.000 93.000 117.000 231.000 477.000 669.000 708.000 360.000 576.000 115.285 260.058 ns 7.239 25.31

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 -7.196 -7.196 -7.196 -7.194 -7.192 -7.191 -7.191 0.0045 0.0049 0.0015 -7.194 ppm -1.02e+11 4.769e+14
Local Clock Time Offset -621.000 -582.000 -447.000 -107.000 392.000 530.000 795.000 839.000 1,112.000 249.758 -71.178 ns -5.444 13.19
Local RMS Frequency Jitter 40.000 41.000 44.000 58.000 92.000 105.000 107.000 48.000 64.000 14.877 61.533 10e-12 41.31 172.6
Local RMS Time Jitter 131.000 135.000 151.000 205.000 269.000 276.000 283.000 118.000 141.000 35.722 206.124 ns 123 658.8
Server Jitter 104.131.155.175 2.261 2.261 2.261 7.841 11.691 11.691 11.691 9.430 9.430 3.515 6.421 ms 3.164 6.412
Server Jitter 162.159.200.1 0.634 0.634 0.634 1.923 9.591 9.591 9.591 8.957 8.957 3.559 4.140 ms 1.1 2.092
Server Jitter 164.67.62.194 0.665 0.665 0.665 1.831 9.826 9.826 9.826 9.161 9.161 2.810 2.872 ms 1.85 4.661
Server Jitter 173.11.101.155 0.473 0.473 0.473 5.140 16.836 16.836 16.836 16.362 16.362 6.818 7.807 ms 0.7886 1.646
Server Jitter 178.62.68.79 2.341 2.341 2.341 4.038 4.038 4.038 4.038 1.698 1.698 0.849 3.189 ms 29.25 104.5
Server Jitter 192.168.1.10 0.151 0.151 0.182 0.454 4.203 5.808 5.808 4.022 5.657 1.378 1.022 ms 1.593 5.554
Server Jitter 203.123.48.219 1.237 1.237 1.237 2.317 4.057 4.057 4.057 2.820 2.820 0.775 2.284 ms 13.92 45.36
Server Jitter 204.17.205.24 1.058 1.058 1.058 3.220 6.633 6.633 6.633 5.575 5.575 1.810 3.376 ms 3.893 9.517
Server Jitter SHM(0) 0.907 0.907 1.044 3.223 6.976 7.402 7.402 5.932 6.495 1.802 3.500 ms 4.163 10.21
Server Jitter SHM(1) 83.000 93.000 117.000 231.000 477.000 669.000 708.000 360.000 576.000 115.285 260.058 ns 7.239 25.31
Server Offset 104.131.155.175 2.733 2.733 2.733 3.175 6.187 6.187 6.187 3.454 3.454 0.894 3.497 ms 35.86 158.4
Server Offset 162.159.200.1 -272.198 -272.198 -272.198 307.222 633.390 633.390 633.390 905.588 905.588 281.853 266.705 µs -0.6686 2.396
Server Offset 164.67.62.194 2.506 2.506 2.506 2.905 3.230 3.230 3.230 0.725 0.725 0.183 2.911 ms 3350 5.057e+04
Server Offset 173.11.101.155 0.119 0.119 0.119 0.610 1.341 1.341 1.341 1.222 1.222 0.401 0.618 ms 2.179 4.675
Server Offset 178.62.68.79 2.700 2.700 2.700 7.951 7.951 7.951 7.951 5.251 5.251 2.626 5.326 ms 4.173 8.464
Server Offset 192.168.1.10 43.472 43.472 146.954 275.867 383.433 509.129 509.129 236.479 465.657 76.704 273.694 µs 24.64 88.21
Server Offset 203.123.48.219 4.894 4.894 4.894 5.495 6.528 6.528 6.528 1.634 1.634 0.502 5.593 ms 1075 1.123e+04
Server Offset 204.17.205.24 1.590 1.590 1.590 2.053 2.872 2.872 2.872 1.281 1.281 0.332 2.101 ms 168.1 998.4
Server Offset SHM(0) -67.792 -67.792 -66.869 -61.673 -55.609 -55.469 -55.469 11.260 12.323 3.903 -60.918 ms -4631 7.775e+04
Server Offset SHM(1) -622.000 -583.000 -448.000 -108.000 393.000 531.000 796.000 841.000 1,114.000 250.501 -71.489 ns -5.447 13.19
TDOP 0.570 0.570 0.580 0.630 0.860 0.980 0.980 0.280 0.410 0.097 0.662 215.2 1379
Temp ZONE0 63.376 63.376 63.376 63.914 64.452 64.990 64.990 1.076 1.614 0.432 64.040 °C
nSats 9.000 9.000 10.000 11.000 12.000 12.000 12.000 2.000 3.000 0.774 11.033 nSat 2369 3.193e+04
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!