NTPsec

Dell-2018

Report generated: Sun Oct 25 00:40:05 2026 UTC
Start Time: Sun Sep 20 00:40:03 2026 UTC
End Time: Sun Oct 25 00:40:03 2026 UTC
Report Period: 35.0 days

Stats for the last 1, 7, 35, 98, 371, some days, or live gps data.

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 -64.349 -0.769 -0.405 -0.001 0.413 0.754 21.088 0.817 1.523 0.780 0.007 ms -23.37 2511
Local Clock Frequency Offset 8.355 10.613 10.715 11.157 13.026 13.212 14.029 2.311 2.600 0.616 11.307 ppm 1.901 6.433

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 0.000 0.175 0.240 0.352 0.508 2.974 27.265 0.268 2.800 0.750 0.436 ms 18.51 492.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 0.000 3.592 4.878 6.941 11.606 173.266 950.123 6.728 169.674 39.803 11.635 ppb 12.92 207.7

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 -64.349 -0.769 -0.405 -0.001 0.413 0.754 21.088 0.817 1.523 0.780 0.007 ms -23.37 2511

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.355 10.613 10.715 11.157 13.026 13.212 14.029 2.311 2.600 0.616 11.307 ppm 1.901 6.433
Temp /dev/sda 18.000 20.000 20.000 25.000 26.000 28.000 34.000 6.000 8.000 2.334 24.211 °C
Temp LM0 27.000 28.000 30.000 34.000 40.000 43.000 53.000 10.000 15.000 2.982 34.018 °C
Temp LM1 27.000 28.000 29.000 36.000 41.000 42.000 47.000 12.000 14.000 4.034 35.174 °C
Temp LM2 0.000 0.000 19.000 32.000 45.000 47.000 48.000 26.000 47.000 10.478 28.457 °C
Temp LM3 0.000 0.000 19.000 31.000 47.000 48.000 50.000 28.000 48.000 8.167 31.486 °C
Temp LM4 0.000 0.000 0.000 33.000 47.000 48.000 55.000 47.000 48.000 14.932 27.280 °C
Temp LM5 27.000 28.000 29.000 33.000 47.000 48.000 50.000 18.000 20.000 4.683 34.266 °C
Temp LM6 0.000 30.000 31.000 34.000 44.000 45.000 45.000 13.000 15.000 3.376 35.030 °C
Temp LM7 0.000 0.000 19.000 34.000 44.000 46.000 56.000 25.000 46.000 8.239 32.810 °C
Temp LM8 27.000 28.000 28.000 32.000 40.000 41.000 47.000 12.000 13.000 3.508 32.804 °C
Temp LM9 31.000 31.000 32.000 35.000 47.000 48.000 50.000 15.000 17.000 3.643 35.725 °C
Temp ZONE0 20.000 20.000 20.000 20.000 20.000 20.000 20.000 0.000 0.000 0.000 20.000 °C
Temp ZONE1 30.000 31.000 32.000 34.000 47.000 48.000 50.000 15.000 17.000 3.773 35.070 °C
Temp ZONE2 27.000 27.000 28.000 30.000 41.000 42.000 43.000 13.000 15.000 3.725 31.382 °C
Temp ZONE3 30.000 31.000 32.000 34.000 47.000 48.000 51.000 15.000 17.000 3.772 35.083 °C
Temp ZONE4 30.000 31.000 32.000 34.000 47.000 48.000 50.000 15.000 17.000 3.773 35.070 °C
Temp ZONE5 29.000 31.000 32.000 35.000 44.000 47.000 56.000 12.000 16.000 4.121 36.286 °C
Temp ZONE6 27.000 27.000 28.000 30.000 40.000 41.000 43.000 12.000 14.000 3.058 31.077 °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 8.000 8.000 9.000 11.000 17.000 19.000 20.000 8.000 11.000 2.402 11.977 nSat 1.224 4.096
TDOP 0.480 0.540 0.600 0.850 1.280 1.640 2.920 0.680 1.100 0.250 0.889 2.238 15.04

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. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



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

peer offset 104.207.148.118 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.207.148.118 -11.999 -5.604 -0.209 4.792 7.585 13.740 17.586 7.794 19.344 2.874 4.340 ms -0.5466 8.692

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 104.232.0.123

peer offset 104.232.0.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.232.0.123 2.639 2.639 2.639 4.841 7.033 7.033 7.033 4.394 4.394 1.310 4.792 ms 0.1249 2.376

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 108.61.215.221

peer offset 108.61.215.221 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 108.61.215.221 -26.608 -2.493 1.820 6.633 10.271 12.393 24.349 8.451 14.886 3.256 6.369 ms -1.578 22.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 134.215.155.177

peer offset 134.215.155.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 134.215.155.177 -8.187 -8.187 -5.536 -1.522 4.849 10.577 10.577 10.385 18.764 3.047 -0.997 ms 1.041 5.461

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 136.243.177.133

peer offset 136.243.177.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 136.243.177.133 7.703 7.703 7.703 9.843 13.947 13.947 13.947 6.244 6.244 2.291 10.391 ms 0.5115 1.634

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 136.244.88.170

peer offset 136.244.88.170 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 136.244.88.170 -31.789 -31.789 -20.842 0.045 4.000 10.603 10.603 24.842 42.393 7.703 -2.888 ms -1.676 6.132

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 142.248.80.92

peer offset 142.248.80.92 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 142.248.80.92 -19.763 -7.670 0.151 7.998 11.634 12.986 21.215 11.482 20.656 4.630 6.869 ms -1.892 11.84

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 144.202.0.197

peer offset 144.202.0.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.202.0.197 -3.748 -3.338 -2.473 1.606 4.141 4.997 7.488 6.614 8.335 2.063 1.221 ms -0.3413 2.722

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 144.202.41.38

peer offset 144.202.41.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.202.41.38 -12.773 -12.773 -12.773 9.932 20.588 20.588 20.588 33.361 33.361 7.001 9.181 ms -1.843 7.452

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 144.202.66.214

peer offset 144.202.66.214 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.202.66.214 2.075 4.000 5.208 8.650 11.148 15.751 16.968 5.940 11.752 1.921 8.563 ms 0.4606 6.066

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 144.76.66.157

peer offset 144.76.66.157 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.76.66.157 -3.402 -3.402 -3.402 -0.816 3.576 3.576 3.576 6.977 6.977 2.655 -0.287 ms 0.3401 1.604

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 144.91.126.59

peer offset 144.91.126.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.91.126.59 -6.438 -6.438 -6.438 10.861 13.635 13.635 13.635 20.073 20.073 7.448 7.058 ms -1.052 2.293

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 147.88.195.53

peer offset 147.88.195.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 147.88.195.53 -34.267 -34.267 -27.801 -4.838 -2.374 -1.503 -1.503 25.427 32.764 8.607 -9.321 ms -1.287 3.331

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 149.28.200.179

peer offset 149.28.200.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.28.200.179 -1.566 -1.566 -1.566 0.261 3.397 3.397 3.397 4.963 4.963 1.890 0.322 ms 0.7746 2.031

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 149.28.61.105

peer offset 149.28.61.105 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.28.61.105 -2.893 -1.393 0.166 4.255 6.538 7.580 9.416 6.371 8.973 1.954 3.877 ms -0.6158 3.314

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 158.51.99.19

peer offset 158.51.99.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 158.51.99.19 -1.962 -1.069 0.074 3.420 5.765 9.486 24.445 5.691 10.555 2.496 3.403 ms 3.821 32.72

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 159.203.158.197

peer offset 159.203.158.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 159.203.158.197 -3.409 -2.313 0.649 5.552 7.905 8.880 9.205 7.257 11.193 2.163 5.248 ms -1.443 6.054

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 -2.180 -0.794 1.356 5.450 7.723 9.037 10.729 6.367 9.831 1.971 5.054 ms -0.7465 4.059

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

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 -3.559 -2.720 -0.675 5.966 8.671 11.944 16.947 9.345 14.663 3.024 5.157 ms -0.4234 4.78

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

peer offset 162.244.81.139 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.244.81.139 -3.970 -2.402 -1.700 2.667 5.309 6.320 11.561 7.009 8.722 2.227 2.397 ms -0.01836 4.144

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

peer offset 162.254.225.151 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.254.225.151 -17.956 -15.060 -5.708 10.223 16.437 18.274 18.494 22.145 33.334 6.977 8.368 ms -1.195 4.441

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

peer offset 162.254.225.152 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.254.225.152 -1.848 -1.848 -1.848 11.984 17.922 17.922 17.922 19.770 19.770 5.527 10.638 ms -0.901 3.021

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 163.123.153.14

peer offset 163.123.153.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 163.123.153.14 -9.441 -9.441 -3.988 -0.222 4.125 5.456 5.456 8.113 14.896 2.500 -0.368 ms -0.3748 4.801

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 167.248.62.201

peer offset 167.248.62.201 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 167.248.62.201 -36.149 -8.871 -0.418 3.596 6.839 9.001 13.433 7.257 17.872 3.422 3.176 ms -4.087 36.12

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 172.104.28.175

peer offset 172.104.28.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.104.28.175 -1.388 -1.388 -1.388 -0.100 3.196 3.196 3.196 4.583 4.583 1.717 0.342 ms 0.8717 2.171

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 172.232.209.103

peer offset 172.232.209.103 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.232.209.103 7.280 7.280 7.280 9.577 13.556 13.556 13.556 6.276 6.276 2.021 9.583 ms 0.9553 2.817

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 172.232.63.219

peer offset 172.232.63.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.232.63.219 -33.437 -20.344 -9.115 1.011 5.236 14.138 34.749 14.352 34.482 5.453 0.236 ms -1.079 12.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 172.233.157.223

peer offset 172.233.157.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.157.223 -34.981 -2.753 -0.971 2.731 12.580 18.256 52.964 13.551 21.009 5.455 3.422 ms 2.119 35.98

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 172.233.189.68

peer offset 172.233.189.68 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.189.68 0.880 1.706 3.867 9.537 14.514 16.678 17.957 10.647 14.973 3.031 9.281 ms -0.08943 3.421

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 172.234.25.10

peer offset 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.25.10 -42.533 -3.456 -1.823 1.877 6.389 11.586 22.519 8.212 15.042 3.478 1.908 ms -2.539 54.07

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 172.234.37.140

peer offset 172.234.37.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.37.140 -13.004 -13.004 -13.004 7.334 32.827 32.827 32.827 45.831 45.831 10.439 7.833 ms 0.5743 4.875

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 172.234.44.141

peer offset 172.234.44.141 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.44.141 0.161 0.258 1.885 5.464 8.767 13.230 14.363 6.882 12.971 2.446 5.617 ms 0.7521 4.851

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 172.235.154.118

