NTPsec

C-ntpsec-6-hour-stats

Report generated: Sun Aug 18 19:05:29 2019 UTC
Start Time: Sun Aug 18 13:05:28 2019 UTC
End Time: Sun Aug 18 19:05:28 2019 UTC
Report published: Sun Aug 18 12:06:37 2019 PDT
Report Period: 0.2 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 -1,062.000 -875.000 -653.000 -179.000 352.000 514.000 692.000 1,005.000 1,389.000 302.906 -165.841 ns -8.291 22.58
Local Clock Frequency Offset -8.065 -8.065 -8.065 -8.052 -8.011 -8.009 -8.009 0.053 0.056 0.0185 -8.046 ppm -8.229e+07 3.579e+10

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 95.000 117.000 137.000 198.000 326.000 364.000 420.000 189.000 247.000 57.985 210.260 ns 26.8 100.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 27.000 34.000 46.000 75.000 132.000 148.000 167.000 86.000 114.000 26.485 80.343 10e-12 15.16 50.13

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 -1,062.000 -875.000 -653.000 -179.000 352.000 514.000 692.000 1,005.000 1,389.000 302.906 -165.841 ns -8.291 22.58

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.052 -8.011 -8.009 -8.009 0.053 0.056 0.0185 -8.046 ppm -8.229e+07 3.579e+10
Temp ZONE0 57.458 57.458 57.996 57.996 58.534 59.072 59.072 0.538 1.614 0.309 58.168 °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.216 8.235 nSat 210 1325
TDOP 0.590 0.600 0.620 0.900 1.640 1.890 5.370 1.020 1.290 0.403 1.034 12.48 84.7

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.363 3.217 4.293 4.312 4.312 3.930 4.484 0.988 3.041 ms 13.89 38.64

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.490 0.490 0.590 1.343 1.714 1.849 1.849 1.125 1.359 0.370 1.214 ms 18.52 58.23

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.495 2.684 2.995 3.266 3.266 0.500 0.810 0.148 2.712 ms 5308 9.325e+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.458 -0.458 -0.147 0.191 0.622 1.567 1.567 0.769 2.025 0.299 0.220 ms 0.4637 6.759

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 -4.590 -4.590 -4.340 -1.994 5.251 22.783 22.783 9.591 27.372 4.557 -0.399 ms -1.696 10.69

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 -35.339 9.489 47.193 78.734 81.787 84.398 69.245 117.126 24.003 44.645 µs 1.625 9.708

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.776 2.264 3.236 3.236 1.182 2.232 0.435 1.707 ms 34.13 132.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.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 1.925 1.925 2.210 2.459 2.666 2.735 2.735 0.457 0.809 0.164 2.443 ms 2745 3.88e+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.188 1.188 1.436 1.819 2.107 2.322 2.322 0.671 1.134 0.213 1.785 ms 424 3290

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) -64.980 -63.760 -60.089 -52.364 -45.599 -44.714 -42.120 14.491 19.046 4.410 -52.207 ms -2156 2.819e+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) -1,063.000 -876.000 -654.000 -180.000 353.000 515.000 693.000 1,007.000 1,391.000 303.588 -166.231 ns -8.288 22.56

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.359 0.359 0.428 1.809 109.495 157.081 157.081 109.067 156.722 33.168 13.120 ms 1.284 7.042

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.157 0.157 0.264 1.384 5.896 10.163 10.163 5.632 10.007 2.251 2.303 ms 1.74 5.409

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.139 0.139 0.352 1.726 8.813 12.225 12.225 8.461 12.086 3.215 3.453 ms 1.083 2.668

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.331 0.331 0.447 2.887 15.700 24.033 24.033 15.253 23.702 5.900 6.339 ms 1.099 3.069

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.538 1.837 15.203 23.539 23.539 14.665 23.539 5.359 4.357 ms 1.134 4.094

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.015 0.020 0.029 0.110 8.566 11.498 12.275 8.537 11.478 2.695 1.381 ms 0.6703 4.249

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.188 0.188 0.262 1.980 12.054 12.343 12.343 11.793 12.155 3.676 3.364 ms 1.074 3.051

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.188 0.188 0.189 0.605 8.907 8.925 8.925 8.718 8.736 2.464 1.697 ms 1.079 3.94

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.248 8.420 16.248 16.248 8.142 16.045 3.111 2.477 ms 2.127 9.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 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.248 0.395 2.027 6.582 8.910 9.082 6.187 8.662 2.025 2.688 ms 1.943 5.003

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) 49.000 72.000 100.000 240.000 546.000 693.000 863.000 446.000 621.000 137.344 266.771 ns 4.817 14.93

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.052 -8.011 -8.009 -8.009 0.053 0.056 0.0185 -8.046 ppm -8.229e+07 3.579e+10
Local Clock Time Offset -1,062.000 -875.000 -653.000 -179.000 352.000 514.000 692.000 1,005.000 1,389.000 302.906 -165.841 ns -8.291 22.58
Local RMS Frequency Jitter 27.000 34.000 46.000 75.000 132.000 148.000 167.000 86.000 114.000 26.485 80.343 10e-12 15.16 50.13
Local RMS Time Jitter 95.000 117.000 137.000 198.000 326.000 364.000 420.000 189.000 247.000 57.985 210.260 ns 26.8 100.7
Server Jitter 104.131.155.175 0.359 0.359 0.428 1.809 109.495 157.081 157.081 109.067 156.722 33.168 13.120 ms 1.284 7.042
Server Jitter 162.159.200.1 0.157 0.157 0.264 1.384 5.896 10.163 10.163 5.632 10.007 2.251 2.303 ms 1.74 5.409
Server Jitter 164.67.62.194 0.139 0.139 0.352 1.726 8.813 12.225 12.225 8.461 12.086 3.215 3.453 ms 1.083 2.668
Server Jitter 173.11.101.155 0.331 0.331 0.447 2.887 15.700 24.033 24.033 15.253 23.702 5.900 6.339 ms 1.099 3.069
Server Jitter 178.62.68.79 0.000 0.000 0.538 1.837 15.203 23.539 23.539 14.665 23.539 5.359 4.357 ms 1.134 4.094
Server Jitter 192.168.1.10 0.015 0.020 0.029 0.110 8.566 11.498 12.275 8.537 11.478 2.695 1.381 ms 0.6703 4.249
Server Jitter 203.123.48.219 0.188 0.188 0.262 1.980 12.054 12.343 12.343 11.793 12.155 3.676 3.364 ms 1.074 3.051
Server Jitter 204.123.2.5 0.188 0.188 0.189 0.605 8.907 8.925 8.925 8.718 8.736 2.464 1.697 ms 1.079 3.94
Server Jitter 204.17.205.24 0.203 0.203 0.277 1.248 8.420 16.248 16.248 8.142 16.045 3.111 2.477 ms 2.127 9.6
Server Jitter SHM(0) 0.106 0.248 0.395 2.027 6.582 8.910 9.082 6.187 8.662 2.025 2.688 ms 1.943 5.003
Server Jitter SHM(1) 49.000 72.000 100.000 240.000 546.000 693.000 863.000 446.000 621.000 137.344 266.771 ns 4.817 14.93
Server Offset 104.131.155.175 -0.172 -0.172 0.363 3.217 4.293 4.312 4.312 3.930 4.484 0.988 3.041 ms 13.89 38.64
Server Offset 162.159.200.1 0.490 0.490 0.590 1.343 1.714 1.849 1.849 1.125 1.359 0.370 1.214 ms 18.52 58.23
Server Offset 164.67.62.194 2.455 2.455 2.495 2.684 2.995 3.266 3.266 0.500 0.810 0.148 2.712 ms 5308 9.325e+04
Server Offset 173.11.101.155 -0.458 -0.458 -0.147 0.191 0.622 1.567 1.567 0.769 2.025 0.299 0.220 ms 0.4637 6.759
Server Offset 178.62.68.79 -4.590 -4.590 -4.340 -1.994 5.251 22.783 22.783 9.591 27.372 4.557 -0.399 ms -1.696 10.69
Server Offset 192.168.1.10 -116.941 -35.339 9.489 47.193 78.734 81.787 84.398 69.245 117.126 24.003 44.645 µs 1.625 9.708
Server Offset 203.123.48.219 1.004 1.004 1.083 1.776 2.264 3.236 3.236 1.182 2.232 0.435 1.707 ms 34.13 132.6
Server Offset 204.123.2.5 1.925 1.925 2.210 2.459 2.666 2.735 2.735 0.457 0.809 0.164 2.443 ms 2745 3.88e+04
Server Offset 204.17.205.24 1.188 1.188 1.436 1.819 2.107 2.322 2.322 0.671 1.134 0.213 1.785 ms 424 3290
Server Offset SHM(0) -64.980 -63.760 -60.089 -52.364 -45.599 -44.714 -42.120 14.491 19.046 4.410 -52.207 ms -2156 2.819e+04
Server Offset SHM(1) -1,063.000 -876.000 -654.000 -180.000 353.000 515.000 693.000 1,007.000 1,391.000 303.588 -166.231 ns -8.288 22.56
TDOP 0.590 0.600 0.620 0.900 1.640 1.890 5.370 1.020 1.290 0.403 1.034 12.48 84.7
Temp ZONE0 57.458 57.458 57.996 57.996 58.534 59.072 59.072 0.538 1.614 0.309 58.168 °C
nSats 5.000 6.000 7.000 8.000 11.000 11.000 11.000 4.000 5.000 1.216 8.235 nSat 210 1325
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!