NTPsec

C-ntpsec-3-hour-stats

Report generated: Sun Aug 18 20:03:58 2019 UTC
Start Time: Sun Aug 18 17:03:58 2019 UTC
End Time: Sun Aug 18 20:03:58 2019 UTC
Report published: Sun Aug 18 13:05:05 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 -806.000 -618.000 -369.000 81.000 615.000 979.000 1,289.000 984.000 1,597.000 313.034 97.531 ns -2.004 5.522
Local Clock Frequency Offset -8.065 -8.065 -8.065 -8.062 -8.053 -8.046 -8.046 0.0115 0.0188 0.0038 -8.062 ppm -9.521e+09 2.018e+13

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 121.000 130.000 147.000 211.000 323.000 360.000 394.000 176.000 230.000 53.097 218.050 ns 39.95 162

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 27.000 33.000 43.000 64.000 165.000 339.000 376.000 122.000 306.000 49.393 77.715 10e-12 5.441 27.53

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 -806.000 -618.000 -369.000 81.000 615.000 979.000 1,289.000 984.000 1,597.000 313.034 97.531 ns -2.004 5.522

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 -8.065 -8.065 -8.065 -8.062 -8.053 -8.046 -8.046 0.0115 0.0188 0.0038 -8.062 ppm -9.521e+09 2.018e+13
Temp ZONE0 57.458 57.458 57.996 57.996 58.534 58.534 58.534 0.538 1.076 0.205 58.056 °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 7.000 8.000 11.000 11.000 11.000 4.000 5.000 1.453 8.253 nSat 117.1 623.4
TDOP 0.590 0.590 0.620 0.850 1.460 2.040 5.370 0.840 1.450 0.439 1.006 11.71 97.64

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.172 -0.172 -0.172 1.903 3.323 3.323 3.323 3.495 3.495 1.046 1.852 ms 2.269 4.831

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 0.477 0.477 0.490 0.748 1.044 1.193 1.193 0.555 0.716 0.163 0.756 ms 59.81 265.3

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.455 2.455 2.540 2.786 2.961 2.995 2.995 0.421 0.540 0.127 2.764 ms 9127 1.916e+05

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.359 -0.359 -0.278 0.334 1.439 1.567 1.567 1.717 1.926 0.417 0.370 ms 0.5376 3.887

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 -20.072 -20.072 -6.163 2.453 9.309 9.321 9.321 15.472 29.393 5.785 1.562 ms -4.647 17.95

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 -116.941 -8.783 13.806 49.250 75.662 82.025 87.567 61.856 90.808 23.603 46.431 µs 1.372 14.33

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 1.004 1.004 1.083 1.904 2.625 3.236 3.236 1.542 2.232 0.527 1.761 ms 20.44 71.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 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 2.196 2.196 2.196 2.519 2.739 2.739 2.739 0.543 0.543 0.160 2.463 ms 2997 4.363e+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.281 1.281 1.319 1.762 1.998 2.068 2.068 0.679 0.787 0.194 1.739 ms 526.7 4369

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) -63.217 -63.202 -62.234 -52.454 -44.892 -42.525 -42.120 17.342 20.677 5.409 -52.906 ms -1286 1.422e+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) -807.000 -619.000 -370.000 82.000 616.000 980.000 1,290.000 986.000 1,599.000 313.744 97.746 ns -2.008 5.52

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 1.664 1.664 1.664 11.839 157.081 157.081 157.081 155.417 155.417 55.564 42.659 ms 0.3206 1.708

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.227 0.227 0.653 1.845 10.398 10.482 10.482 9.745 10.255 2.710 2.987 ms 1.888 5.306

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.340 0.340 0.408 1.666 6.410 6.439 6.439 6.002 6.099 1.607 1.853 ms 2.185 6.24

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 1.657 1.657 2.136 8.415 15.700 16.182 16.182 13.564 14.525 4.924 8.149 ms 2.348 4.544

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 178.62.68.79