peer offset 172.235.154.118 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.235.154.118 -1.805 0.077 3.315 7.192 10.233 14.821 16.912 6.918 14.744 2.413 7.174 ms 0.02952 5.667

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 172.237.147.185

peer offset 172.237.147.185 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.237.147.185 -200.621 -7.616 -0.855 3.793 6.883 15.346 16.593 7.738 22.962 13.165 2.907 ms -14.59 225.8

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

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

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

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



Server Offset 173.71.69.149

peer offset 173.71.69.149 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.71.69.149 -32.631 -23.065 -3.051 1.666 5.159 6.822 7.925 8.210 29.887 4.482 1.127 ms -4.836 34.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 176.120.96.12

peer offset 176.120.96.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 176.120.96.12 7.763 7.763 7.763 10.322 13.850 13.850 13.850 6.087 6.087 2.060 10.546 ms 0.374 1.845

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 191.96.11.19

peer offset 191.96.11.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 191.96.11.19 -33.510 -27.663 -8.237 5.810 9.079 11.474 12.362 17.316 39.137 6.694 3.626 ms -2.763 13.45

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

peer offset 192.207.55.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.207.55.254 -68.913 -55.256 -6.572 0.132 6.972 15.177 22.208 13.544 70.432 8.299 -0.601 ms -5.484 44.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 192.231.84.117

peer offset 192.231.84.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.231.84.117 -2.391 -2.391 1.478 4.260 7.283 65.926 65.926 5.805 68.317 9.116 5.351 ms 6.221 41.5

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

peer offset 192.231.84.118 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.231.84.118 -1.548 -1.548 -1.131 1.669 6.088 12.258 12.258 7.219 13.806 2.297 1.986 ms 1.634 8.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 193.25.222.136

peer offset 193.25.222.136 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 193.25.222.136 -161.067 -64.510 -18.201 3.404 7.219 8.835 9.217 25.420 73.346 18.068 -0.427 ms -7.05 59.63

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 193.42.63.23

peer offset 193.42.63.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 193.42.63.23 -59.983 -23.546 -9.466 6.724 9.953 10.570 11.591 19.419 34.116 8.626 3.718 ms -3.942 25.7

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 194.0.5.123

peer offset 194.0.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.0.5.123 -26.416 -11.770 -5.483 2.355 11.459 224.213 227.738 16.943 235.983 30.653 6.323 ms 6.815 48.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 198.137.202.56

peer offset 198.137.202.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.137.202.56 -2.919 -2.236 -1.431 1.589 4.673 6.062 6.088 6.105 8.298 1.933 1.473 ms 0.1306 2.384

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 198.206.187.98

peer offset 198.206.187.98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.206.187.98 -51.757 -51.757 -51.757 -48.763 -19.447 -19.447 -19.447 32.310 32.310 11.963 -43.169 ms 1.436 3.168

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 207.244.103.95

peer offset 207.244.103.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 207.244.103.95 -7.124 -7.124 0.999 10.585 17.648 18.445 18.445 16.649 25.569 4.483 9.686 ms -1.342 6.812

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 208.70.148.101

peer offset 208.70.148.101 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 208.70.148.101 -8.831 -5.331 1.105 5.436 7.602 18.582 380.175 6.497 23.913 25.124 6.732 ms 14.5 213.9

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 209.177.158.85

peer offset 209.177.158.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.177.158.85 -3.024 -3.024 -3.024 1.651 3.804 3.804 3.804 6.827 6.827 2.492 0.610 ms -0.2339 1.812

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 209.205.228.50

peer offset 209.205.228.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.205.228.50 7.010 7.010 7.010 18.187 24.067 24.067 24.067 17.057 17.057 5.704 16.869 ms -0.6241 2.005

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 209.51.161.238

peer offset 209.51.161.238 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.51.161.238 -153.422 -127.019 -23.151 0.591 8.422 219.405 221.766 31.573 346.425 38.719 1.412 ms 3.117 25.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 213.108.170.26

peer offset 213.108.170.26 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 213.108.170.26 -4.269 -4.269 -4.269 -1.792 2.919 2.919 2.919 7.189 7.189 2.884 -0.922 ms 0.2241 1.32

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 216.144.228.179

peer offset 216.144.228.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.144.228.179 4.214 4.214 4.214 6.167 6.167 6.167 6.167 1.952 1.952 0.976 5.191 ms 0 1

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

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

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

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



Server Offset 216.229.4.66

peer offset 216.229.4.66 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.229.4.66 -2.093 -2.093 -0.203 4.137 5.998 10.083 10.083 6.201 12.176 2.006 3.911 ms -0.6222 4.429

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 216.250.115.174

peer offset 216.250.115.174 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.250.115.174 -27.840 -23.835 -20.040 -12.434 -1.084 0.767 1.380 18.957 24.602 4.854 -11.833 ms 0.4888 4.909

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 217.197.83.230

peer offset 217.197.83.230 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 217.197.83.230 -644.978 -430.700 -94.793 1.639 7.916 15.521 21.281 102.708 446.222 72.325 -16.519 ms -6.69 53.08

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 23.131.76.162

peer offset 23.131.76.162 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.131.76.162 -40.144 -9.111 -0.645 3.582 5.655 6.562 8.776 6.300 15.673 3.162 2.924 ms -7.092 89.75

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 23.142.248.8

peer offset 23.142.248.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.142.248.8 -21.913 -6.456 -2.188 6.733 11.176 12.284 16.278 13.364 18.740 4.629 5.757 ms -2.217 12.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 23.143.196.201

peer offset 23.143.196.201 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.143.196.201 -3.248 -2.432 -1.161 2.192 5.184 5.896 6.528 6.345 8.328 2.016 2.129 ms -0.2213 2.34

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

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

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

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



Server Offset 23.143.196.204

peer offset 23.143.196.204 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.143.196.204 -107.049 -94.828 -7.774 0.136 6.684 220.984 222.164 14.458 315.812 33.455 2.740 ms 5.036 36.93

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 23.150.41.123

peer offset 23.150.41.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.150.41.123 -3.102 -0.046 0.663 4.521 7.058 8.535 9.344 6.395 8.581 1.968 4.127 ms -0.3479 3.423

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 23.157.100.123

peer offset 23.157.100.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.157.100.123 -4.745 -3.123 -2.383 0.872 4.094 7.697 13.088 6.477 10.821 2.230 0.872 ms 1.057 7.789

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 23.172.120.58

peer offset 23.172.120.58 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.172.120.58 -79.949 -79.949 -79.949 2.744 9.020 9.020 9.020 88.969 88.969 28.367 -11.643 ms -1.482 3.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 23.186.168.125

peer offset 23.186.168.125 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.125 -7.597 -5.256 -2.601 1.474 3.874 5.461 9.062 6.475 10.717 2.089 1.109 ms -0.6114 4.37

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 23.186.168.126

peer offset 23.186.168.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.126 -4.439 -3.321 -1.941 1.678 3.774 5.283 10.039 5.715 8.604 1.722 1.466 ms -0.2168 5.218

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 23.186.168.127

peer offset 23.186.168.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.127 -58.630 -25.454 -3.967 -0.282 1.996 2.609 17.173 5.963 28.063 5.710 -1.045 ms -8.127 77.12

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 23.186.168.128

peer offset 23.186.168.128 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.128 -7.831 -7.397 -5.841 -1.084 1.297 4.084 63.422 7.138 11.481 5.840 -1.083 ms 9.224 102.7

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 23.186.168.129

peer offset 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.129 -7.304 -5.964 -4.201 0.089 3.966 9.112 11.385 8.167 15.077 2.804 0.061 ms 0.4305 4.255

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 23.186.168.130

peer offset 23.186.168.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.130 -55.890 -48.645 -2.247 1.585 4.061 4.925 18.506 6.308 53.570 6.517 0.686 ms -7.058 57.17

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

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

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

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



Server Offset 23.186.168.131

peer offset 23.186.168.131 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.131 -101.224 -14.992 -10.507 -2.342 4.758 216.109 218.513 15.265 231.100 25.680 -0.393 ms 7.012 64.06

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 23.93.251.54

peer offset 23.93.251.54 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.93.251.54 -51.217 -48.316 1.849 5.492 7.678 9.363 23.453 5.829 57.678 7.050 4.320 ms -6.582 49.67

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

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

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

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



Server Offset 24.111.79.186

peer offset 24.111.79.186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 24.111.79.186 -94.266 -94.266 -94.266 4.192 359.261 359.261 359.261 453.527 453.527 165.614 90.784 ms 0.8726 1.912

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 34.147.28.4

peer offset 34.147.28.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 34.147.28.4 -126.901 -126.901 -79.343 -2.682 5.387 6.747 6.747 84.731 133.648 28.768 -16.642 ms -1.977 6.669

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 38.80.8.230

peer offset 38.80.8.230 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 38.80.8.230 6.608 6.608 6.608 8.543 16.012 16.012 16.012 9.405 9.405 3.256 9.029 ms 1.487 3.635

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 44.190.5.123

peer offset 44.190.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 44.190.5.123 -629.428 -1.789 -0.344 3.447 5.707 10.023 12.530 6.051 11.812 31.118 1.711 ms -20.15 408.8

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

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

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

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



Server Offset 45.139.163.87

peer offset 45.139.163.87 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.139.163.87 -23.711 -16.906 -7.426 3.140 9.320 37.740 41.016 16.746 54.647 7.496 3.209 ms 1.85 12.82

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 45.33.53.84

peer offset 45.33.53.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.33.53.84 -17.924 -11.963 -0.947 2.317 5.234 6.139 20.631 6.180 18.102 2.817 2.106 ms -1.958 18.48

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 45.79.111.167

peer offset 45.79.111.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.79.111.167 -49.125 -40.782 1.444 5.990 9.608 11.350 11.654 8.165 52.133 5.897 5.000 ms -7.129 62.11

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 45.79.13.35

peer offset 45.79.13.35 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.79.13.35 1.657 1.657 1.657 2.347 2.347 2.347 2.347 0.691 0.691 0.345 2.002 ms 1.884e-15 1

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

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

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

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



Server Offset 45.79.227.165

peer offset 45.79.227.165 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.79.227.165 -2.285 -2.285 -0.823 2.093 11.560 16.184 16.184 12.383 18.469 3.577 2.968 ms 1.694 6.086

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 5.57.11.195

peer offset 5.57.11.195 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.57.11.195 7.691 7.691 7.691 9.219 9.219 9.219 9.219 1.528 1.528 0.764 8.455 ms -3.421e-15 1

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

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

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

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



Server Offset 64.131.47.178

