NTPsec

B-ntpsec-1-hour-stats

Report generated: Sun Aug 18 19:02:16 2019 UTC
Start Time: Sun Aug 18 18:01:46 2019 UTC
End Time: Sun Aug 18 19:02:14 2019 UTC
Report published: Sun Aug 18 12:02:24 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 -572.000 -495.000 -347.000 103.000 505.000 541.000 804.000 852.000 1,036.000 260.259 94.473 ns -2.324 5.438
Local Clock Frequency Offset -5.767 -5.767 -5.767 -5.766 -5.762 -5.761 -5.761 0.0047 0.0055 0.0014 -5.765 ppm -6.344e+10 2.53e+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 132.000 156.000 250.000 372.000 438.000 470.000 216.000 306.000 62.789 254.243 ns 38.14 153.7

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 35.000 37.000 42.000 62.000 93.000 101.000 110.000 51.000 64.000 16.250 63.677 10e-12 34.1 131.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 -495.000 -347.000 103.000 505.000 541.000 804.000 852.000 1,036.000 260.259 94.473 ns -2.324 5.438

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.767 -5.767 -5.767 -5.766 -5.762 -5.761 -5.761 0.0047 0.0055 0.0014 -5.765 ppm -6.344e+10 2.53e+14
Temp ZONE0 58.534 58.534 59.072 59.072 59.610 60.148 60.148 0.538 1.614 0.268 59.144 °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 7.000 8.000 8.000 1.000 2.000 0.381 6.951 nSat 5181 9.022e+04
TDOP 0.830 0.830 1.030 1.280 1.580 1.600 1.600 0.550 0.770 0.162 1.265 332.8 2398

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.273 1.857 2.303 2.303 2.303 2.576 2.576 0.874 1.553 ms 1.625 3.207

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 2.216 2.216 2.216 2.367 2.425 2.425 2.425 0.209 0.209 0.076 2.337 ms 2.611e+04 7.764e+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 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.263 2.263 2.263 2.482 3.016 3.016 3.016 0.752 0.752 0.220 2.516 ms 1176 1.266e+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 0.579 0.579 0.579 3.429 7.189 7.189 7.189 6.611 6.611 1.755 3.437 ms 4.155 10.54

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 -28.788 -1.076 43.046 75.050 78.744 78.744 76.126 107.532 23.187 41.227 µs 2.233 5.322

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.666 1.072 1.495 1.495 1.495 0.829 0.829 0.236 1.123 ms 64.56 287.6

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.353 1.353 1.353 1.770 2.017 2.017 2.017 0.664 0.664 0.185 1.755 ms 635.6 5594

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.079 2.530 2.946 2.946 2.946 0.867 0.867 0.191 2.523 ms 1858 2.314e+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 -3.584 -0.325 0.717 0.717 0.717 4.302 4.302 1.166 -0.785 ms -10.84 35.71

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.817 -97.652 -92.036 -81.132 -71.664 -68.653 -64.822 20.372 29.000 6.375 -81.359 ms -2648 3.701e+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 -496.000 -348.000 104.000 506.000 542.000 805.000 854.000 1,038.000 261.013 94.761 ns -2.326 5.437

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.627 0.627 0.627 2.218 118.745 118.745 118.745 118.118 118.118 34.693 14.952 ms 0.7483 4.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 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 1.208 1.208 1.208 6.334 8.923 8.923 8.923 7.715 7.715 3.270 4.491 ms 1.395 2.487

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.377 0.377 0.377 1.179 2.996 2.996 2.996 2.619 2.619 0.849 1.456 ms 3.056 6.802

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.913 0.913 0.913 7.668 10.155 10.155 10.155 9.242 9.242 3.208 5.961 ms 2.855 5.396

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.035 0.263 8.699 24.522 24.522 8.664 24.509 4.363 3.004 ms 1.365 8.791

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.612 0.612 0.612 1.362 9.501 9.501 9.501 8.889 8.889 2.654 2.686 ms 1.55 4.07

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.350 0.350 0.350 2.261 10.798 10.798 10.798 10.448 10.448 2.884 2.724 ms 1.715 5.358

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.371 0.371 0.371 0.752 5.590 5.590 5.590 5.218 5.218 1.928 1.717 ms 0.9717 2.512

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 2.474 2.474 2.474 16.840 32.474 32.474 32.474 30.000 30.000 11.498 17.064 ms 1.606 2.988

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.722 2.771 3.842 7.194 13.425 16.409 23.213 9.583 13.638 2.904 7.789 ms 10.77 35.88

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) 94.000 103.000 132.000 240.000 450.000 546.000 600.000 318.000 443.000 98.855 262.084 ns 10.27 32.66

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.767 -5.767 -5.767 -5.766 -5.762 -5.761 -5.761 0.0047 0.0055 0.0014 -5.765 ppm -6.344e+10 2.53e+14
Local Clock Time Offset -572.000 -495.000 -347.000 103.000 505.000 541.000 804.000 852.000 1,036.000 260.259 94.473 ns -2.324 5.438
Local RMS Frequency Jitter 35.000 37.000 42.000 62.000 93.000 101.000 110.000 51.000 64.000 16.250 63.677 10e-12 34.1 131.6
Local RMS Time Jitter 123.000 132.000 156.000 250.000 372.000 438.000 470.000 216.000 306.000 62.789 254.243 ns 38.14 153.7
Server Jitter 104.131.155.175 0.627 0.627 0.627 2.218 118.745 118.745 118.745 118.118 118.118 34.693 14.952 ms 0.7483 4.065
Server Jitter 162.213.2.253 1.208 1.208 1.208 6.334 8.923 8.923 8.923 7.715 7.715 3.270 4.491 ms 1.395 2.487
Server Jitter 169.229.128.134 0.377 0.377 0.377 1.179 2.996 2.996 2.996 2.619 2.619 0.849 1.456 ms 3.056 6.802
Server Jitter 178.62.68.79 0.913 0.913 0.913 7.668 10.155 10.155 10.155 9.242 9.242 3.208 5.961 ms 2.855 5.396
Server Jitter 192.168.1.10 0.013 0.013 0.035 0.263 8.699 24.522 24.522 8.664 24.509 4.363 3.004 ms 1.365 8.791
Server Jitter 203.123.48.219 0.612 0.612 0.612 1.362 9.501 9.501 9.501 8.889 8.889 2.654 2.686 ms 1.55 4.07
Server Jitter 204.17.205.24 0.350 0.350 0.350 2.261 10.798 10.798 10.798 10.448 10.448 2.884 2.724 ms 1.715 5.358
Server Jitter 66.220.9.122 0.371 0.371 0.371 0.752 5.590 5.590 5.590 5.218 5.218 1.928 1.717 ms 0.9717 2.512
Server Jitter 76.14.161.109 2.474 2.474 2.474 16.840 32.474 32.474 32.474 30.000 30.000 11.498 17.064 ms 1.606 2.988
Server Jitter SHM(0) 1.722 2.771 3.842 7.194 13.425 16.409 23.213 9.583 13.638 2.904 7.789 ms 10.77 35.88
Server Jitter SHM(1) 94.000 103.000 132.000 240.000 450.000 546.000 600.000 318.000 443.000 98.855 262.084 ns 10.27 32.66
Server Offset 104.131.155.175 -0.273 -0.273 -0.273 1.857 2.303 2.303 2.303 2.576 2.576 0.874 1.553 ms 1.625 3.207
Server Offset 162.213.2.253 2.216 2.216 2.216 2.367 2.425 2.425 2.425 0.209 0.209 0.076 2.337 ms 2.611e+04 7.764e+05
Server Offset 169.229.128.134 2.263 2.263 2.263 2.482 3.016 3.016 3.016 0.752 0.752 0.220 2.516 ms 1176 1.266e+04
Server Offset 178.62.68.79 0.579 0.579 0.579 3.429 7.189 7.189 7.189 6.611 6.611 1.755 3.437 ms 4.155 10.54
Server Offset 192.168.1.10 -28.788 -28.788 -1.076 43.046 75.050 78.744 78.744 76.126 107.532 23.187 41.227 µs 2.233 5.322
Server Offset 203.123.48.219 0.666 0.666 0.666 1.072 1.495 1.495 1.495 0.829 0.829 0.236 1.123 ms 64.56 287.6
Server Offset 204.17.205.24 1.353 1.353 1.353 1.770 2.017 2.017 2.017 0.664 0.664 0.185 1.755 ms 635.6 5594
Server Offset 66.220.9.122 2.079 2.079 2.079 2.530 2.946 2.946 2.946 0.867 0.867 0.191 2.523 ms 1858 2.314e+04
Server Offset 76.14.161.109 -3.584 -3.584 -3.584 -0.325 0.717 0.717 0.717 4.302 4.302 1.166 -0.785 ms -10.84 35.71
Server Offset SHM(0) -104.817 -97.652 -92.036 -81.132 -71.664 -68.653 -64.822 20.372 29.000 6.375 -81.359 ms -2648 3.701e+04
Server Offset SHM(1) -573.000 -496.000 -348.000 104.000 506.000 542.000 805.000 854.000 1,038.000 261.013 94.761 ns -2.326 5.437
TDOP 0.830 0.830 1.030 1.280 1.580 1.600 1.600 0.550 0.770 0.162 1.265 332.8 2398
Temp ZONE0 58.534 58.534 59.072 59.072 59.610 60.148 60.148 0.538 1.614 0.268 59.144 °C
nSats 6.000 6.000 6.000 7.000 7.000 8.000 8.000 1.000 2.000 0.381 6.951 nSat 5181 9.022e+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!