peer jitter 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.62.68.79 0.000 0.000 0.000 2.653 20.867 23.539 23.539 20.867 23.539 6.540 5.761 ms 1.026 3.279

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.016 0.018 0.038 0.097 8.064 8.709 12.275 8.026 8.692 2.286 0.965 ms 0.998 6.179

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.300 0.300 0.413 2.731 11.037 11.881 11.881 10.623 11.582 3.581 4.004 ms 1.22 2.83

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 462.675 605.239 605.239 605.239 605.239 605.239 191.149 379.142 µs 3.316 6.587

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.203 0.203 0.277 1.613 6.551 8.735 8.735 6.273 8.531 2.020 2.004 ms 1.712 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 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.106 0.162 0.311 2.272 5.966 7.061 7.264 5.654 6.900 1.811 2.674 ms 2.06 4.609

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) 63.000 81.000 107.000 250.000 527.000 734.000 884.000 420.000 653.000 133.583 271.960 ns 5.357 17.04

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 -8.065 -8.065 -8.065 -8.062 -8.053 -8.046 -8.046 0.0115 0.0188 0.0038 -8.062 ppm -9.521e+09 2.018e+13
Local Clock Time Offset -806.000 -618.000 -369.000 81.000 615.000 979.000 1,289.000 984.000 1,597.000 313.034 97.531 ns -2.004 5.522
Local RMS Frequency Jitter 27.000 33.000 43.000 64.000 165.000 339.000 376.000 122.000 306.000 49.393 77.715 10e-12 5.441 27.53
Local RMS Time Jitter 121.000 130.000 147.000 211.000 323.000 360.000 394.000 176.000 230.000 53.097 218.050 ns 39.95 162
Server Jitter 104.131.155.175 1.664 1.664 1.664 11.839 157.081 157.081 157.081 155.417 155.417 55.564 42.659 ms 0.3206 1.708
Server Jitter 162.159.200.1 0.227 0.227 0.653 1.845 10.398 10.482 10.482 9.745 10.255 2.710 2.987 ms 1.888 5.306
Server Jitter 164.67.62.194 0.340 0.340 0.408 1.666 6.410 6.439 6.439 6.002 6.099 1.607 1.853 ms 2.185 6.24
Server Jitter 173.11.101.155 1.657 1.657 2.136 8.415 15.700 16.182 16.182 13.564 14.525 4.924 8.149 ms 2.348 4.544
Server Jitter 178.62.68.79 0.000 0.000 0.000 2.653 20.867 23.539 23.539 20.867 23.539 6.540 5.761 ms 1.026 3.279
Server Jitter 192.168.1.10 0.016 0.018 0.038 0.097 8.064 8.709 12.275 8.026 8.692 2.286 0.965 ms 0.998 6.179
Server Jitter 203.123.48.219 0.300 0.300 0.413 2.731 11.037 11.881 11.881 10.623 11.582 3.581 4.004 ms 1.22 2.83
Server Jitter 204.123.2.5 0.000 0.000 0.000 462.675 605.239 605.239 605.239 605.239 605.239 191.149 379.142 µs 3.316 6.587
Server Jitter 204.17.205.24 0.203 0.203 0.277 1.613 6.551 8.735 8.735 6.273 8.531 2.020 2.004 ms 1.712 5.554
Server Jitter SHM(0) 0.106 0.162 0.311 2.272 5.966 7.061 7.264 5.654 6.900 1.811 2.674 ms 2.06 4.609
Server Jitter SHM(1) 63.000 81.000 107.000 250.000 527.000 734.000 884.000 420.000 653.000 133.583 271.960 ns 5.357 17.04
Server Offset 104.131.155.175 -0.172 -0.172 -0.172 1.903 3.323 3.323 3.323 3.495 3.495 1.046 1.852 ms 2.269 4.831
Server Offset 162.159.200.1 0.477 0.477 0.490 0.748 1.044 1.193 1.193 0.555 0.716 0.163 0.756 ms 59.81 265.3
Server Offset 164.67.62.194 2.455 2.455 2.540 2.786 2.961 2.995 2.995 0.421 0.540 0.127 2.764 ms 9127 1.916e+05
Server Offset 173.11.101.155 -0.359 -0.359 -0.278 0.334 1.439 1.567 1.567 1.717 1.926 0.417 0.370 ms 0.5376 3.887
Server Offset 178.62.68.79 -20.072 -20.072 -6.163 2.453 9.309 9.321 9.321 15.472 29.393 5.785 1.562 ms -4.647 17.95
Server Offset 192.168.1.10 -116.941 -8.783 13.806 49.250 75.662 82.025 87.567 61.856 90.808 23.603 46.431 µs 1.372 14.33
Server Offset 203.123.48.219 1.004 1.004 1.083 1.904 2.625 3.236 3.236 1.542 2.232 0.527 1.761 ms 20.44 71.19
Server Offset 204.123.2.5 2.196 2.196 2.196 2.519 2.739 2.739 2.739 0.543 0.543 0.160 2.463 ms 2997 4.363e+04
Server Offset 204.17.205.24 1.281 1.281 1.319 1.762 1.998 2.068 2.068 0.679 0.787 0.194 1.739 ms 526.7 4369
Server Offset SHM(0) -63.217 -63.202 -62.234 -52.454 -44.892 -42.525 -42.120 17.342 20.677 5.409 -52.906 ms -1286 1.422e+04
Server Offset SHM(1) -807.000 -619.000 -370.000 82.000 616.000 980.000 1,290.000 986.000 1,599.000 313.744 97.746 ns -2.008 5.52
TDOP 0.590 0.590 0.620 0.850 1.460 2.040 5.370 0.840 1.450 0.439 1.006 11.71 97.64
Temp ZONE0 57.458 57.458 57.996 57.996 58.534 58.534 58.534 0.538 1.076 0.205 58.056 °C
nSats 5.000 6.000 7.000 8.000 11.000 11.000 11.000 4.000 5.000 1.453 8.253 nSat 117.1 623.4
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!