peer offset 64.131.47.178 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.131.47.178 -14.668 -8.402 1.294 8.733 14.089 15.647 20.679 12.795 24.050 4.428 8.401 ms -1.592 9.678

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 64.79.100.197

peer offset 64.79.100.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.79.100.197 -2.342 -2.342 -1.290 1.698 3.467 4.619 4.619 4.757 6.961 1.376 1.497 ms -0.6709 3.338

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 65.182.224.60

peer offset 65.182.224.60 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 65.182.224.60 -135.836 0.487 1.679 5.071 8.011 9.028 22.443 6.332 8.541 4.248 4.849 ms -22.07 680

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

peer offset 66.244.16.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.244.16.123 -28.074 -7.346 0.732 5.369 8.352 14.172 37.483 7.621 21.517 4.117 4.837 ms -1.368 37.78

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 67.210.96.32

peer offset 67.210.96.32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 67.210.96.32 -2.561 -1.611 -0.813 3.475 5.579 6.219 7.311 6.392 7.831 1.943 3.069 ms -0.6649 2.816

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 67.217.246.204

peer offset 67.217.246.204 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 67.217.246.204 -16.077 -16.077 -16.077 -6.624 9.348 9.348 9.348 25.425 25.425 7.124 -6.675 ms 1.008 3.706

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 68.183.147.240

peer offset 68.183.147.240 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 68.183.147.240 -203.968 -76.027 -18.550 -0.728 11.605 220.740 222.620 30.155 296.767 38.326 0.582 ms 2.949 29.87

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 69.89.207.99

peer offset 69.89.207.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.89.207.99 -6.705 -3.801 -2.387 1.168 4.811 11.781 20.985 7.197 15.581 2.749 1.289 ms 2.698 19.11

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 72.30.35.88

peer offset 72.30.35.88 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.30.35.88 -0.550 1.048 1.636 5.649 8.897 13.400 17.485 7.262 12.352 2.267 5.458 ms 0.7578 6.645

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 73.185.182.209

peer offset 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 73.185.182.209 -5.858 -5.858 -2.715 1.521 4.652 6.055 6.055 7.367 11.912 2.237 1.362 ms -0.7418 4.211

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 74.208.14.149

peer offset 74.208.14.149 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 74.208.14.149 -23.137 -21.739 -17.023 -4.566 -0.923 12.871 14.795 16.100 34.610 4.966 -5.349 ms -0.1748 8.229

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 77.68.54.236

peer offset 77.68.54.236 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 77.68.54.236 -45.787 -16.205 -3.751 8.205 10.236 12.370 22.562 13.987 28.575 5.741 6.093 ms -3.194 21.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 91.224.149.196

peer offset 91.224.149.196 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 91.224.149.196 -121.847 -121.847 -74.362 -1.999 8.521 14.505 14.505 82.883 136.352 26.960 -12.966 ms -1.996 7.048

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 93.94.88.51

peer offset 93.94.88.51 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 93.94.88.51 5.727 5.727 5.727 8.914 11.648 11.648 11.648 5.921 5.921 2.084 8.668 ms -0.08498 1.687

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 96.19.94.82

peer offset 96.19.94.82 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 96.19.94.82 0.297 0.297 2.740 5.189 7.144 7.510 7.510 4.404 7.212 1.387 5.121 ms -0.7476 4.02

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 96.245.170.99

peer offset 96.245.170.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 96.245.170.99 -6.017 -5.876 -3.123 2.815 5.216 5.802 6.038 8.339 11.679 2.351 2.390 ms -1.525 5.442

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 97.107.136.23

peer offset 97.107.136.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 97.107.136.23 -30.116 -1.254 -0.119 2.964 6.178 7.047 8.178 6.298 8.301 2.165 2.994 ms -2.275 34.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 99.28.14.242

peer offset 99.28.14.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 99.28.14.242 -5.923 -5.923 -4.207 0.059 3.438 4.480 4.480 7.645 10.404 1.955 -0.022 ms -0.3342 3.88

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(3)

peer offset SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(3) -548.313 -0.889 -0.607 -0.159 0.278 0.453 492.808 0.886 1.341 5.536 -0.157 ms -11.15 8330

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(5)

peer offset SHM(5) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(5) -6.214 -0.680 -0.543 -0.094 0.296 0.514 0.725 0.839 1.193 0.390 -0.116 ms -7.627 105.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 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.207.148.118

peer jitter 104.207.148.118 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.207.148.118 0.000 0.773 1.230 3.423 27.147 44.314 65.594 25.917 43.541 8.475 6.197 ms 3.387 15.91

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 104.232.0.123

peer jitter 104.232.0.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.232.0.123 0.000 0.000 0.000 3.344 4.768 4.768 4.768 4.768 4.768 1.498 2.672 ms -0.5272 2.194

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 108.61.215.221

peer jitter 108.61.215.221 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 108.61.215.221 0.000 1.325 2.224 16.796 42.171 52.131 72.527 39.947 50.807 12.688 18.183 ms 0.7497 3.317

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 134.215.155.177

peer jitter 134.215.155.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 134.215.155.177 1.166 1.166 1.224 3.696 7.154 12.563 12.563 5.930 11.397 2.168 4.226 ms 0.9088 4.697

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 136.243.177.133

peer jitter 136.243.177.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 136.243.177.133 0.000 0.000 0.000 2.028 4.634 4.634 4.634 4.634 4.634 1.858 2.128 ms 0.3576 1.473

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 136.244.88.170

peer jitter 136.244.88.170 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 136.244.88.170 0.000 0.000 3.340 53.700 95.857 115.431 115.431 92.517 115.431 26.317 52.780 ms -0.2567 2.74

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 142.248.80.92

peer jitter 142.248.80.92 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 142.248.80.92 0.000 0.000 1.549 21.181 65.301 116.983 119.589 63.752 116.983 20.872 24.694 ms 1.965 8.51

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 144.202.0.197

peer jitter 144.202.0.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.0.197 0.000 0.629 1.565 12.103 38.752 230.623 231.516 37.187 229.994 28.271 17.548 ms 6.255 47.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 144.202.41.38

peer jitter 144.202.41.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.41.38 0.000 0.000 0.000 7.107 63.024 63.024 63.024 63.024 63.024 15.809 12.707 ms 2.194 7.453

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 144.202.66.214

peer jitter 144.202.66.214 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.66.214 0.000 0.908 1.281 3.460 28.421 49.498 65.663 27.140 48.590 9.543 6.636 ms 3.42 16.37

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 144.76.66.157

peer jitter 144.76.66.157 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.76.66.157 0.000 0.000 0.000 22.537 39.690 39.690 39.690 39.690 39.690 12.862 20.083 ms -0.2726 2.012

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 144.91.126.59

peer jitter 144.91.126.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.91.126.59 0.000 0.000 0.000 2.704 53.810 53.810 53.810 53.810 53.810 21.999 14.246 ms 1.153 2.345

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 147.88.195.53

peer jitter 147.88.195.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 147.88.195.53 0.000 0.000 1.577 49.151 92.890 103.980 103.980 91.314 103.980 28.536 45.486 ms -0.06166 2.114

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 149.28.200.179

peer jitter 149.28.200.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.28.200.179 0.000 0.000 0.000 3.136 3.687 3.687 3.687 3.687 3.687 1.419 2.384 ms -0.952 2.19

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 149.28.61.105

peer jitter 149.28.61.105 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.28.61.105 0.000 0.503 1.262 4.626 26.368 56.964 89.252 25.107 56.461 11.306 9.421 ms 3.314 18.89

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 158.51.99.19

peer jitter 158.51.99.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 158.51.99.19 0.000 0.731 1.238 3.582 16.983 23.297 52.793 15.745 22.565 5.449 5.122 ms 3.925 25.63

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 159.203.158.197

peer jitter 159.203.158.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 159.203.158.197 0.000 0.000 0.970 3.679 28.068 35.073 59.229 27.098 35.073 8.869 6.920 ms 2.834 12.9

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.000 0.340 1.068 3.328 12.237 17.690 200.939 11.169 17.349 13.122 5.205 ms 11.93 166.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 162.159.200.123

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.000 0.000 0.646 2.916 10.459 45.394 45.778 9.814 45.394 7.580 4.798 ms 4.613 24.8

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

peer jitter 162.244.81.139 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.244.81.139 0.000 0.826 1.847 13.246 39.579 53.859 116.687 37.732 53.033 13.251 15.177 ms 2.751 18.17

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.254.225.151

peer jitter 162.254.225.151 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.254.225.151 0.000 3.082 8.987 32.115 61.363 75.521 82.844 52.376 72.439 15.378 33.549 ms 0.483 3.374

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

peer jitter 162.254.225.152 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.254.225.152 0.000 0.000 0.000 8.593 27.885 27.885 27.885 27.885 27.885 9.771 11.475 ms 0.5127 1.898

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 163.123.153.14

peer jitter 163.123.153.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 163.123.153.14 1.341 1.341 1.585 3.195 11.487 12.525 12.525 9.902 11.184 2.905 4.106 ms 1.58 4.37

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 167.248.62.201

peer jitter 167.248.62.201 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 167.248.62.201 0.000 1.155 2.100 17.285 46.193 60.101 106.709 44.092 58.947 14.886 19.582 ms 1.154 5.016

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 172.104.28.175

peer jitter 172.104.28.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.104.28.175 0.000 0.000 0.000 3.258 3.451 3.451 3.451 3.451 3.451 1.418 2.445 ms -1.124 2.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.



Server Jitter 172.232.209.103

peer jitter 172.232.209.103 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.232.209.103 0.000 0.000 0.000 1.473 4.884 4.884 4.884 4.884 4.884 1.621 1.690 ms 0.9883 2.805

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 172.232.63.219

peer jitter 172.232.63.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.232.63.219 0.000 1.712 3.783 38.718 65.960 77.114 101.802 62.177 75.402 20.760 35.373 ms -0.04819 1.974

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 172.233.157.223

peer jitter 172.233.157.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.157.223 0.000 0.000 1.315 3.699 14.120 31.995 92.339 12.805 31.995 8.049 5.265 ms 7.904 78.03

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 172.233.189.68

peer jitter 172.233.189.68 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.189.68 0.000 0.000 1.706 18.691 37.751 49.953 52.151 36.044 49.953 11.632 18.495 ms 0.41 2.822

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 172.234.25.10

peer jitter 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.25.10 0.000 0.998 1.474 4.269 20.235 51.678 143.146 18.761 50.680 12.127 6.987 ms 6.993 64.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.234.37.140

peer jitter 172.234.37.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.37.140 0.000 0.000 0.000 3.018 45.831 45.831 45.831 45.831 45.831 14.041 9.772 ms 1.647 4.516

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 172.234.44.141

peer jitter 172.234.44.141 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.44.141 0.000 0.852 1.491 10.714 37.592 42.602 60.768 36.101 41.749 11.682 13.096 ms 1.357 4.987

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 172.235.154.118

peer jitter 172.235.154.118 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.235.154.118 0.000 0.000 1.535 20.649 53.942 63.342 63.958 52.407 63.342 14.580 22.437 ms 0.8483 3.724

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 172.237.147.185

peer jitter 172.237.147.185 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.237.147.185 0.000 0.000 1.246 3.521 35.180 65.369 192.448 33.933 65.369 16.375 7.595 ms 7.156 70.74

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

peer jitter 173.71.69.149 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.71.69.149 0.000 2.626 6.987 27.396 64.007 87.970 99.582 57.020 85.343 17.494 30.027 ms 1.239 5.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 176.120.96.12

peer jitter 176.120.96.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 176.120.96.12 0.000 0.000 0.000 3.141 4.265 4.265 4.265 4.265 4.265 1.391 2.481 ms -0.5143 2.224

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 191.96.11.19

peer jitter 191.96.11.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 191.96.11.19 0.000 0.000 17.039 55.416 100.487 107.908 109.073 83.448 107.908 23.605 58.050 ms 0.07604 2.649

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

peer jitter 192.207.55.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.207.55.254 0.000 0.000 1.395 5.353 78.059 132.954 134.633 76.664 132.954 30.185 17.569 ms 2.68 9.499

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

peer jitter 192.231.84.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.231.84.117 0.000 0.000 0.904 2.731 111.990 114.301 114.301 111.086 114.301 31.413 15.471 ms 2.543 7.959

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

peer jitter 192.231.84.118 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.231.84.118 0.783 0.783 0.987 2.823 5.224 12.104 12.104 4.237 11.321 1.769 3.001 ms 2.302 12.46

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 193.25.222.136

peer jitter 193.25.222.136 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 193.25.222.136 0.000 0.000 16.168 57.233 99.532 111.631 142.839 83.364 111.631 24.708 58.914 ms 0.2412 3.527

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 193.42.63.23

peer jitter 193.42.63.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 193.42.63.23 0.000 0.000 23.581 57.052 101.489 137.095 137.243 77.908 137.095 25.982 59.298 ms 0.2539 3.348

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 194.0.5.123

peer jitter 194.0.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.0.5.123 0.000 0.000 2.042 5.604 64.252 101.012 108.378 62.210 101.012 18.402 10.794 ms 3.781 17.05

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 198.137.202.56

peer jitter 198.137.202.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.137.202.56 0.000 1.370 2.011 4.724 21.562 96.418 98.300 19.551 95.048 12.769 7.070 ms 6.321 44.38

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 198.206.187.98

peer jitter 198.206.187.98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.206.187.98 0.000 0.000 0.000 2.747 29.704 29.704 29.704 29.704 29.704 11.123 7.569 ms 1.462 3.202

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 207.244.103.95

peer jitter 207.244.103.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 207.244.103.95 0.000 0.000 0.797 28.422 57.233 62.990 62.990 56.436 62.990 14.523 27.944 ms 0.1276 2.827

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 208.70.148.101

peer jitter 208.70.148.101 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 208.70.148.101 0.000 0.000 1.072 3.219 19.662 74.616 123.551 18.590 74.616 12.225 5.975 ms 6.569 53.32

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 209.177.158.85

peer jitter 209.177.158.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.177.158.85 0.000 0.000 0.000 6.827 8.779 8.779 8.779 8.779 8.779 3.267 5.079 ms -0.5381 1.893

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 209.205.228.50

peer jitter 209.205.228.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.205.228.50 0.000 0.000 0.000 6.067 10.822 10.822 10.822 10.822 10.822 3.658 6.881 ms -0.5453 2.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 209.51.161.238

peer jitter 209.51.161.238 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.51.161.238 0.000 0.000 1.680 15.367 64.068 97.556 115.689 62.388 97.556 19.899 20.779 ms 1.928 7.566

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 213.108.170.26

peer jitter 213.108.170.26 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 213.108.170.26 0.000 0.000 0.000 23.112 39.710 39.710 39.710 39.710 39.710 14.142 18.806 ms 0.06097 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 216.144.228.179

peer jitter 216.144.228.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.144.228.179 0.000 0.000 0.000 1.952 1.952 1.952 1.952 1.952 1.952 0.976 0.976 ms 0 1

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 216.229.4.66

peer jitter 216.229.4.66 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.229.4.66 0.000 0.000 0.943 2.943 8.520 19.868 19.868 7.576 19.868 2.965 3.509 ms 3.018 15.46

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 216.250.115.174

peer jitter 216.250.115.174 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.250.115.174 0.000 0.000 6.068 20.529 54.934 81.386 83.847 48.866 81.386 17.140 25.105 ms 1.131 4.163

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 217.197.83.230

peer jitter 217.197.83.230 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 217.197.83.230 0.000 0.000 4.956 46.871 90.474 397.834 572.672 85.518 397.834 64.054 52.984 ms 5.569 41.28

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 23.131.76.162

peer jitter 23.131.76.162 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.131.76.162 0.000 0.838 1.143 3.483 32.200 83.041 130.769 31.057 82.204 14.724 7.991 ms 4.356 25.71

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 23.142.248.8

peer jitter 23.142.248.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.142.248.8 0.000 0.000 1.889 23.892 66.465 90.447 125.380 64.576 90.447 21.027 26.393 ms 1.626 7.067

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 23.143.196.201

peer jitter 23.143.196.201 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.143.196.201 0.000 0.947 1.274 3.631 11.912 30.762 56.127 10.638 29.814 5.955 4.936 ms 5.525 42.13

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 23.143.196.204

peer jitter 23.143.196.204 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.143.196.204 0.000 0.000 1.619 5.871 65.017 89.728 93.365 63.399 89.728 20.442 13.760 ms 2.255 6.963

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 23.150.41.123

peer jitter 23.150.41.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.150.41.123 0.000 0.949 1.437 3.169 14.827 18.154 65.524 13.390 17.206 6.124 4.531 ms 6.637 58.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.157.100.123

peer jitter 23.157.100.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.157.100.123 0.000 0.000 1.185 3.466 29.380 139.189 142.047 28.195 139.189 20.111 8.629 ms 4.929 28.67

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 23.172.120.58

peer jitter 23.172.120.58 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.172.120.58 0.000 0.000 0.000 36.865 82.693 82.693 82.693 82.693 82.693 28.106 36.432 ms -0.003439 1.781

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 23.186.168.125

peer jitter 23.186.168.125 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.125 0.000 0.475 1.321 3.503 14.734 22.812 103.846 13.413 22.337 6.761 5.034 ms 8.817 114.9

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 23.186.168.126

peer jitter 23.186.168.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.126 0.000 0.379 1.234 3.520 9.373 20.536 69.160 8.140 20.157 5.676 4.521 ms 8.237 89.8

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 23.186.168.127

peer jitter 23.186.168.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.127 0.000 0.816 1.186 3.260 12.057 34.485 68.429 10.870 33.669 6.156 4.673 ms 5.39 39.95

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 23.186.168.128

peer jitter 23.186.168.128 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.128 0.000 0.000 1.074 3.860 18.835 121.148 160.767 17.761 121.148 19.298 8.224 ms 5.732 38.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 23.186.168.129

peer jitter 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.129 0.000 0.000 1.343 3.576 11.765 155.946 158.429 10.422 155.946 21.546 7.443 ms 6.156 40.28

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 23.186.168.130

peer jitter 23.186.168.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.130 0.000 0.856 1.198 3.184 14.747 52.146 66.437 13.549 51.291 7.610 4.880 ms 5.694 40.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 23.186.168.131

peer jitter 23.186.168.131 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.131 0.000 0.000 1.736 5.260 49.244 94.071 100.094 47.508 94.071 18.648 11.590 ms 3.05 11.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 23.93.251.54

peer jitter 23.93.251.54 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.93.251.54 0.000 0.606 1.336 3.156 16.052 50.104 68.236 14.716 49.497 7.284 4.836 ms 5.676 41.06

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 24.111.79.186

peer jitter 24.111.79.186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 24.111.79.186 0.000 0.000 0.000 29.554 98.190 98.190 98.190 98.190 98.190 24.004 27.902 ms 1.474 5.638

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 34.147.28.4

peer jitter 34.147.28.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 34.147.28.4 0.000 0.000 0.000 36.784 80.641 98.031 98.031 80.641 98.031 26.771 35.752 ms 0.2642 2.026

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 38.80.8.230

peer jitter 38.80.8.230 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 38.80.8.230 0.000 0.000 0.000 4.552 9.249 9.249 9.249 9.249 9.249 3.096 3.714 ms 0.4513 2.293

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 44.190.5.123

peer jitter 44.190.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 44.190.5.123 0.000 0.754 1.161 3.072 12.210 51.300 606.922 11.049 50.546 32.559 6.542 ms 16.19 286.8

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 45.139.163.87

peer jitter 45.139.163.87 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.139.163.87 0.000 1.505 3.948 36.954 67.946 84.052 155.210 63.998 82.547 21.831 35.186 ms 0.5335 4.356

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 45.33.53.84

peer jitter 45.33.53.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.33.53.84 0.000 0.982 1.381 3.846 10.759 26.794 50.227 9.378 25.812 4.647 4.852 ms 4.737 33.81

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 45.79.111.167

peer jitter 45.79.111.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.79.111.167 0.000 0.000 0.953 3.169 15.255 82.645 207.001 14.303 82.645 17.209 6.044 ms 9.837 110.1

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 45.79.13.35

peer jitter 45.79.13.35 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.79.13.35 0.000 0.000 0.000 2.016 2.016 2.016 2.016 2.016 2.016 1.008 1.008 ms 0 1

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 45.79.227.165

peer jitter 45.79.227.165 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.79.227.165 1.043 1.043 1.299 2.959 9.123 13.714 13.714 7.824 12.671 2.882 4.176 ms 1.39 4.601

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 5.57.11.195

peer jitter 5.57.11.195 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.57.11.195 0.000 0.000 0.000 1.528 1.528 1.528 1.528 1.528 1.528 0.764 0.764 ms 0 1

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 64.131.47.178

peer jitter 64.131.47.178 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.131.47.178 0.000 0.000 2.215 20.077 59.730 75.178 76.179 57.515 75.178 15.675 22.212 ms 1.297 5.217

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 64.79.100.197

peer jitter 64.79.100.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.79.100.197 0.000 0.000 1.015 3.244 6.249 8.572 8.572 5.235 8.572 1.612 3.346 ms 0.5926 3.386

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 65.182.224.60

peer jitter 65.182.224.60 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 65.182.224.60 0.000 0.939 1.297 3.840 12.314 53.393 162.196 11.017 52.454 10.041 5.555 ms 9.658 121.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.244.16.123

peer jitter 66.244.16.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.244.16.123 0.000 0.000 1.343 3.655 29.480 79.272 82.711 28.137 79.272 12.302 7.244 ms 4.118 21.53

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 67.210.96.32

peer jitter 67.210.96.32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 67.210.96.32 0.000 0.000 1.207 3.085 15.678 32.664 56.283 14.472 32.664 6.015 4.631 ms 5.327 39.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.



Server Jitter 67.217.246.204

peer jitter 67.217.246.204 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 67.217.246.204 0.000 0.000 0.000 8.214 18.246 18.246 18.246 18.246 18.246 5.353 8.181 ms 0.4194 2.435

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 68.183.147.240

peer jitter 68.183.147.240 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 68.183.147.240 0.000 0.000 1.157 13.703 40.794 119.968 127.941 39.637 119.968 20.038 17.502 ms 3.439 17

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 69.89.207.99

peer jitter 69.89.207.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.89.207.99 0.000 0.906 1.365 3.493 13.900 32.552 72.491 12.535 31.646 6.189 5.141 ms 5.485 43.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 72.30.35.88

peer jitter 72.30.35.88 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.30.35.88 0.000 1.007 1.531 5.856 34.003 42.466 56.014 32.471 41.460 9.973 10.023 ms 1.675 5.678

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 73.185.182.209

peer jitter 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.185.182.209 0.000 0.000 1.722 4.138 20.829 41.394 41.394 19.107 41.394 8.540 7.454 ms 2.602 10.05

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 74.208.14.149

peer jitter 74.208.14.149 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 74.208.14.149 0.000 1.820 12.427 24.899 47.302 58.364 66.145 34.875 56.544 11.079 27.112 ms 0.5371 3.692

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 77.68.54.236

peer jitter 77.68.54.236 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.68.54.236 0.000 0.870 2.597 37.363 68.112 77.995 148.641 65.514 77.125 22.350 35.456 ms 0.2658 3.066

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 91.224.149.196

peer jitter 91.224.149.196 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 91.224.149.196 0.000 0.000 0.000 43.263 88.987 111.344 111.344 88.987 111.344 27.682 42.186 ms 0.329 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 93.94.88.51

peer jitter 93.94.88.51 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 93.94.88.51 0.000 0.000 0.000 3.397 4.085 4.085 4.085 4.085 4.085 1.395 2.685 ms -0.8737 2.601

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 96.19.94.82

peer jitter 96.19.94.82 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 96.19.94.82 0.000 0.000 1.290 8.486 37.107 50.905 50.905 35.817 50.905 10.794 11.028 ms 1.79 6.151

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 96.245.170.99

peer jitter 96.245.170.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 96.245.170.99 0.000 0.000 0.928 18.260 41.943 57.524 58.502 41.015 57.524 13.116 19.082 ms 0.5645 3.202

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 97.107.136.23

peer jitter 97.107.136.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 97.107.136.23 0.000 0.995 1.498 5.148 28.169 47.150 68.240 26.671 46.155 9.352 9.035 ms 2.29 9.624

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 99.28.14.242

peer jitter 99.28.14.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 99.28.14.242 0.556 0.556 1.011 2.330 5.902 6.270 6.270 4.892 5.714 1.210 2.559 ms 1.297 4.695

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(3)

peer jitter SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(3) 0.000 0.136 0.177 0.295 0.497 0.601 60.851 0.320 0.466 0.839 0.330 ms 56.45 3551

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(5)

peer jitter SHM(5) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(5) 0.000 0.096 0.141 0.254 0.478 1.017 3.570 0.338 0.920 0.263 0.295 ms 8.352 86.43

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.355 10.613 10.715 11.157 13.026 13.212 14.029 2.311 2.600 0.616 11.307 ppm 1.901 6.433
Local Clock Time Offset -64.349 -0.769 -0.405 -0.001 0.413 0.754 21.088 0.817 1.523 0.780 0.007 ms -23.37 2511
Local RMS Frequency Jitter 0.000 3.592 4.878 6.941 11.606 173.266 950.123 6.728 169.674 39.803 11.635 ppb 12.92 207.7
Local RMS Time Jitter 0.000 0.175 0.240 0.352 0.508 2.974 27.265 0.268 2.800 0.750 0.436 ms 18.51 492.7
Server Jitter 104.207.148.118 0.000 0.773 1.230 3.423 27.147 44.314 65.594 25.917 43.541 8.475 6.197 ms 3.387 15.91
Server Jitter 104.232.0.123 0.000 0.000 0.000 3.344 4.768 4.768 4.768 4.768 4.768 1.498 2.672 ms -0.5272 2.194
Server Jitter 108.61.215.221 0.000 1.325 2.224 16.796 42.171 52.131 72.527 39.947 50.807 12.688 18.183 ms 0.7497 3.317
Server Jitter 134.215.155.177 1.166 1.166 1.224 3.696 7.154 12.563 12.563 5.930 11.397 2.168 4.226 ms 0.9088 4.697
Server Jitter 136.243.177.133 0.000 0.000 0.000 2.028 4.634 4.634 4.634 4.634 4.634 1.858 2.128 ms 0.3576 1.473
Server Jitter 136.244.88.170 0.000 0.000 3.340 53.700 95.857 115.431 115.431 92.517 115.431 26.317 52.780 ms -0.2567 2.74
Server Jitter 142.248.80.92 0.000 0.000 1.549 21.181 65.301 116.983 119.589 63.752 116.983 20.872 24.694 ms 1.965 8.51
Server Jitter 144.202.0.197 0.000 0.629 1.565 12.103 38.752 230.623 231.516 37.187 229.994 28.271 17.548 ms 6.255 47.24
Server Jitter 144.202.41.38 0.000 0.000 0.000 7.107 63.024 63.024 63.024 63.024 63.024 15.809 12.707 ms 2.194 7.453
Server Jitter 144.202.66.214 0.000 0.908 1.281 3.460 28.421 49.498 65.663 27.140 48.590 9.543 6.636 ms 3.42 16.37
Server Jitter 144.76.66.157 0.000 0.000 0.000 22.537 39.690 39.690 39.690 39.690 39.690 12.862 20.083 ms -0.2726 2.012
Server Jitter 144.91.126.59 0.000 0.000 0.000 2.704 53.810 53.810 53.810 53.810 53.810 21.999 14.246 ms 1.153 2.345
Server Jitter 147.88.195.53 0.000 0.000 1.577 49.151 92.890 103.980 103.980 91.314 103.980 28.536 45.486 ms -0.06166 2.114
Server Jitter 149.28.200.179 0.000 0.000 0.000 3.136 3.687 3.687 3.687 3.687 3.687 1.419 2.384 ms -0.952 2.19
Server Jitter 149.28.61.105 0.000 0.503 1.262 4.626 26.368 56.964 89.252 25.107 56.461 11.306 9.421 ms 3.314 18.89
Server Jitter 158.51.99.19 0.000 0.731 1.238 3.582 16.983 23.297 52.793 15.745 22.565 5.449 5.122 ms 3.925 25.63
Server Jitter 159.203.158.197 0.000 0.000 0.970 3.679 28.068 35.073 59.229 27.098 35.073 8.869 6.920 ms 2.834 12.9
Server Jitter 162.159.200.1 0.000 0.340 1.068 3.328 12.237 17.690 200.939 11.169 17.349 13.122 5.205 ms 11.93 166.6
Server Jitter 162.159.200.123 0.000 0.000 0.646 2.916 10.459 45.394 45.778 9.814 45.394 7.580 4.798 ms 4.613 24.8
Server Jitter 162.244.81.139 0.000 0.826 1.847 13.246 39.579 53.859 116.687 37.732 53.033 13.251 15.177 ms 2.751 18.17
Server Jitter 162.254.225.151 0.000 3.082 8.987 32.115 61.363 75.521 82.844 52.376 72.439 15.378 33.549 ms 0.483 3.374
Server Jitter 162.254.225.152 0.000 0.000 0.000 8.593 27.885 27.885 27.885 27.885 27.885 9.771 11.475 ms 0.5127 1.898
Server Jitter 163.123.153.14 1.341 1.341 1.585 3.195 11.487 12.525 12.525 9.902 11.184 2.905 4.106 ms 1.58 4.37
Server Jitter 167.248.62.201 0.000 1.155 2.100 17.285 46.193 60.101 106.709 44.092 58.947 14.886 19.582 ms 1.154 5.016
Server Jitter 172.104.28.175 0.000 0.000 0.000 3.258 3.451 3.451 3.451 3.451 3.451 1.418 2.445 ms -1.124 2.31
Server Jitter 172.232.209.103 0.000 0.000 0.000 1.473 4.884 4.884 4.884 4.884 4.884 1.621 1.690 ms 0.9883 2.805
Server Jitter 172.232.63.219 0.000 1.712 3.783 38.718 65.960 77.114 101.802 62.177 75.402 20.760 35.373 ms -0.04819 1.974
Server Jitter 172.233.157.223 0.000 0.000 1.315 3.699 14.120 31.995 92.339 12.805 31.995 8.049 5.265 ms 7.904 78.03
Server Jitter 172.233.189.68 0.000 0.000 1.706 18.691 37.751 49.953 52.151 36.044 49.953 11.632 18.495 ms 0.41 2.822
Server Jitter 172.234.25.10 0.000 0.998 1.474 4.269 20.235 51.678 143.146 18.761 50.680 12.127 6.987 ms 6.993 64.7
Server Jitter 172.234.37.140 0.000 0.000 0.000 3.018 45.831 45.831 45.831 45.831 45.831 14.041 9.772 ms 1.647 4.516
Server Jitter 172.234.44.141 0.000 0.852 1.491 10.714 37.592 42.602 60.768 36.101 41.749 11.682 13.096 ms 1.357 4.987
Server Jitter 172.235.154.118 0.000 0.000 1.535 20.649 53.942 63.342 63.958 52.407 63.342 14.580 22.437 ms 0.8483 3.724
Server Jitter 172.237.147.185 0.000 0.000 1.246 3.521 35.180 65.369 192.448 33.933 65.369 16.375 7.595 ms 7.156 70.74
Server Jitter 173.71.69.149 0.000 2.626 6.987 27.396 64.007 87.970 99.582 57.020 85.343 17.494 30.027 ms 1.239 5.3
Server Jitter 176.120.96.12 0.000 0.000 0.000 3.141 4.265 4.265 4.265 4.265 4.265 1.391 2.481 ms -0.5143 2.224
Server Jitter 191.96.11.19 0.000 0.000 17.039 55.416 100.487 107.908 109.073 83.448 107.908 23.605 58.050 ms 0.07604 2.649
Server Jitter 192.207.55.254 0.000 0.000 1.395 5.353 78.059 132.954 134.633 76.664 132.954 30.185 17.569 ms 2.68 9.499
Server Jitter 192.231.84.117 0.000 0.000 0.904 2.731 111.990 114.301 114.301 111.086 114.301 31.413 15.471 ms 2.543 7.959
Server Jitter 192.231.84.118 0.783 0.783 0.987 2.823 5.224 12.104 12.104 4.237 11.321 1.769 3.001 ms 2.302 12.46
Server Jitter 193.25.222.136 0.000 0.000 16.168 57.233 99.532 111.631 142.839 83.364 111.631 24.708 58.914 ms 0.2412 3.527
Server Jitter 193.42.63.23 0.000 0.000 23.581 57.052 101.489 137.095 137.243 77.908 137.095 25.982 59.298 ms 0.2539 3.348
Server Jitter 194.0.5.123 0.000 0.000 2.042 5.604 64.252 101.012 108.378 62.210 101.012 18.402 10.794 ms 3.781 17.05
Server Jitter 198.137.202.56 0.000 1.370 2.011 4.724 21.562 96.418 98.300 19.551 95.048 12.769 7.070 ms 6.321 44.38
Server Jitter 198.206.187.98 0.000 0.000 0.000 2.747 29.704 29.704 29.704 29.704 29.704 11.123 7.569 ms 1.462 3.202
Server Jitter 207.244.103.95 0.000 0.000 0.797 28.422 57.233 62.990 62.990 56.436 62.990 14.523 27.944 ms 0.1276 2.827
Server Jitter 208.70.148.101 0.000 0.000 1.072 3.219 19.662 74.616 123.551 18.590 74.616 12.225 5.975 ms 6.569 53.32
Server Jitter 209.177.158.85 0.000 0.000 0.000 6.827 8.779 8.779 8.779 8.779 8.779 3.267 5.079 ms -0.5381 1.893
Server Jitter 209.205.228.50 0.000 0.000 0.000 6.067 10.822 10.822 10.822 10.822 10.822 3.658 6.881 ms -0.5453 2.24
Server Jitter 209.51.161.238 0.000 0.000 1.680 15.367 64.068 97.556 115.689 62.388 97.556 19.899 20.779 ms 1.928 7.566
Server Jitter 213.108.170.26 0.000 0.000 0.000 23.112 39.710 39.710 39.710 39.710 39.710 14.142 18.806 ms 0.06097 1.708
Server Jitter 216.144.228.179 0.000 0.000 0.000 1.952 1.952 1.952 1.952 1.952 1.952 0.976 0.976 ms 0 1
Server Jitter 216.229.4.66 0.000 0.000 0.943 2.943 8.520 19.868 19.868 7.576 19.868 2.965 3.509 ms 3.018 15.46
Server Jitter 216.250.115.174 0.000 0.000 6.068 20.529 54.934 81.386 83.847 48.866 81.386 17.140 25.105 ms 1.131 4.163
Server Jitter 217.197.83.230 0.000 0.000 4.956 46.871 90.474 397.834 572.672 85.518 397.834 64.054 52.984 ms 5.569 41.28
Server Jitter 23.131.76.162 0.000 0.838 1.143 3.483 32.200 83.041 130.769 31.057 82.204 14.724 7.991 ms 4.356 25.71
Server Jitter 23.142.248.8 0.000 0.000 1.889 23.892 66.465 90.447 125.380 64.576 90.447 21.027 26.393 ms 1.626 7.067
Server Jitter 23.143.196.201 0.000 0.947 1.274 3.631 11.912 30.762 56.127 10.638 29.814 5.955 4.936 ms 5.525 42.13
Server Jitter 23.143.196.204 0.000 0.000 1.619 5.871 65.017 89.728 93.365 63.399 89.728 20.442 13.760 ms 2.255 6.963
Server Jitter 23.150.41.123 0.000 0.949 1.437 3.169 14.827 18.154 65.524 13.390 17.206 6.124 4.531 ms 6.637 58.7
Server Jitter 23.157.100.123 0.000 0.000 1.185 3.466 29.380 139.189 142.047 28.195 139.189 20.111 8.629 ms 4.929 28.67
Server Jitter 23.172.120.58 0.000 0.000 0.000 36.865 82.693 82.693 82.693 82.693 82.693 28.106 36.432 ms -0.003439 1.781
Server Jitter 23.186.168.125 0.000 0.475 1.321 3.503 14.734 22.812 103.846 13.413 22.337 6.761 5.034 ms 8.817 114.9
Server Jitter 23.186.168.126 0.000 0.379 1.234 3.520 9.373 20.536 69.160 8.140 20.157 5.676 4.521 ms 8.237 89.8
Server Jitter 23.186.168.127 0.000 0.816 1.186 3.260 12.057 34.485 68.429 10.870 33.669 6.156 4.673 ms 5.39 39.95
Server Jitter 23.186.168.128 0.000 0.000 1.074 3.860 18.835 121.148 160.767 17.761 121.148 19.298 8.224 ms 5.732 38.6
Server Jitter 23.186.168.129 0.000 0.000 1.343 3.576 11.765 155.946 158.429 10.422 155.946 21.546 7.443 ms 6.156 40.28
Server Jitter 23.186.168.130 0.000 0.856 1.198 3.184 14.747 52.146 66.437 13.549 51.291 7.610 4.880 ms 5.694 40.5
Server Jitter 23.186.168.131 0.000 0.000 1.736 5.260 49.244 94.071 100.094 47.508 94.071 18.648 11.590 ms 3.05 11.83
Server Jitter 23.93.251.54 0.000 0.606 1.336 3.156 16.052 50.104 68.236 14.716 49.497 7.284 4.836 ms 5.676 41.06
Server Jitter 24.111.79.186 0.000 0.000 0.000 29.554 98.190 98.190 98.190 98.190 98.190 24.004 27.902 ms 1.474 5.638
Server Jitter 34.147.28.4 0.000 0.000 0.000 36.784 80.641 98.031 98.031 80.641 98.031 26.771 35.752 ms 0.2642 2.026
Server Jitter 38.80.8.230 0.000 0.000 0.000 4.552 9.249 9.249 9.249 9.249 9.249 3.096 3.714 ms 0.4513 2.293
Server Jitter 44.190.5.123 0.000 0.754 1.161 3.072 12.210 51.300 606.922 11.049 50.546 32.559 6.542 ms 16.19 286.8
Server Jitter 45.139.163.87 0.000 1.505 3.948 36.954 67.946 84.052 155.210 63.998 82.547 21.831 35.186 ms 0.5335 4.356
Server Jitter 45.33.53.84 0.000 0.982 1.381 3.846 10.759 26.794 50.227 9.378 25.812 4.647 4.852 ms 4.737 33.81
Server Jitter 45.79.111.167 0.000 0.000 0.953 3.169 15.255 82.645 207.001 14.303 82.645 17.209 6.044 ms 9.837 110.1
Server Jitter 45.79.13.35 0.000 0.000 0.000 2.016 2.016 2.016 2.016 2.016 2.016 1.008 1.008 ms 0 1
Server Jitter 45.79.227.165 1.043 1.043 1.299 2.959 9.123 13.714 13.714 7.824 12.671 2.882 4.176 ms 1.39 4.601
Server Jitter 5.57.11.195 0.000 0.000 0.000 1.528 1.528 1.528 1.528 1.528 1.528 0.764 0.764 ms 0 1
Server Jitter 64.131.47.178 0.000 0.000 2.215 20.077 59.730 75.178 76.179 57.515 75.178 15.675 22.212 ms 1.297 5.217
Server Jitter 64.79.100.197 0.000 0.000 1.015 3.244 6.249 8.572 8.572 5.235 8.572 1.612 3.346 ms 0.5926 3.386
Server Jitter 65.182.224.60 0.000 0.939 1.297 3.840 12.314 53.393 162.196 11.017 52.454 10.041 5.555 ms 9.658 121.3
Server Jitter 66.244.16.123 0.000 0.000 1.343 3.655 29.480 79.272 82.711 28.137 79.272 12.302 7.244 ms 4.118 21.53
Server Jitter 67.210.96.32 0.000 0.000 1.207 3.085 15.678 32.664 56.283 14.472 32.664 6.015 4.631 ms 5.327 39.04
Server Jitter 67.217.246.204 0.000 0.000 0.000 8.214 18.246 18.246 18.246 18.246 18.246 5.353 8.181 ms 0.4194 2.435
Server Jitter 68.183.147.240 0.000 0.000 1.157 13.703 40.794 119.968 127.941 39.637 119.968 20.038 17.502 ms 3.439 17
Server Jitter 69.89.207.99 0.000 0.906 1.365 3.493 13.900 32.552 72.491 12.535 31.646 6.189 5.141 ms 5.485 43.88
Server Jitter 72.30.35.88 0.000 1.007 1.531 5.856 34.003 42.466 56.014 32.471 41.460 9.973 10.023 ms 1.675 5.678
Server Jitter 73.185.182.209 0.000 0.000 1.722 4.138 20.829 41.394 41.394 19.107 41.394 8.540 7.454 ms 2.602 10.05
Server Jitter 74.208.14.149 0.000 1.820 12.427 24.899 47.302 58.364 66.145 34.875 56.544 11.079 27.112 ms 0.5371 3.692
Server Jitter 77.68.54.236 0.000 0.870 2.597 37.363 68.112 77.995 148.641 65.514 77.125 22.350 35.456 ms 0.2658 3.066
Server Jitter 91.224.149.196 0.000 0.000 0.000 43.263 88.987 111.344 111.344 88.987 111.344 27.682 42.186 ms 0.329 2.512
Server Jitter 93.94.88.51 0.000 0.000 0.000 3.397 4.085 4.085 4.085 4.085 4.085 1.395 2.685 ms -0.8737 2.601
Server Jitter 96.19.94.82 0.000 0.000 1.290 8.486 37.107 50.905 50.905 35.817 50.905 10.794 11.028 ms 1.79 6.151
Server Jitter 96.245.170.99 0.000 0.000 0.928 18.260 41.943 57.524 58.502 41.015 57.524 13.116 19.082 ms 0.5645 3.202
Server Jitter 97.107.136.23 0.000 0.995 1.498 5.148 28.169 47.150 68.240 26.671 46.155 9.352 9.035 ms 2.29 9.624
Server Jitter 99.28.14.242 0.556 0.556 1.011 2.330 5.902 6.270 6.270 4.892 5.714 1.210 2.559 ms 1.297 4.695
Server Jitter SHM(3) 0.000 0.136 0.177 0.295 0.497 0.601 60.851 0.320 0.466 0.839 0.330 ms 56.45 3551
Server Jitter SHM(5) 0.000 0.096 0.141 0.254 0.478 1.017 3.570 0.338 0.920 0.263 0.295 ms 8.352 86.43
Server Offset 104.207.148.118 -11.999 -5.604 -0.209 4.792 7.585 13.740 17.586 7.794 19.344 2.874 4.340 ms -0.5466 8.692
Server Offset 104.232.0.123 2.639 2.639 2.639 4.841 7.033 7.033 7.033 4.394 4.394 1.310 4.792 ms 0.1249 2.376
Server Offset 108.61.215.221 -26.608 -2.493 1.820 6.633 10.271 12.393 24.349 8.451 14.886 3.256 6.369 ms -1.578 22.6
Server Offset 134.215.155.177 -8.187 -8.187 -5.536 -1.522 4.849 10.577 10.577 10.385 18.764 3.047 -0.997 ms 1.041 5.461
Server Offset 136.243.177.133 7.703 7.703 7.703 9.843 13.947 13.947 13.947 6.244 6.244 2.291 10.391 ms 0.5115 1.634
Server Offset 136.244.88.170 -31.789 -31.789 -20.842 0.045 4.000 10.603 10.603 24.842 42.393 7.703 -2.888 ms -1.676 6.132
Server Offset 142.248.80.92 -19.763 -7.670 0.151 7.998 11.634 12.986 21.215 11.482 20.656 4.630 6.869 ms -1.892 11.84
Server Offset 144.202.0.197 -3.748 -3.338 -2.473 1.606 4.141 4.997 7.488 6.614 8.335 2.063 1.221 ms -0.3413 2.722
Server Offset 144.202.41.38 -12.773 -12.773 -12.773 9.932 20.588 20.588 20.588 33.361 33.361 7.001 9.181 ms -1.843 7.452
Server Offset 144.202.66.214 2.075 4.000 5.208 8.650 11.148 15.751 16.968 5.940 11.752 1.921 8.563 ms 0.4606 6.066
Server Offset 144.76.66.157 -3.402 -3.402 -3.402 -0.816 3.576 3.576 3.576 6.977 6.977 2.655 -0.287 ms 0.3401 1.604
Server Offset 144.91.126.59 -6.438 -6.438 -6.438 10.861 13.635 13.635 13.635 20.073 20.073 7.448 7.058 ms -1.052 2.293
Server Offset 147.88.195.53 -34.267 -34.267 -27.801 -4.838 -2.374 -1.503 -1.503 25.427 32.764 8.607 -9.321 ms -1.287 3.331
Server Offset 149.28.200.179 -1.566 -1.566 -1.566 0.261 3.397 3.397 3.397 4.963 4.963 1.890 0.322 ms 0.7746 2.031
Server Offset 149.28.61.105 -2.893 -1.393 0.166 4.255 6.538 7.580 9.416 6.371 8.973 1.954 3.877 ms -0.6158 3.314
Server Offset 158.51.99.19 -1.962 -1.069 0.074 3.420 5.765 9.486 24.445 5.691 10.555 2.496 3.403 ms 3.821 32.72
Server Offset 159.203.158.197 -3.409 -2.313 0.649 5.552 7.905 8.880 9.205 7.257 11.193 2.163 5.248 ms -1.443 6.054
Server Offset 162.159.200.1 -2.180 -0.794 1.356 5.450 7.723 9.037 10.729 6.367 9.831 1.971 5.054 ms -0.7465 4.059
Server Offset 162.159.200.123 -3.559 -2.720 -0.675 5.966 8.671 11.944 16.947 9.345 14.663 3.024 5.157 ms -0.4234 4.78
Server Offset 162.244.81.139 -3.970 -2.402 -1.700 2.667 5.309 6.320 11.561 7.009 8.722 2.227 2.397 ms -0.01836 4.144
Server Offset 162.254.225.151 -17.956 -15.060 -5.708 10.223 16.437 18.274 18.494 22.145 33.334 6.977 8.368 ms -1.195 4.441
Server Offset 162.254.225.152 -1.848 -1.848 -1.848 11.984 17.922 17.922 17.922 19.770 19.770 5.527 10.638 ms -0.901 3.021
Server Offset 163.123.153.14 -9.441 -9.441 -3.988 -0.222 4.125 5.456 5.456 8.113 14.896 2.500 -0.368 ms -0.3748 4.801
Server Offset 167.248.62.201 -36.149 -8.871 -0.418 3.596 6.839 9.001 13.433 7.257 17.872 3.422 3.176 ms -4.087 36.12
Server Offset 172.104.28.175 -1.388 -1.388 -1.388 -0.100 3.196 3.196 3.196 4.583 4.583 1.717 0.342 ms 0.8717 2.171
Server Offset 172.232.209.103 7.280 7.280 7.280 9.577 13.556 13.556 13.556 6.276 6.276 2.021 9.583 ms 0.9553 2.817
Server Offset 172.232.63.219 -33.437 -20.344 -9.115 1.011 5.236 14.138 34.749 14.352 34.482 5.453 0.236 ms -1.079 12.54
Server Offset 172.233.157.223 -34.981 -2.753 -0.971 2.731 12.580 18.256 52.964 13.551 21.009 5.455 3.422 ms 2.119 35.98
Server Offset 172.233.189.68 0.880 1.706 3.867 9.537 14.514 16.678 17.957 10.647 14.973 3.031 9.281 ms -0.08943 3.421
Server Offset 172.234.25.10 -42.533 -3.456 -1.823 1.877 6.389 11.586 22.519 8.212 15.042 3.478 1.908 ms -2.539 54.07
Server Offset 172.234.37.140 -13.004 -13.004 -13.004 7.334 32.827 32.827 32.827 45.831 45.831 10.439 7.833 ms 0.5743 4.875
Server Offset 172.234.44.141 0.161 0.258 1.885 5.464 8.767 13.230 14.363 6.882 12.971 2.446 5.617 ms 0.7521 4.851
Server Offset 172.235.154.118 -1.805 0.077 3.315 7.192 10.233 14.821 16.912 6.918 14.744 2.413 7.174 ms 0.02952 5.667
Server Offset 172.237.147.185 -200.621 -7.616 -0.855 3.793 6.883 15.346 16.593 7.738 22.962 13.165 2.907 ms -14.59 225.8
Server Offset 173.71.69.149 -32.631 -23.065 -3.051 1.666 5.159 6.822 7.925 8.210 29.887 4.482 1.127 ms -4.836 34.19
Server Offset 176.120.96.12 7.763 7.763 7.763 10.322 13.850 13.850 13.850 6.087 6.087 2.060 10.546 ms 0.374 1.845
Server Offset 191.96.11.19 -33.510 -27.663 -8.237 5.810 9.079 11.474 12.362 17.316 39.137 6.694 3.626 ms -2.763 13.45
Server Offset 192.207.55.254 -68.913 -55.256 -6.572 0.132 6.972 15.177 22.208 13.544 70.432 8.299 -0.601 ms -5.484 44.3
Server Offset 192.231.84.117 -2.391 -2.391 1.478 4.260 7.283 65.926 65.926 5.805 68.317 9.116 5.351 ms 6.221 41.5
Server Offset 192.231.84.118 -1.548 -1.548 -1.131 1.669 6.088 12.258 12.258 7.219 13.806 2.297 1.986 ms 1.634 8.05
Server Offset 193.25.222.136 -161.067 -64.510 -18.201 3.404 7.219 8.835 9.217 25.420 73.346 18.068 -0.427 ms -7.05 59.63
Server Offset 193.42.63.23 -59.983 -23.546 -9.466 6.724 9.953 10.570 11.591 19.419 34.116 8.626 3.718 ms -3.942 25.7
Server Offset 194.0.5.123 -26.416 -11.770 -5.483 2.355 11.459 224.213 227.738 16.943 235.983 30.653 6.323 ms 6.815 48.95
Server Offset 198.137.202.56 -2.919 -2.236 -1.431 1.589 4.673 6.062 6.088 6.105 8.298 1.933 1.473 ms 0.1306 2.384
Server Offset 198.206.187.98 -51.757 -51.757 -51.757 -48.763 -19.447 -19.447 -19.447 32.310 32.310 11.963 -43.169 ms 1.436 3.168
Server Offset 207.244.103.95 -7.124 -7.124 0.999 10.585 17.648 18.445 18.445 16.649 25.569 4.483 9.686 ms -1.342 6.812
Server Offset 208.70.148.101 -8.831 -5.331 1.105 5.436 7.602 18.582 380.175 6.497 23.913 25.124 6.732 ms 14.5 213.9
Server Offset 209.177.158.85 -3.024 -3.024 -3.024 1.651 3.804 3.804 3.804 6.827 6.827 2.492 0.610 ms -0.2339 1.812
Server Offset 209.205.228.50 7.010 7.010 7.010 18.187 24.067 24.067 24.067 17.057 17.057 5.704 16.869 ms -0.6241 2.005
Server Offset 209.51.161.238 -153.422 -127.019 -23.151 0.591 8.422 219.405 221.766 31.573 346.425 38.719 1.412 ms 3.117 25.69
Server Offset 213.108.170.26 -4.269 -4.269 -4.269 -1.792 2.919 2.919 2.919 7.189 7.189 2.884 -0.922 ms 0.2241 1.32
Server Offset 216.144.228.179 4.214 4.214 4.214 6.167 6.167 6.167 6.167 1.952 1.952 0.976 5.191 ms 0 1
Server Offset 216.229.4.66 -2.093 -2.093 -0.203 4.137 5.998 10.083 10.083 6.201 12.176 2.006 3.911 ms -0.6222 4.429
Server Offset 216.250.115.174 -27.840 -23.835 -20.040 -12.434 -1.084 0.767 1.380 18.957 24.602 4.854 -11.833 ms 0.4888 4.909
Server Offset 217.197.83.230 -644.978 -430.700 -94.793 1.639 7.916 15.521 21.281 102.708 446.222 72.325 -16.519 ms -6.69 53.08
Server Offset 23.131.76.162 -40.144 -9.111 -0.645 3.582 5.655 6.562 8.776 6.300 15.673 3.162 2.924 ms -7.092 89.75
Server Offset 23.142.248.8 -21.913 -6.456 -2.188 6.733 11.176 12.284 16.278 13.364 18.740 4.629 5.757 ms -2.217 12.71
Server Offset 23.143.196.201 -3.248 -2.432 -1.161 2.192 5.184 5.896 6.528 6.345 8.328 2.016 2.129 ms -0.2213 2.34
Server Offset 23.143.196.204 -107.049 -94.828 -7.774 0.136 6.684 220.984 222.164 14.458 315.812 33.455 2.740 ms 5.036 36.93
Server Offset 23.150.41.123 -3.102 -0.046 0.663 4.521 7.058 8.535 9.344 6.395 8.581 1.968 4.127 ms -0.3479 3.423
Server Offset 23.157.100.123 -4.745 -3.123 -2.383 0.872 4.094 7.697 13.088 6.477 10.821 2.230 0.872 ms 1.057 7.789
Server Offset 23.172.120.58 -79.949 -79.949 -79.949 2.744 9.020 9.020 9.020 88.969 88.969 28.367 -11.643 ms -1.482 3.759
Server Offset 23.186.168.125 -7.597 -5.256 -2.601 1.474 3.874 5.461 9.062 6.475 10.717 2.089 1.109 ms -0.6114 4.37
Server Offset 23.186.168.126 -4.439 -3.321 -1.941 1.678 3.774 5.283 10.039 5.715 8.604 1.722 1.466 ms -0.2168 5.218
Server Offset 23.186.168.127 -58.630 -25.454 -3.967 -0.282 1.996 2.609 17.173 5.963 28.063 5.710 -1.045 ms -8.127 77.12
Server Offset 23.186.168.128 -7.831 -7.397 -5.841 -1.084 1.297 4.084 63.422 7.138 11.481 5.840 -1.083 ms 9.224 102.7
Server Offset 23.186.168.129 -7.304 -5.964 -4.201 0.089 3.966 9.112 11.385 8.167 15.077 2.804 0.061 ms 0.4305 4.255
Server Offset 23.186.168.130 -55.890 -48.645 -2.247 1.585 4.061 4.925 18.506 6.308 53.570 6.517 0.686 ms -7.058 57.17
Server Offset 23.186.168.131 -101.224 -14.992 -10.507 -2.342 4.758 216.109 218.513 15.265 231.100 25.680 -0.393 ms 7.012 64.06
Server Offset 23.93.251.54 -51.217 -48.316 1.849 5.492 7.678 9.363 23.453 5.829 57.678 7.050 4.320 ms -6.582 49.67
Server Offset 24.111.79.186 -94.266 -94.266 -94.266 4.192 359.261 359.261 359.261 453.527 453.527 165.614 90.784 ms 0.8726 1.912
Server Offset 34.147.28.4 -126.901 -126.901 -79.343 -2.682 5.387 6.747 6.747 84.731 133.648 28.768 -16.642 ms -1.977 6.669
Server Offset 38.80.8.230 6.608 6.608 6.608 8.543 16.012 16.012 16.012 9.405 9.405 3.256 9.029 ms 1.487 3.635
Server Offset 44.190.5.123 -629.428 -1.789 -0.344 3.447 5.707 10.023 12.530 6.051 11.812 31.118 1.711 ms -20.15 408.8
Server Offset 45.139.163.87 -23.711 -16.906 -7.426 3.140 9.320 37.740 41.016 16.746 54.647 7.496 3.209 ms 1.85 12.82
Server Offset 45.33.53.84 -17.924 -11.963 -0.947 2.317 5.234 6.139 20.631 6.180 18.102 2.817 2.106 ms -1.958 18.48
Server Offset 45.79.111.167 -49.125 -40.782 1.444 5.990 9.608 11.350 11.654 8.165 52.133 5.897 5.000 ms -7.129 62.11
Server Offset 45.79.13.35 1.657 1.657 1.657 2.347 2.347 2.347 2.347 0.691 0.691 0.345 2.002 ms 1.884e-15 1
Server Offset 45.79.227.165 -2.285 -2.285 -0.823 2.093 11.560 16.184 16.184 12.383 18.469 3.577 2.968 ms 1.694 6.086
Server Offset 5.57.11.195 7.691 7.691 7.691 9.219 9.219 9.219 9.219 1.528 1.528 0.764 8.455 ms -3.421e-15 1
Server Offset 64.131.47.178 -14.668 -8.402 1.294 8.733 14.089 15.647 20.679 12.795 24.050 4.428 8.401 ms -1.592 9.678
Server Offset 64.79.100.197 -2.342 -2.342 -1.290 1.698 3.467 4.619 4.619 4.757 6.961 1.376 1.497 ms -0.6709 3.338
Server Offset 65.182.224.60 -135.836 0.487 1.679 5.071 8.011 9.028 22.443 6.332 8.541 4.248 4.849 ms -22.07 680
Server Offset 66.244.16.123 -28.074 -7.346 0.732 5.369 8.352 14.172 37.483 7.621 21.517 4.117 4.837 ms -1.368 37.78
Server Offset 67.210.96.32 -2.561 -1.611 -0.813 3.475 5.579 6.219 7.311 6.392 7.831 1.943 3.069 ms -0.6649 2.816
Server Offset 67.217.246.204 -16.077 -16.077 -16.077 -6.624 9.348 9.348 9.348 25.425 25.425 7.124 -6.675 ms 1.008 3.706
Server Offset 68.183.147.240 -203.968 -76.027 -18.550 -0.728 11.605 220.740 222.620 30.155 296.767 38.326 0.582 ms 2.949 29.87
Server Offset 69.89.207.99 -6.705 -3.801 -2.387 1.168 4.811 11.781 20.985 7.197 15.581 2.749 1.289 ms 2.698 19.11
Server Offset 72.30.35.88 -0.550 1.048 1.636 5.649 8.897 13.400 17.485 7.262 12.352 2.267 5.458 ms 0.7578 6.645
Server Offset 73.185.182.209 -5.858 -5.858 -2.715 1.521 4.652 6.055 6.055 7.367 11.912 2.237 1.362 ms -0.7418 4.211
Server Offset 74.208.14.149 -23.137 -21.739 -17.023 -4.566 -0.923 12.871 14.795 16.100 34.610 4.966 -5.349 ms -0.1748 8.229
Server Offset 77.68.54.236 -45.787 -16.205 -3.751 8.205 10.236 12.370 22.562 13.987 28.575 5.741 6.093 ms -3.194 21.4
Server Offset 91.224.149.196 -121.847 -121.847 -74.362 -1.999 8.521 14.505 14.505 82.883 136.352 26.960 -12.966 ms -1.996 7.048
Server Offset 93.94.88.51 5.727 5.727 5.727 8.914 11.648 11.648 11.648 5.921 5.921 2.084 8.668 ms -0.08498 1.687
Server Offset 96.19.94.82 0.297 0.297 2.740 5.189 7.144 7.510 7.510 4.404 7.212 1.387 5.121 ms -0.7476 4.02
Server Offset 96.245.170.99 -6.017 -5.876 -3.123 2.815 5.216 5.802 6.038 8.339 11.679 2.351 2.390 ms -1.525 5.442
Server Offset 97.107.136.23 -30.116 -1.254 -0.119 2.964 6.178 7.047 8.178 6.298 8.301 2.165 2.994 ms -2.275 34.23
Server Offset 99.28.14.242 -5.923 -5.923 -4.207 0.059 3.438 4.480 4.480 7.645 10.404 1.955 -0.022 ms -0.3342 3.88
Server Offset SHM(3) -548.313 -0.889 -0.607 -0.159 0.278 0.453 492.808 0.886 1.341 5.536 -0.157 ms -11.15 8330
Server Offset SHM(5) -6.214 -0.680 -0.543 -0.094 0.296 0.514 0.725 0.839 1.193 0.390 -0.116 ms -7.627 105.3
TDOP 0.480 0.540 0.600 0.850 1.280 1.640 2.920 0.680 1.100 0.250 0.889 2.238 15.04
Temp /dev/sda 18.000 20.000 20.000 25.000 26.000 28.000 34.000 6.000 8.000 2.334 24.211 °C
Temp LM0 27.000 28.000 30.000 34.000 40.000 43.000 53.000 10.000 15.000 2.982 34.018 °C
Temp LM1 27.000 28.000 29.000 36.000 41.000 42.000 47.000 12.000 14.000 4.034 35.174 °C
Temp LM2 0.000 0.000 19.000 32.000 45.000 47.000 48.000 26.000 47.000 10.478 28.457 °C
Temp LM3 0.000 0.000 19.000 31.000 47.000 48.000 50.000 28.000 48.000 8.167 31.486 °C
Temp LM4 0.000 0.000 0.000 33.000 47.000 48.000 55.000 47.000 48.000 14.932 27.280 °C
Temp LM5 27.000 28.000 29.000 33.000 47.000 48.000 50.000 18.000 20.000 4.683 34.266 °C
Temp LM6 0.000 30.000 31.000 34.000 44.000 45.000 45.000 13.000 15.000 3.376 35.030 °C
Temp LM7 0.000 0.000 19.000 34.000 44.000 46.000 56.000 25.000 46.000 8.239 32.810 °C
Temp LM8 27.000 28.000 28.000 32.000 40.000 41.000 47.000 12.000 13.000 3.508 32.804 °C
Temp LM9 31.000 31.000 32.000 35.000 47.000 48.000 50.000 15.000 17.000 3.643 35.725 °C
Temp ZONE0 20.000 20.000 20.000 20.000 20.000 20.000 20.000 0.000 0.000 0.000 20.000 °C
Temp ZONE1 30.000 31.000 32.000 34.000 47.000 48.000 50.000 15.000 17.000 3.773 35.070 °C
Temp ZONE2 27.000 27.000 28.000 30.000 41.000 42.000 43.000 13.000 15.000 3.725 31.382 °C
Temp ZONE3 30.000 31.000 32.000 34.000 47.000 48.000 51.000 15.000 17.000 3.772 35.083 °C
Temp ZONE4 30.000 31.000 32.000 34.000 47.000 48.000 50.000 15.000 17.000 3.773 35.070 °C
Temp ZONE5 29.000 31.000 32.000 35.000 44.000 47.000 56.000 12.000 16.000 4.121 36.286 °C
Temp ZONE6 27.000 27.000 28.000 30.000 40.000 41.000 43.000 12.000 14.000 3.058 31.077 °C
nSats 8.000 8.000 9.000 11.000 17.000 19.000 20.000 8.000 11.000 2.402 11.977 nSat 1.224 4.096
Summary as CSV file

Stats for the last 1, 7, 35, 98, 371, some days, or live gps data.

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.
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 FIsher-Pearson moment of skewness. There are other different ways to calculate Skewness Wikipedia describes Skewness best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
Kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses standard Kurtosis. There are other different ways to calculate 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".
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!