NTPsec

Dell-2018

Report generated: Sat Jul 4 14:34:04 2026 UTC
Start Time: Sat Mar 28 14:33:52 2026 UTC
End Time: Sat Jul 4 14:33:52 2026 UTC
Report Period: 98.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 -127.900 -6.472 -5.960 -0.057 0.423 2.383 116.829 6.383 8.854 2.768 -0.721 ms -10.39 598.6
Local Clock Frequency Offset -7.584 10.804 11.200 11.506 21.370 22.302 183.534 10.170 11.498 3.324 12.643 ppm 6.538 213.2

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.198 0.239 0.355 1.881 4.049 70.769 1.642 3.851 1.552 0.560 ms 23.17 736.2

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.0000 0.0039 0.0048 0.0069 0.476 1.029 60.819 0.471 1.025 0.991 0.121 ppm 31.83 1250

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 -127.900 -6.472 -5.960 -0.057 0.423 2.383 116.829 6.383 8.854 2.768 -0.721 ms -10.39 598.6

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -7.584 10.804 11.200 11.506 21.370 22.302 183.534 10.170 11.498 3.324 12.643 ppm 6.538 213.2
Temp /dev/sda 18.000 20.000 20.000 25.000 26.000 28.000 33.000 6.000 8.000 2.273 24.416 °C
Temp LM0 31.000 32.000 35.000 37.000 40.000 42.000 59.000 5.000 10.000 1.903 36.978 °C
Temp LM1 29.000 30.000 31.000 34.000 38.000 43.000 54.000 7.000 13.000 2.322 34.340 °C
Temp LM2 26.000 26.000 34.000 37.000 40.000 41.000 46.000 6.000 15.000 2.120 37.022 °C
Temp LM3 0.000 0.000 3.000 39.000 40.000 41.000 43.000 37.000 41.000 17.403 25.992 °C
Temp LM4 0.000 0.000 0.000 0.000 39.000 41.000 51.000 39.000 41.000 17.055 13.399 °C
Temp LM5 27.000 29.000 31.000 33.000 38.000 38.000 39.000 7.000 9.000 2.865 33.781 °C
Temp LM6 28.000 32.000 33.000 35.000 37.000 37.000 44.000 4.000 5.000 1.208 34.578 °C
Temp LM7 31.000 33.000 34.000 36.000 38.000 39.000 46.000 4.000 6.000 1.265 36.252 °C
Temp LM8 26.800 26.800 35.000 37.000 38.000 39.000 46.000 3.000 12.200 1.641 36.237 °C
Temp LM9 26.800 26.800 35.000 37.000 38.000 39.000 46.000 3.000 12.200 1.641 36.237 °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 26.800 26.800 34.000 36.000 38.000 38.000 46.000 4.000 11.200 1.546 35.646 °C
Temp ZONE2 29.000 29.000 32.000 37.000 38.000 38.000 38.000 6.000 9.000 2.400 35.632 °C
Temp ZONE3 30.000 32.000 34.000 36.000 38.000 43.000 54.000 4.000 11.000 1.763 35.623 °C
Temp ZONE4 26.800 26.800 34.000 36.000 38.000 38.000 46.000 4.000 11.200 1.546 35.646 °C
Temp ZONE5 30.000 31.000 32.000 36.000 41.000 42.000 58.000 9.000 11.000 2.688 36.341 °C
Temp ZONE6 27.000 30.000 31.000 32.000 37.000 38.000 44.000 6.000 8.000 2.160 33.092 °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 10.000 11.000 14.000 18.000 19.000 22.000 7.000 9.000 2.091 14.149 nSat 0.3186 2.713
TDOP 0.450 0.510 0.560 0.770 1.200 1.570 3.610 0.640 1.060 0.219 0.808 2.484 17.77

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

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 -127.900 -126.268 -9.978 1.217 6.708 13.031 14.937 16.686 139.299 24.434 -4.191 ms -4.349 20.94

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

peer offset 104.234.61.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.234.61.117 -11.180 -9.140 -3.447 1.426 6.606 12.091 16.244 10.053 21.231 3.430 1.519 ms -0.07377 5.449

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 107.172.222.7

peer offset 107.172.222.7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 107.172.222.7 -12.642 -11.375 -7.178 1.882 7.310 12.947 14.359 14.488 24.322 3.982 1.625 ms -0.7389 5.565

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 -28.570 -9.305 -0.181 3.903 6.523 8.097 13.175 6.704 17.402 2.862 3.479 ms -3.533 28.36

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 12.205.28.193

peer offset 12.205.28.193 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 12.205.28.193 -126.850 -126.850 -126.850 -114.175 6.955 6.955 6.955 133.805 133.805 46.151 -91.142 ms 1.065 2.644

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 -6.511 -6.511 -4.780 0.657 5.183 15.538 15.538 9.962 22.050 3.593 0.567 ms 1.062 6.279

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 -82.929 -82.929 -82.929 -12.037 -3.376 -3.376 -3.376 79.553 79.553 25.987 -27.375 ms -0.9053 2.457

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 139.84.137.244

peer offset 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 139.84.137.244 -76.084 -65.577 -13.776 14.532 22.795 28.795 33.775 36.571 94.372 14.402 10.474 ms -3.014 14.66

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 143.42.229.154

peer offset 143.42.229.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 143.42.229.154 -12.280 -11.918 -8.448 0.679 4.877 10.025 10.853 13.326 21.944 3.809 0.031 ms -0.9182 4.866

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 -112.597 -112.597 -112.597 -0.542 1.509 1.509 1.509 114.106 114.106 56.383 -55.610 ms 0.0001555 1.001

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 -1,991.190 -7.297 2.180 9.379 12.747 26.232 58.058 10.567 33.529 152.944 -2.874 ms -12.88 167.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 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 -119.005 -102.607 -78.625 -8.685 6.545 10.280 13.559 85.170 112.887 26.779 -18.851 ms -1.354 4.238

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

peer offset 149.248.12.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.248.12.167 -8.248 -8.248 -5.145 2.102 8.205 12.647 12.647 13.350 20.895 4.129 1.825 ms 0.01569 3.465

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 -15.182 -10.996 -7.700 0.875 6.594 11.091 14.392 14.294 22.087 3.870 0.627 ms -0.6716 5.971

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 -1,995.498 -19.186 -4.326 3.251 6.159 17.348 44.622 10.485 36.534 163.873 -10.990 ms -12 145.2

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 151.236.20.166

peer offset 151.236.20.166 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 151.236.20.166 -7.947 -5.621 -3.416 0.364 5.984 9.517 13.621 9.399 15.138 3.092 0.765 ms 0.5972 3.916

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 155.248.196.28

peer offset 155.248.196.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 155.248.196.28 -7.263 -4.833 -2.819 0.165 4.387 7.586 11.821 7.206 12.418 2.282 0.520 ms 0.7572 5.018

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 157.245.125.229

peer offset 157.245.125.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 157.245.125.229 1.618 1.618 1.618 2.114 3.912 3.912 3.912 2.294 2.294 0.986 2.548 ms 0.5751 1.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 161.35.230.200

peer offset 161.35.230.200 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 161.35.230.200 -2.730 -2.730 -1.127 1.511 390.595 395.667 395.667 391.722 398.397 147.881 68.930 ms 1.72 3.961

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 -33.205 -5.539 -1.239 5.482 8.982 11.637 16.373 10.221 17.176 3.898 4.765 ms -3.203 30.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 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 -1,990.740 -3.828 -1.053 5.787 8.818 12.008 41.636 9.871 15.836 54.668 3.802 ms -36.3 1324

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 170.187.147.56

peer offset 170.187.147.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 170.187.147.56 1.026 1.199 3.846 6.744 9.809 11.373 12.448 5.963 10.174 1.897 6.818 ms -0.2684 3.74

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 171.66.97.126

peer offset 171.66.97.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 171.66.97.126 -111.117 -111.117 -111.117 -1.864 2.857 2.857 2.857 113.973 113.973 55.954 -54.736 ms 0.002046 1.003

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

peer offset 172.233.155.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.155.39 -1.467 -1.004 0.504 3.923 6.683 9.443 9.891 6.178 10.447 1.888 3.780 ms -0.1655 3.462

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 -378.349 -377.277 -1.613 7.945 13.980 16.005 16.638 15.592 393.281 71.028 -5.439 ms -5.005 26.14

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 -384.852 -377.114 -10.309 2.206 9.952 35.580 41.762 20.261 412.695 46.143 -2.705 ms -7.84 64.55

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

peer offset 172.235.60.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.235.60.8 -1,994.828 -7.193 -2.951 1.687 6.652 8.955 47.412 9.602 16.148 100.097 -3.238 ms -19.74 391.2

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

peer offset 172.238.164.57 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.238.164.57 -20.678 -5.109 -3.388 1.693 6.481 7.573 11.018 9.869 12.682 3.241 1.724 ms -0.3793 3.926

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

peer offset 172.245.210.108 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.245.210.108 -261.506 -261.506 -251.411 0.386 170.775 173.801 173.801 422.186 435.307 82.626 -6.480 ms -0.7581 6.622

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

peer offset 173.255.230.96 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.255.230.96 -4.019 -1.915 0.365 4.658 8.077 9.189 28.541 7.712 11.104 2.614 4.581 ms 2.225 26.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 185.234.20.134

peer offset 185.234.20.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 185.234.20.134 -207.966 -198.229 8.539 43.432 54.518 222.317 228.892 45.980 420.546 43.466 39.110 ms -0.8489 21.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 192.48.105.15

peer offset 192.48.105.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.48.105.15 -38.144 -16.120 -11.322 4.337 8.624 13.335 24.385 19.946 29.455 6.098 2.898 ms -2.025 11.15

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 -1,993.360 -8.509 -3.462 4.470 7.817 12.344 390.115 11.279 20.852 70.101 1.248 ms -27.4 778.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 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 -206.226 -6.792 -4.823 -1.585 2.970 6.864 17.267 7.794 13.656 10.679 -1.881 ms -16.46 302.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 198.46.254.130

peer offset 198.46.254.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.46.254.130 -11.109 -10.105 -8.900 -0.000 6.524 48.594 50.250 15.424 58.699 6.597 0.210 ms 4.556 35.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 198.71.50.75

peer offset 198.71.50.75 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.71.50.75 -21.461 -16.971 -10.397 -4.651 -1.037 1.083 5.931 9.360 18.054 3.141 -4.906 ms -1.601 9.855

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 199.68.201.237

peer offset 199.68.201.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 199.68.201.237 -54.221 -4.457 -2.342 2.245 5.491 7.434 14.187 7.833 11.890 3.323 1.891 ms -8.342 141.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 204.2.134.173

peer offset 204.2.134.173 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.2.134.173 -330.587 -1.995 0.505 4.402 7.005 7.870 8.684 6.500 9.866 24.915 2.289 ms -13.06 173.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 206.210.192.99

peer offset 206.210.192.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 206.210.192.99 3.732 3.732 3.732 10.882 12.986 12.986 12.986 9.255 9.255 2.868 9.737 ms -0.9345 2.785

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 -30.375 -4.599 -3.528 0.644 5.660 6.592 10.469 9.189 11.191 3.484 1.079 ms -2.528 23.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 212.227.240.160

peer offset 212.227.240.160 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 212.227.240.160 -12.742 -12.742 -12.742 -3.409 1.156 1.156 1.156 13.898 13.898 4.103 -3.640 ms -1.253 3.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 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 -17.026 -11.915 -9.323 -0.727 3.365 13.045 13.185 12.689 24.960 3.711 -1.195 ms -0.3257 7.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 -50.737 -50.737 -50.737 -22.856 369.510 369.510 369.510 420.246 420.246 153.331 42.225 ms 1.636 3.702

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

peer offset 216.66.48.42 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.66.48.42 -57.714 -48.968 -41.803 -10.099 4.232 45.537 48.178 46.035 94.505 15.518 -12.901 ms 0.07764 5.238

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

peer offset 216.82.35.115 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.82.35.115 -29.297 -29.297 -9.388 -1.589 392.815 392.815 392.815 402.203 422.112 140.650 54.907 ms 1.952 4.828

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 -3.042 1.210 6.116 10.762 12.869 13.726 15.979 6.753 12.515 2.256 10.325 ms -1.928 8.756

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

peer offset 23.142.248.9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.142.248.9 -263.459 -263.459 -262.784 -5.526 168.098 168.098 168.098 430.883 431.557 135.791 -14.334 ms -0.3337 2.497

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

peer offset 23.150.41.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.150.41.122 -3.912 -0.906 1.567 5.532 9.044 10.304 12.219 7.477 11.210 2.174 5.373 ms -0.477 4.713

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 -22.902 -6.841 -4.011 7.985 11.290 27.089 32.724 15.301 33.931 6.002 6.415 ms -0.1132 6.673

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

peer offset 23.155.72.147 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.155.72.147 -392.987 -391.252 -12.441 -6.112 -0.837 1.703 7.397 11.604 392.955 61.955 -16.524 ms -5.782 34.56

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

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

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

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



Server Offset 23.159.16.194

peer offset 23.159.16.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.159.16.194 -332.773 -2.949 1.895 12.336 15.900 21.536 27.238 14.005 24.484 25.353 9.220 ms -12.89 173.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 23.161.104.133

peer offset 23.161.104.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.161.104.133 -2,049.972 -101.968 -80.336 -10.292 8.933 16.421 36.039 89.268 118.389 73.298 -20.257 ms -23.94 661.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 23.168.24.210

peer offset 23.168.24.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.168.24.210 -30.994 -9.946 -0.456 4.953 9.479 14.370 15.899 9.935 24.316 3.912 4.627 ms -3.016 28.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 23.186.168.123

peer offset 23.186.168.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.123 -18.265 -9.033 -4.573 1.968 4.196 5.440 24.970 8.768 14.473 2.913 1.183 ms -1.453 9.185

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 -336.573 -2.857 -1.290 2.156 4.173 5.028 21.753 5.462 7.885 12.191 1.436 ms -26.88 738.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 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 -114.793 -114.793 -114.793 -5.494 -0.844 -0.844 -0.844 113.950 113.950 54.847 -57.177 ms -0.005087 1.013

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 -100.937 -99.110 -94.535 -0.231 26.999 28.752 33.560 121.534 127.862 23.833 -4.843 ms -3.043 12.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.95.35.34

peer offset 23.95.35.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.95.35.34 -27.613 -6.330 -4.084 -0.692 1.519 7.411 20.501 5.603 13.742 2.639 -0.860 ms -1.428 41.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 2602:f590::23:161:104:133 (isere.sd.ysun.co)

peer offset 2602:f590::23:161:104:133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:f590::23:161:104:133 (isere.sd.ysun.co) -471.581 -385.176 -54.827 -11.476 0.126 5.242 28.182 54.953 390.419 61.385 -26.183 ms -5.774 37.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 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 -2,001.428 -123.441 -64.427 -8.775 4.087 9.142 11.849 68.513 132.582 117.993 -21.514 ms -16.19 271.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 38.45.64.130

peer offset 38.45.64.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 38.45.64.130 -257.312 -73.003 -9.597 5.725 9.142 13.153 177.823 18.739 86.156 24.534 3.845 ms -3.142 73.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 40.160.28.79

peer offset 40.160.28.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 40.160.28.79 -52.835 -52.513 -34.382 -5.004 1.626 5.643 7.374 36.008 58.156 10.906 -8.229 ms -2.157 7.89

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 -7.144 -7.144 -5.951 -0.158 3.398 3.755 3.755 9.349 10.899 2.890 -0.778 ms -0.2377 2.111

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 -46.045 -0.594 1.252 5.059 7.317 7.897 8.597 6.064 8.490 2.909 4.640 ms -9.672 161.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.55.58.103

peer offset 45.55.58.103 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.55.58.103 -110.343 -110.343 -110.343 0.562 3.360 3.360 3.360 113.703 113.703 54.930 -52.554 ms -0.005973 1.01

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

peer offset 45.63.54.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.63.54.13 -5.411 -1.284 1.511 5.531 7.546 8.410 9.171 6.035 9.693 1.905 5.168 ms -1.347 6.272

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

peer offset 45.77.126.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.77.126.122 2.520 2.520 2.520 7.490 10.132 10.132 10.132 7.613 7.613 2.779 7.072 ms -0.4913 1.881

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

peer offset 45.83.234.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.83.234.123 -92.017 -92.017 -53.358 -1.514 30.819 37.116 37.116 84.178 129.133 21.169 -7.277 ms -0.9842 5.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 47.85.203.40

peer offset 47.85.203.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 47.85.203.40 -11.482 -4.542 -0.158 5.077 10.458 14.417 15.104 10.616 18.959 3.390 5.170 ms -0.3312 5.456

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 49.12.103.123

peer offset 49.12.103.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 49.12.103.123 -104.453 -96.809 -69.563 -6.827 5.026 15.191 21.860 74.590 112.001 23.583 -15.248 ms -1.71 5.611

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

peer offset 5.161.111.190 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.111.190 -18.177 -13.919 -7.797 -3.175 1.189 3.412 7.582 8.985 17.330 3.150 -3.351 ms -0.7991 5.935

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

peer offset 5.161.65.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.65.34 -8.208 -8.208 -5.991 -2.626 391.162 391.162 391.162 397.153 399.370 139.388 55.456 ms 1.96 4.843

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

peer offset 5.161.94.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.94.12 -26.311 -6.789 -5.364 -1.781 1.988 4.296 14.347 7.351 11.084 2.473 -1.710 ms -0.7917 18.97

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 50.117.3.95

peer offset 50.117.3.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.117.3.95 -13.393 -13.270 -8.900 -1.296 1.731 4.497 6.235 10.631 17.767 3.214 -1.929 ms -1.378 5.671

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 50.218.103.254

peer offset 50.218.103.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.218.103.254 -39.877 -17.266 -8.068 0.775 5.720 46.263 49.954 13.788 63.530 7.440 0.730 ms 2.027 26.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 51.81.226.229

peer offset 51.81.226.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 51.81.226.229 -3.807 -1.522 1.150 5.163 7.606 8.830 11.602 6.456 10.352 1.992 4.926 ms -0.7831 4.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 64.251.10.152

peer offset 64.251.10.152 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.251.10.152 -9.929 -6.388 -4.004 -0.535 3.189 7.131 10.599 7.193 13.520 2.557 -0.405 ms 0.497 5.923

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

peer offset 65.182.224.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 65.182.224.39 -19.040 -5.987 -1.484 1.519 6.164 11.148 17.628 7.648 17.136 3.038 1.696 ms -0.02657 18.42

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 -4.897 -4.897 -2.203 1.449 6.846 10.883 10.883 9.048 15.780 2.958 1.749 ms 0.4925 3.551

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

peer offset 66.118.228.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.118.228.14 -333.165 -10.163 -2.631 4.084 8.349 9.848 12.691 10.980 20.011 25.449 1.791 ms -12.74 167.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 66.118.229.14

peer offset 66.118.229.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.118.229.14 -46.204 -13.396 -8.297 4.542 8.438 12.813 14.060 16.735 26.209 5.776 3.279 ms -3.792 28.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 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 -33.203 -13.840 -6.321 -1.577 2.341 5.436 13.727 8.662 19.277 3.265 -1.879 ms -1.993 17.59

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

peer offset 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.89.207.199 -132.300 -132.300 -132.300 -82.315 12.317 12.317 12.317 144.616 144.616 60.181 -69.022 ms 0.2283 1.231

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 -38.922 -5.235 -2.966 0.525 2.859 4.153 5.952 5.826 9.389 2.447 0.240 ms -7.231 113.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 72.14.182.49

peer offset 72.14.182.49 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.14.182.49 -1.532 -0.973 0.417 4.164 7.308 8.085 8.396 6.891 9.058 1.895 4.150 ms -0.3723 3.354

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

peer offset 72.14.186.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.14.186.59 -10.962 -10.962 -6.498 5.272 7.467 8.444 8.444 13.965 19.405 4.884 3.065 ms -1.172 3.134

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 -385.027 -380.946 -6.151 1.376 7.161 9.409 12.049 13.313 390.355 55.425 -6.810 ms -6.565 44.31

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

peer offset 77.37.97.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 77.37.97.124 -64.960 -64.960 -62.814 -13.281 12.547 12.582 12.582 75.362 77.541 22.383 -16.669 ms -0.5829 2.612

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

peer offset 77.42.37.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 77.42.37.85 -83.037 -83.037 -83.037 -1.405 13.595 13.595 13.595 96.633 96.633 29.560 -20.475 ms -0.8498 2.319

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 79.160.225.13

peer offset 79.160.225.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 79.160.225.13 -64.543 -64.543 -64.543 -6.827 0.842 0.842 0.842 65.386 65.386 19.265 -16.275 ms -1.272 3.416

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 83.228.206.15

peer offset 83.228.206.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 83.228.206.15 -137.287 -106.678 -85.463 -5.076 5.321 28.735 31.867 90.784 135.413 27.600 -16.729 ms -1.765 5.927

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 -1,995.690 -9.227 -2.599 3.709 6.341 11.025 51.057 8.939 20.252 126.659 -4.965 ms -15.62 245.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.



Refclock Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(0) -1,142.216 -564.225 -529.412 -140.626 -132.232 -128.952 -93.627 397.180 435.272 115.790 -178.036 ms -2.758 8.733

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(1) -1,005.833 -0.779 -0.585 -0.193 0.202 0.340 2,340.449 0.787 1.119 14.473 -0.160 ms 125.6 2.282e+04

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(3)

peer offset SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(3) -6.622 -3.354 -0.652 -0.170 0.436 0.614 0.792 1.088 3.968 0.596 -0.166 ms -4.721 36.43

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(4)

peer offset SHM(4) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(4) -161.294 -159.152 -156.877 -151.439 -146.907 -145.585 -142.438 9.970 13.567 3.040 -151.647 ms -0.2552 2.747

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(5)

peer offset SHM(5) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(5) -6.986 -3.330 -0.686 -0.171 0.413 0.591 0.760 1.099 3.921 0.607 -0.178 ms -4.609 34.92

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(1)

peer offset SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SOCK(1) -8.572 -7.005 -6.722 -5.935 -2.506 -0.741 1.134 4.216 6.265 1.322 -5.535 ms 1.864 6.508

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.000 0.000 0.959 4.705 16.552 88.041 111.550 15.593 88.041 12.440 6.937 ms 6.359 47.12

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

peer jitter 104.234.61.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.234.61.117 0.000 0.735 1.495 3.548 13.550 26.903 29.916 12.055 26.168 4.494 4.883 ms 3.04 14.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 107.172.222.7

peer jitter 107.172.222.7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 107.172.222.7 0.000 0.000 1.084 4.379 25.305 36.743 37.327 24.221 36.743 8.622 8.136 ms 1.606 4.837

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 0.714 1.150 4.505 26.091 34.413 41.318 24.940 33.698 8.433 8.402 ms 1.357 4.032

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 12.205.28.193

peer jitter 12.205.28.193 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 12.205.28.193 0.000 0.000 0.000 11.183 108.575 108.575 108.575 108.575 108.575 37.651 31.806 ms 0.9856 2.424

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 0.000 0.000 0.215 3.893 9.692 11.268 11.268 9.477 11.268 2.613 4.426 ms 0.7499 2.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 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 0.000 45.687 96.956 96.956 96.956 96.956 96.956 24.598 45.912 ms -0.1894 3.157

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 139.84.137.244

peer jitter 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.84.137.244 0.000 0.000 7.974 22.219 35.861 55.740 70.631 27.886 55.740 9.150 22.470 ms 0.8186 6.784

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 143.42.229.154

peer jitter 143.42.229.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 143.42.229.154 0.000 0.000 1.148 7.611 49.932 51.852 52.766 48.784 51.852 13.133 12.146 ms 1.725 5.461

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.000 0.000 87.784 111.447 111.447 111.447 111.447 111.447 49.774 49.877 ms 0.05641 1.077

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.842 1.241 3.979 17.508 43.753 123.164 16.267 42.911 9.251 6.136 ms 7.096 70.4

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 0.000 41.577 77.749 93.726 95.821 77.749 93.726 21.527 41.634 ms -0.03586 2.951

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

peer jitter 149.248.12.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.248.12.167 0.000 0.000 1.937 5.393 14.159 15.551 15.551 12.222 15.551 4.000 6.455 ms 0.6547 2.36

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 1.399 3.543 11.629 26.497 26.744 10.230 26.497 4.761 4.914 ms 3.113 13.79

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.606 1.171 5.169 37.680 56.441 197.074 36.509 55.835 13.496 10.350 ms 4.225 38.58

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 151.236.20.166

peer jitter 151.236.20.166 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 151.236.20.166 0.000 1.259 1.527 3.486 15.315 62.462 73.702 13.788 61.203 9.812 5.895 ms 4.933 28.97

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 155.248.196.28

peer jitter 155.248.196.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 155.248.196.28 0.000 0.589 0.940 3.258 9.816 16.282 21.738 8.876 15.693 3.024 4.022 ms 2.002 8.941

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 157.245.125.229

peer jitter 157.245.125.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 157.245.125.229 0.000 0.000 0.000 1.602 1.798 1.798 1.798 1.798 1.798 0.805 1.133 ms -0.676 1.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 161.35.230.200

peer jitter 161.35.230.200 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 161.35.230.200 0.000 0.000 0.000 1.722 4.765 5.072 5.072 4.765 5.072 1.384 2.182 ms 0.4533 2.424

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.000 1.190 3.508 15.735 89.491 91.781 14.545 89.491 12.955 6.347 ms 5.836 37.66

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

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

RMS Jitter is field 8 in the peerstats log file.



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.562 1.152 3.313 15.781 29.826 79.186 14.630 29.264 6.392 4.936 ms 5.802 52.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 170.187.147.56

peer jitter 170.187.147.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 170.187.147.56 0.000 0.000 0.910 2.839 12.056 56.163 57.472 11.146 56.163 7.201 5.030 ms 4.95 33.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 171.66.97.126

peer jitter 171.66.97.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 171.66.97.126 0.000 0.000 0.000 87.962 108.804 108.804 108.804 108.804 108.804 49.147 49.518 ms 0.04453 1.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 172.233.155.39

peer jitter 172.233.155.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.155.39 0.000 0.000 0.995 2.783 14.298 19.870 19.951 13.303 19.870 3.907 3.826 ms 2.866 11.26

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.000 1.365 4.096 9.848 14.966 20.475 8.483 14.966 3.089 4.974 ms 1.756 8.373

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 1.222 4.204 62.081 90.303 110.008 60.859 90.303 18.827 11.234 ms 3.105 12.68

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

peer jitter 172.235.60.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.235.60.8 0.000 0.773 1.154 3.472 14.471 27.652 74.064 13.318 26.879 5.681 4.934 ms 5.261 44.65

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

peer jitter 172.238.164.57 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.238.164.57 0.000 0.651 1.077 3.190 12.196 22.320 98.321 11.119 21.670 6.582 4.553 ms 9.34 119.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 172.245.210.108

peer jitter 172.245.210.108 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.245.210.108 0.000 0.000 0.000 3.191 187.963 208.084 208.084 187.963 208.084 52.818 21.295 ms 2.724 8.749

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

peer jitter 173.255.230.96 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.255.230.96 0.000 0.000 1.050 3.510 18.774 67.403 67.650 17.724 67.403 9.020 6.895 ms 3.984 24.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 185.234.20.134

peer jitter 185.234.20.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 185.234.20.134 0.000 0.000 1.496 40.867 79.288 185.571 206.604 77.792 185.571 30.174 41.957 ms 2.461 13.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 192.48.105.15

peer jitter 192.48.105.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.48.105.15 0.000 8.231 15.837 32.614 63.290 81.489 85.309 47.453 73.258 15.919 35.883 ms 0.6456 3.005

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.770 1.192 3.434 12.895 26.428 398.640 11.703 25.657 8.060 4.946 ms 20.91 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 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 0.755 1.178 3.161 12.596 31.040 170.481 11.418 30.284 8.714 4.938 ms 12.32 205.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 198.46.254.130

peer jitter 198.46.254.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.46.254.130 0.000 0.000 0.999 3.685 17.434 36.558 41.450 16.435 36.558 6.279 5.702 ms 2.802 13.08

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

peer jitter 198.71.50.75 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.71.50.75 0.000 1.525 3.734 23.735 49.077 91.787 92.484 45.343 90.262 15.505 24.891 ms 1.557 7.619

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 199.68.201.237

peer jitter 199.68.201.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 199.68.201.237 0.000 1.108 1.497 4.379 13.223 24.575 59.461 11.726 23.467 4.609 5.470 ms 4.52 39.75

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.2.134.173

peer jitter 204.2.134.173 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.2.134.173 0.000 0.737 1.155 3.937 11.016 25.193 273.013 9.861 24.456 16.748 5.825 ms 14.91 236.2

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 206.210.192.99

peer jitter 206.210.192.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 206.210.192.99 0.000 0.000 0.000 2.291 4.456 4.456 4.456 4.456 4.456 1.344 2.379 ms 0.04821 2.401

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.644 1.070 3.271 17.237 42.327 53.244 16.167 41.683 6.708 5.210 ms 4.222 25

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 212.227.240.160

peer jitter 212.227.240.160 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 212.227.240.160 0.000 0.000 0.000 5.333 13.898 13.898 13.898 13.898 13.898 4.106 5.460 ms 0.8261 3.059

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 1.118 3.126 13.486 18.864 19.152 12.368 18.864 3.617 4.133 ms 2.295 8.497

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 0.000 2.191 28.627 28.627 28.627 28.627 28.627 10.430 9.269 ms 0.6825 1.75

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

peer jitter 216.66.48.42 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.66.48.42 0.000 0.000 2.641 25.978 59.408 65.378 72.744 56.767 65.378 15.554 27.857 ms 0.5488 2.961

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

peer jitter 216.82.35.115 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.82.35.115 0.000 0.000 0.000 17.805 45.013 45.013 45.013 45.013 45.013 13.064 18.801 ms 0.1825 1.945

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.713 1.166 4.681 17.883 23.569 194.491 16.717 22.855 8.023 7.030 ms 11.93 270.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.142.248.9

peer jitter 23.142.248.9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.142.248.9 0.000 0.000 0.000 1.910 223.573 223.573 223.573 223.573 223.573 80.245 51.522 ms 1.16 2.531

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

peer jitter 23.150.41.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.150.41.122 0.000 0.796 1.190 3.307 13.542 32.912 36.946 12.352 32.116 4.892 4.685 ms 3.705 20.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.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.009 1.430 7.025 37.263 61.594 89.122 35.833 61.586 12.962 11.880 ms 2.6 12.26

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

peer jitter 23.155.72.147 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.155.72.147 0.000 0.000 1.155 3.406 36.728 38.286 43.030 35.574 38.286 9.343 6.981 ms 2.473 8.282

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

peer jitter 23.159.16.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.159.16.194 0.000 1.045 2.467 16.809 27.390 32.850 58.053 24.924 31.805 7.442 16.306 ms 0.07263 4.257

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

peer jitter 23.161.104.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.161.104.133 0.000 0.000 13.856 45.509 77.776 97.826 152.099 63.921 97.826 19.599 46.225 ms 0.3163 4.847

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

peer jitter 23.168.24.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.168.24.210 0.000 0.000 1.329 6.287 36.844 40.675 48.121 35.515 40.675 10.711 11.315 ms 1.333 4.184

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

peer jitter 23.186.168.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.123 0.000 0.755 1.146 3.302 13.804 22.011 69.314 12.658 21.256 5.089 4.656 ms 5.393 51.22

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.760 1.194 3.478 12.503 23.541 68.977 11.309 22.781 4.874 4.687 ms 5.05 44.55

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.000 0.000 86.127 106.510 106.510 106.510 106.510 106.510 46.232 50.498 ms 0.03958 1.076

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 0.996 3.875 94.456 98.238 99.122 93.460 98.238 24.442 12.180 ms 2.896 9.894

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

peer jitter 23.95.35.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.95.35.34 0.520 0.923 1.251 3.906 18.822 43.808 53.916 17.571 42.885 7.013 5.962 ms 3.75 20.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 2602:f590::23:161:104:133 (isere.sd.ysun.co)

peer jitter 2602:f590::23:161:104:133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:f590::23:161:104:133 (isere.sd.ysun.co) 0.000 0.000 7.038 40.173 63.744 78.005 83.945 56.706 78.005 17.076 39.669 ms -0.2518 2.788

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 16.821 50.006 92.451 102.838 108.993 75.629 102.838 23.719 52.229 ms 0.0375 2.526

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

peer jitter 38.45.64.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 38.45.64.130 0.000 0.000 7.571 29.546 64.425 166.492 263.171 56.855 166.492 23.853 34.485 ms 4.369 34.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 40.160.28.79

peer jitter 40.160.28.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 40.160.28.79 0.000 1.801 6.063 24.301 44.703 52.503 53.020 38.640 50.702 10.983 25.335 ms 0.2798 2.796

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.000 1.096 3.713 6.087 7.846 7.846 4.992 7.846 1.629 3.721 ms 0.1742 3.376

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.840 1.364 3.976 13.560 25.417 53.423 12.196 24.576 5.132 5.246 ms 4.231 29.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 45.55.58.103

peer jitter 45.55.58.103 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.55.58.103 0.000 0.000 0.000 85.863 108.041 108.041 108.041 108.041 108.041 46.518 50.518 ms 0.04903 1.088

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

peer jitter 45.63.54.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.63.54.13 0.000 0.703 1.053 3.308 11.454 24.347 79.311 10.401 23.644 7.089 4.708 ms 7.246 66.94

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.77.126.122

peer jitter 45.77.126.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.77.126.122 0.000 0.000 0.000 4.330 5.704 5.704 5.704 5.704 5.704 1.979 3.654 ms -0.9831 2.587

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.83.234.123

peer jitter 45.83.234.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.83.234.123 0.000 0.000 1.495 39.106 122.949 180.284 180.284 121.454 180.284 34.900 47.542 ms 1.947 8.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 47.85.203.40

peer jitter 47.85.203.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 47.85.203.40 0.000 0.848 1.598 5.948 28.308 42.271 42.446 26.710 41.422 9.054 9.477 ms 1.937 6.968

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 49.12.103.123

peer jitter 49.12.103.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 49.12.103.123 0.000 0.000 8.494 52.028 95.543 105.971 112.348 87.049 105.971 24.109 52.611 ms -0.002461 2.709

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

peer jitter 5.161.111.190 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.111.190 0.000 0.887 1.554 4.668 21.349 37.015 37.112 19.795 36.128 7.669 8.606 ms 1.358 4.999

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

peer jitter 5.161.65.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.65.34 0.000 0.000 0.000 4.473 17.184 17.184 17.184 17.184 17.184 4.658 5.050 ms 0.938 3.169

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

peer jitter 5.161.94.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.94.12 0.000 0.726 1.062 4.573 30.285 60.359 81.956 29.223 59.633 11.411 9.222 ms 2.922 14.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 50.117.3.95

peer jitter 50.117.3.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.117.3.95 0.000 0.000 0.710 3.258 22.835 29.378 30.209 22.125 29.378 8.114 8.046 ms 1.002 2.77

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 50.218.103.254

peer jitter 50.218.103.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.218.103.254 0.000 0.000 1.605 10.036 31.573 43.704 46.371 29.968 43.704 9.984 12.026 ms 1.256 4.602

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 51.81.226.229

peer jitter 51.81.226.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 51.81.226.229 0.000 0.713 1.057 3.022 15.578 21.479 24.923 14.521 20.766 4.163 4.325 ms 2.659 10.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 64.251.10.152

peer jitter 64.251.10.152 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.251.10.152 0.000 0.662 1.310 2.937 14.783 23.548 24.751 13.473 22.886 4.514 4.810 ms 2.064 7.271

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

peer jitter 65.182.224.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 65.182.224.39 0.000 0.000 0.862 2.239 8.881 15.286 19.717 8.019 15.286 2.933 3.202 ms 2.506 10.58

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.000 2.004 3.445 7.058 10.501 10.501 5.054 10.501 1.855 3.928 ms 1.023 4.59

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

peer jitter 66.118.228.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.118.228.14 0.000 1.929 2.939 6.604 16.232 40.531 64.782 13.293 38.601 6.085 7.807 ms 4.869 36.09

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

peer jitter 66.118.229.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.118.229.14 0.000 12.905 17.541 43.034 69.623 82.562 91.203 52.082 69.657 15.534 43.735 ms 0.08592 3.136

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 1.125 4.412 16.989 25.689 29.849 50.963 21.277 28.725 6.222 16.635 ms -0.06841 4.509

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

peer jitter 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.89.207.199 0.000 0.000 0.000 5.339 120.778 120.778 120.778 120.778 120.778 35.927 22.760 ms 1.778 4.812

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.952 1.441 4.280 9.976 22.131 97.381 8.535 21.179 6.351 5.140 ms 10.66 147.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 72.14.182.49

peer jitter 72.14.182.49 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.14.182.49 0.000 0.852 1.163 3.269 16.589 22.688 25.413 15.425 21.836 4.550 4.656 ms 2.49 9.16

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

peer jitter 72.14.186.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.14.186.59 0.000 0.000 0.605 2.607 7.822 13.480 13.480 7.218 13.480 2.890 3.838 ms 0.9825 3.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 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.137 4.631 53.379 61.483 80.745 52.243 61.483 15.185 9.547 ms 2.874 10.22

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

peer jitter 77.37.97.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.37.97.124 0.000 0.000 0.000 37.688 62.650 66.768 66.768 62.650 66.768 21.573 32.407 ms -0.3942 1.864

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

peer jitter 77.42.37.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.42.37.85 0.000 0.000 0.000 33.065 79.065 79.065 79.065 79.065 79.065 26.327 27.862 ms 0.2787 1.786

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 79.160.225.13

peer jitter 79.160.225.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 79.160.225.13 0.000 0.000 0.000 42.736 61.519 61.519 61.519 61.519 61.519 17.606 39.671 ms -1.383 3.946

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 83.228.206.15

peer jitter 83.228.206.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 83.228.206.15 0.000 0.000 26.174 58.345 95.964 116.045 155.978 69.791 116.045 22.450 58.259 ms 0.1172 4.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 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.000 0.828 1.266 3.849 19.898 76.766 200.156 18.632 75.938 14.712 7.068 ms 8.068 83.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.



Refclock RMS Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(0) 0.000 0.670 1.005 2.833 280.963 308.021 775.273 279.958 307.351 104.987 53.807 ms 1.598 3.654

The RMS Jitter of a local refclock. 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.



Refclock RMS Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(1) 0.000 0.130 0.168 0.281 0.482 0.595 1,000.217 0.314 0.465 9.139 0.431 ms 79.39 6977

The RMS Jitter of a local refclock. 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.



Refclock RMS Jitter SHM(3)

peer jitter SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(3) 0.000 133.517 181.281 304.326 498.521 600.190 1,315.528 317.240 466.673 105.124 321.352 µs 1.254 9.155

The RMS Jitter of a local refclock. 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.



Refclock RMS Jitter SHM(4)

peer jitter SHM(4) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(4) 0.000 0.462 0.715 1.781 4.115 5.613 9.498 3.400 5.151 1.084 2.018 ms 1.439 6.41

The RMS Jitter of a local refclock. 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.



Refclock RMS Jitter SHM(5)

peer jitter SHM(5) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(5) 0.000 113.019 173.172 305.621 513.760 609.838 1,715.353 340.588 496.819 114.363 324.731 µs 1.861 16.26

The RMS Jitter of a local refclock. 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.



Refclock RMS Jitter SOCK(1)

peer jitter SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SOCK(1) 0.000 0.138 0.186 0.343 0.746 1.197 4.136 0.560 1.059 0.228 0.394 ms 5.204 60.15

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -7.584 10.804 11.200 11.506 21.370 22.302 183.534 10.170 11.498 3.324 12.643 ppm 6.538 213.2
Local Clock Time Offset -127.900 -6.472 -5.960 -0.057 0.423 2.383 116.829 6.383 8.854 2.768 -0.721 ms -10.39 598.6
Local RMS Frequency Jitter 0.0000 0.0039 0.0048 0.0069 0.476 1.029 60.819 0.471 1.025 0.991 0.121 ppm 31.83 1250
Local RMS Time Jitter 0.000 0.198 0.239 0.355 1.881 4.049 70.769 1.642 3.851 1.552 0.560 ms 23.17 736.2
Refclock Offset SHM(0) -1,142.216 -564.225 -529.412 -140.626 -132.232 -128.952 -93.627 397.180 435.272 115.790 -178.036 ms -2.758 8.733
Refclock Offset SHM(1) -1,005.833 -0.779 -0.585 -0.193 0.202 0.340 2,340.449 0.787 1.119 14.473 -0.160 ms 125.6 2.282e+04
Refclock Offset SHM(3) -6.622 -3.354 -0.652 -0.170 0.436 0.614 0.792 1.088 3.968 0.596 -0.166 ms -4.721 36.43
Refclock Offset SHM(4) -161.294 -159.152 -156.877 -151.439 -146.907 -145.585 -142.438 9.970 13.567 3.040 -151.647 ms -0.2552 2.747
Refclock Offset SHM(5) -6.986 -3.330 -0.686 -0.171 0.413 0.591 0.760 1.099 3.921 0.607 -0.178 ms -4.609 34.92
Refclock Offset SOCK(1) -8.572 -7.005 -6.722 -5.935 -2.506 -0.741 1.134 4.216 6.265 1.322 -5.535 ms 1.864 6.508
Refclock RMS Jitter SHM(0) 0.000 0.670 1.005 2.833 280.963 308.021 775.273 279.958 307.351 104.987 53.807 ms 1.598 3.654
Refclock RMS Jitter SHM(1) 0.000 0.130 0.168 0.281 0.482 0.595 1,000.217 0.314 0.465 9.139 0.431 ms 79.39 6977
Refclock RMS Jitter SHM(3) 0.000 133.517 181.281 304.326 498.521 600.190 1,315.528 317.240 466.673 105.124 321.352 µs 1.254 9.155
Refclock RMS Jitter SHM(4) 0.000 0.462 0.715 1.781 4.115 5.613 9.498 3.400 5.151 1.084 2.018 ms 1.439 6.41
Refclock RMS Jitter SHM(5) 0.000 113.019 173.172 305.621 513.760 609.838 1,715.353 340.588 496.819 114.363 324.731 µs 1.861 16.26
Refclock RMS Jitter SOCK(1) 0.000 0.138 0.186 0.343 0.746 1.197 4.136 0.560 1.059 0.228 0.394 ms 5.204 60.15
Server Jitter 104.131.155.175 0.000 0.000 0.959 4.705 16.552 88.041 111.550 15.593 88.041 12.440 6.937 ms 6.359 47.12
Server Jitter 104.234.61.117 0.000 0.735 1.495 3.548 13.550 26.903 29.916 12.055 26.168 4.494 4.883 ms 3.04 14.17
Server Jitter 107.172.222.7 0.000 0.000 1.084 4.379 25.305 36.743 37.327 24.221 36.743 8.622 8.136 ms 1.606 4.837
Server Jitter 108.61.215.221 0.000 0.714 1.150 4.505 26.091 34.413 41.318 24.940 33.698 8.433 8.402 ms 1.357 4.032
Server Jitter 12.205.28.193 0.000 0.000 0.000 11.183 108.575 108.575 108.575 108.575 108.575 37.651 31.806 ms 0.9856 2.424
Server Jitter 134.215.155.177 0.000 0.000 0.215 3.893 9.692 11.268 11.268 9.477 11.268 2.613 4.426 ms 0.7499 2.88
Server Jitter 136.244.88.170 0.000 0.000 0.000 45.687 96.956 96.956 96.956 96.956 96.956 24.598 45.912 ms -0.1894 3.157
Server Jitter 139.84.137.244 0.000 0.000 7.974 22.219 35.861 55.740 70.631 27.886 55.740 9.150 22.470 ms 0.8186 6.784
Server Jitter 143.42.229.154 0.000 0.000 1.148 7.611 49.932 51.852 52.766 48.784 51.852 13.133 12.146 ms 1.725 5.461
Server Jitter 144.202.0.197 0.000 0.000 0.000 87.784 111.447 111.447 111.447 111.447 111.447 49.774 49.877 ms 0.05641 1.077
Server Jitter 144.202.66.214 0.000 0.842 1.241 3.979 17.508 43.753 123.164 16.267 42.911 9.251 6.136 ms 7.096 70.4
Server Jitter 147.88.195.53 0.000 0.000 0.000 41.577 77.749 93.726 95.821 77.749 93.726 21.527 41.634 ms -0.03586 2.951
Server Jitter 149.248.12.167 0.000 0.000 1.937 5.393 14.159 15.551 15.551 12.222 15.551 4.000 6.455 ms 0.6547 2.36
Server Jitter 149.28.200.179 0.000 0.000 1.399 3.543 11.629 26.497 26.744 10.230 26.497 4.761 4.914 ms 3.113 13.79
Server Jitter 149.28.61.105 0.000 0.606 1.171 5.169 37.680 56.441 197.074 36.509 55.835 13.496 10.350 ms 4.225 38.58
Server Jitter 151.236.20.166 0.000 1.259 1.527 3.486 15.315 62.462 73.702 13.788 61.203 9.812 5.895 ms 4.933 28.97
Server Jitter 155.248.196.28 0.000 0.589 0.940 3.258 9.816 16.282 21.738 8.876 15.693 3.024 4.022 ms 2.002 8.941
Server Jitter 157.245.125.229 0.000 0.000 0.000 1.602 1.798 1.798 1.798 1.798 1.798 0.805 1.133 ms -0.676 1.5
Server Jitter 161.35.230.200 0.000 0.000 0.000 1.722 4.765 5.072 5.072 4.765 5.072 1.384 2.182 ms 0.4533 2.424
Server Jitter 162.159.200.1 0.000 0.000 1.190 3.508 15.735 89.491 91.781 14.545 89.491 12.955 6.347 ms 5.836 37.66
Server Jitter 162.159.200.123 0.000 0.562 1.152 3.313 15.781 29.826 79.186 14.630 29.264 6.392 4.936 ms 5.802 52.67
Server Jitter 170.187.147.56 0.000 0.000 0.910 2.839 12.056 56.163 57.472 11.146 56.163 7.201 5.030 ms 4.95 33.37
Server Jitter 171.66.97.126 0.000 0.000 0.000 87.962 108.804 108.804 108.804 108.804 108.804 49.147 49.518 ms 0.04453 1.06
Server Jitter 172.233.155.39 0.000 0.000 0.995 2.783 14.298 19.870 19.951 13.303 19.870 3.907 3.826 ms 2.866 11.26
Server Jitter 172.234.25.10 0.000 0.000 1.365 4.096 9.848 14.966 20.475 8.483 14.966 3.089 4.974 ms 1.756 8.373
Server Jitter 172.234.37.140 0.000 0.000 1.222 4.204 62.081 90.303 110.008 60.859 90.303 18.827 11.234 ms 3.105 12.68
Server Jitter 172.235.60.8 0.000 0.773 1.154 3.472 14.471 27.652 74.064 13.318 26.879 5.681 4.934 ms 5.261 44.65
Server Jitter 172.238.164.57 0.000 0.651 1.077 3.190 12.196 22.320 98.321 11.119 21.670 6.582 4.553 ms 9.34 119.8
Server Jitter 172.245.210.108 0.000 0.000 0.000 3.191 187.963 208.084 208.084 187.963 208.084 52.818 21.295 ms 2.724 8.749
Server Jitter 173.255.230.96 0.000 0.000 1.050 3.510 18.774 67.403 67.650 17.724 67.403 9.020 6.895 ms 3.984 24.19
Server Jitter 185.234.20.134 0.000 0.000 1.496 40.867 79.288 185.571 206.604 77.792 185.571 30.174 41.957 ms 2.461 13.31
Server Jitter 192.48.105.15 0.000 8.231 15.837 32.614 63.290 81.489 85.309 47.453 73.258 15.919 35.883 ms 0.6456 3.005
Server Jitter 194.0.5.123 0.000 0.770 1.192 3.434 12.895 26.428 398.640 11.703 25.657 8.060 4.946 ms 20.91 822
Server Jitter 198.137.202.56 0.000 0.755 1.178 3.161 12.596 31.040 170.481 11.418 30.284 8.714 4.938 ms 12.32 205.7
Server Jitter 198.46.254.130 0.000 0.000 0.999 3.685 17.434 36.558 41.450 16.435 36.558 6.279 5.702 ms 2.802 13.08
Server Jitter 198.71.50.75 0.000 1.525 3.734 23.735 49.077 91.787 92.484 45.343 90.262 15.505 24.891 ms 1.557 7.619
Server Jitter 199.68.201.237 0.000 1.108 1.497 4.379 13.223 24.575 59.461 11.726 23.467 4.609 5.470 ms 4.52 39.75
Server Jitter 204.2.134.173 0.000 0.737 1.155 3.937 11.016 25.193 273.013 9.861 24.456 16.748 5.825 ms 14.91 236.2
Server Jitter 206.210.192.99 0.000 0.000 0.000 2.291 4.456 4.456 4.456 4.456 4.456 1.344 2.379 ms 0.04821 2.401
Server Jitter 209.177.158.85 0.000 0.644 1.070 3.271 17.237 42.327 53.244 16.167 41.683 6.708 5.210 ms 4.222 25
Server Jitter 212.227.240.160 0.000 0.000 0.000 5.333 13.898 13.898 13.898 13.898 13.898 4.106 5.460 ms 0.8261 3.059
Server Jitter 216.229.4.66 0.000 0.000 1.118 3.126 13.486 18.864 19.152 12.368 18.864 3.617 4.133 ms 2.295 8.497
Server Jitter 216.250.115.174 0.000 0.000 0.000 2.191 28.627 28.627 28.627 28.627 28.627 10.430 9.269 ms 0.6825 1.75
Server Jitter 216.66.48.42 0.000 0.000 2.641 25.978 59.408 65.378 72.744 56.767 65.378 15.554 27.857 ms 0.5488 2.961
Server Jitter 216.82.35.115 0.000 0.000 0.000 17.805 45.013 45.013 45.013 45.013 45.013 13.064 18.801 ms 0.1825 1.945
Server Jitter 23.142.248.8 0.000 0.713 1.166 4.681 17.883 23.569 194.491 16.717 22.855 8.023 7.030 ms 11.93 270.8
Server Jitter 23.142.248.9 0.000 0.000 0.000 1.910 223.573 223.573 223.573 223.573 223.573 80.245 51.522 ms 1.16 2.531
Server Jitter 23.150.41.122 0.000 0.796 1.190 3.307 13.542 32.912 36.946 12.352 32.116 4.892 4.685 ms 3.705 20.28
Server Jitter 23.150.41.123 0.000 0.009 1.430 7.025 37.263 61.594 89.122 35.833 61.586 12.962 11.880 ms 2.6 12.26
Server Jitter 23.155.72.147 0.000 0.000 1.155 3.406 36.728 38.286 43.030 35.574 38.286 9.343 6.981 ms 2.473 8.282
Server Jitter 23.159.16.194 0.000 1.045 2.467 16.809 27.390 32.850 58.053 24.924 31.805 7.442 16.306 ms 0.07263 4.257
Server Jitter 23.161.104.133 0.000 0.000 13.856 45.509 77.776 97.826 152.099 63.921 97.826 19.599 46.225 ms 0.3163 4.847
Server Jitter 23.168.24.210 0.000 0.000 1.329 6.287 36.844 40.675 48.121 35.515 40.675 10.711 11.315 ms 1.333 4.184
Server Jitter 23.186.168.123 0.000 0.755 1.146 3.302 13.804 22.011 69.314 12.658 21.256 5.089 4.656 ms 5.393 51.22
Server Jitter 23.186.168.125 0.000 0.760 1.194 3.478 12.503 23.541 68.977 11.309 22.781 4.874 4.687 ms 5.05 44.55
Server Jitter 23.186.168.126 0.000 0.000 0.000 86.127 106.510 106.510 106.510 106.510 106.510 46.232 50.498 ms 0.03958 1.076
Server Jitter 23.186.168.129 0.000 0.000 0.996 3.875 94.456 98.238 99.122 93.460 98.238 24.442 12.180 ms 2.896 9.894
Server Jitter 23.95.35.34 0.520 0.923 1.251 3.906 18.822 43.808 53.916 17.571 42.885 7.013 5.962 ms 3.75 20.81
Server Jitter 2602:f590::23:161:104:133 (isere.sd.ysun.co) 0.000 0.000 7.038 40.173 63.744 78.005 83.945 56.706 78.005 17.076 39.669 ms -0.2518 2.788
Server Jitter 34.147.28.4 0.000 0.000 16.821 50.006 92.451 102.838 108.993 75.629 102.838 23.719 52.229 ms 0.0375 2.526
Server Jitter 38.45.64.130 0.000 0.000 7.571 29.546 64.425 166.492 263.171 56.855 166.492 23.853 34.485 ms 4.369 34.53
Server Jitter 40.160.28.79 0.000 1.801 6.063 24.301 44.703 52.503 53.020 38.640 50.702 10.983 25.335 ms 0.2798 2.796
Server Jitter 44.190.5.123 0.000 0.000 1.096 3.713 6.087 7.846 7.846 4.992 7.846 1.629 3.721 ms 0.1742 3.376
Server Jitter 45.33.53.84 0.000 0.840 1.364 3.976 13.560 25.417 53.423 12.196 24.576 5.132 5.246 ms 4.231 29.9
Server Jitter 45.55.58.103 0.000 0.000 0.000 85.863 108.041 108.041 108.041 108.041 108.041 46.518 50.518 ms 0.04903 1.088
Server Jitter 45.63.54.13 0.000 0.703 1.053 3.308 11.454 24.347 79.311 10.401 23.644 7.089 4.708 ms 7.246 66.94
Server Jitter 45.77.126.122 0.000 0.000 0.000 4.330 5.704 5.704 5.704 5.704 5.704 1.979 3.654 ms -0.9831 2.587
Server Jitter 45.83.234.123 0.000 0.000 1.495 39.106 122.949 180.284 180.284 121.454 180.284 34.900 47.542 ms 1.947 8.067
Server Jitter 47.85.203.40 0.000 0.848 1.598 5.948 28.308 42.271 42.446 26.710 41.422 9.054 9.477 ms 1.937 6.968
Server Jitter 49.12.103.123 0.000 0.000 8.494 52.028 95.543 105.971 112.348 87.049 105.971 24.109 52.611 ms -0.002461 2.709
Server Jitter 5.161.111.190 0.000 0.887 1.554 4.668 21.349 37.015 37.112 19.795 36.128 7.669 8.606 ms 1.358 4.999
Server Jitter 5.161.65.34 0.000 0.000 0.000 4.473 17.184 17.184 17.184 17.184 17.184 4.658 5.050 ms 0.938 3.169
Server Jitter 5.161.94.12 0.000 0.726 1.062 4.573 30.285 60.359 81.956 29.223 59.633 11.411 9.222 ms 2.922 14.51
Server Jitter 50.117.3.95 0.000 0.000 0.710 3.258 22.835 29.378 30.209 22.125 29.378 8.114 8.046 ms 1.002 2.77
Server Jitter 50.218.103.254 0.000 0.000 1.605 10.036 31.573 43.704 46.371 29.968 43.704 9.984 12.026 ms 1.256 4.602
Server Jitter 51.81.226.229 0.000 0.713 1.057 3.022 15.578 21.479 24.923 14.521 20.766 4.163 4.325 ms 2.659 10.38
Server Jitter 64.251.10.152 0.000 0.662 1.310 2.937 14.783 23.548 24.751 13.473 22.886 4.514 4.810 ms 2.064 7.271
Server Jitter 65.182.224.39 0.000 0.000 0.862 2.239 8.881 15.286 19.717 8.019 15.286 2.933 3.202 ms 2.506 10.58
Server Jitter 65.182.224.60 0.000 0.000 2.004 3.445 7.058 10.501 10.501 5.054 10.501 1.855 3.928 ms 1.023 4.59
Server Jitter 66.118.228.14 0.000 1.929 2.939 6.604 16.232 40.531 64.782 13.293 38.601 6.085 7.807 ms 4.869 36.09
Server Jitter 66.118.229.14 0.000 12.905 17.541 43.034 69.623 82.562 91.203 52.082 69.657 15.534 43.735 ms 0.08592 3.136
Server Jitter 67.217.246.204 0.000 1.125 4.412 16.989 25.689 29.849 50.963 21.277 28.725 6.222 16.635 ms -0.06841 4.509
Server Jitter 69.89.207.199 0.000 0.000 0.000 5.339 120.778 120.778 120.778 120.778 120.778 35.927 22.760 ms 1.778 4.812
Server Jitter 69.89.207.99 0.000 0.952 1.441 4.280 9.976 22.131 97.381 8.535 21.179 6.351 5.140 ms 10.66 147.3
Server Jitter 72.14.182.49 0.000 0.852 1.163 3.269 16.589 22.688 25.413 15.425 21.836 4.550 4.656 ms 2.49 9.16
Server Jitter 72.14.186.59 0.000 0.000 0.605 2.607 7.822 13.480 13.480 7.218 13.480 2.890 3.838 ms 0.9825 3.827
Server Jitter 73.185.182.209 0.000 0.000 1.137 4.631 53.379 61.483 80.745 52.243 61.483 15.185 9.547 ms 2.874 10.22
Server Jitter 77.37.97.124 0.000 0.000 0.000 37.688 62.650 66.768 66.768 62.650 66.768 21.573 32.407 ms -0.3942 1.864
Server Jitter 77.42.37.85 0.000 0.000 0.000 33.065 79.065 79.065 79.065 79.065 79.065 26.327 27.862 ms 0.2787 1.786
Server Jitter 79.160.225.13 0.000 0.000 0.000 42.736 61.519 61.519 61.519 61.519 61.519 17.606 39.671 ms -1.383 3.946
Server Jitter 83.228.206.15 0.000 0.000 26.174 58.345 95.964 116.045 155.978 69.791 116.045 22.450 58.259 ms 0.1172 4.217
Server Jitter 99.28.14.242 0.000 0.828 1.266 3.849 19.898 76.766 200.156 18.632 75.938 14.712 7.068 ms 8.068 83.06
Server Offset 104.131.155.175 -127.900 -126.268 -9.978 1.217 6.708 13.031 14.937 16.686 139.299 24.434 -4.191 ms -4.349 20.94
Server Offset 104.234.61.117 -11.180 -9.140 -3.447 1.426 6.606 12.091 16.244 10.053 21.231 3.430 1.519 ms -0.07377 5.449
Server Offset 107.172.222.7 -12.642 -11.375 -7.178 1.882 7.310 12.947 14.359 14.488 24.322 3.982 1.625 ms -0.7389 5.565
Server Offset 108.61.215.221 -28.570 -9.305 -0.181 3.903 6.523 8.097 13.175 6.704 17.402 2.862 3.479 ms -3.533 28.36
Server Offset 12.205.28.193 -126.850 -126.850 -126.850 -114.175 6.955 6.955 6.955 133.805 133.805 46.151 -91.142 ms 1.065 2.644
Server Offset 134.215.155.177 -6.511 -6.511 -4.780 0.657 5.183 15.538 15.538 9.962 22.050 3.593 0.567 ms 1.062 6.279
Server Offset 136.244.88.170 -82.929 -82.929 -82.929 -12.037 -3.376 -3.376 -3.376 79.553 79.553 25.987 -27.375 ms -0.9053 2.457
Server Offset 139.84.137.244 -76.084 -65.577 -13.776 14.532 22.795 28.795 33.775 36.571 94.372 14.402 10.474 ms -3.014 14.66
Server Offset 143.42.229.154 -12.280 -11.918 -8.448 0.679 4.877 10.025 10.853 13.326 21.944 3.809 0.031 ms -0.9182 4.866
Server Offset 144.202.0.197 -112.597 -112.597 -112.597 -0.542 1.509 1.509 1.509 114.106 114.106 56.383 -55.610 ms 0.0001555 1.001
Server Offset 144.202.66.214 -1,991.190 -7.297 2.180 9.379 12.747 26.232 58.058 10.567 33.529 152.944 -2.874 ms -12.88 167.1
Server Offset 147.88.195.53 -119.005 -102.607 -78.625 -8.685 6.545 10.280 13.559 85.170 112.887 26.779 -18.851 ms -1.354 4.238
Server Offset 149.248.12.167 -8.248 -8.248 -5.145 2.102 8.205 12.647 12.647 13.350 20.895 4.129 1.825 ms 0.01569 3.465
Server Offset 149.28.200.179 -15.182 -10.996 -7.700 0.875 6.594 11.091 14.392 14.294 22.087 3.870 0.627 ms -0.6716 5.971
Server Offset 149.28.61.105 -1,995.498 -19.186 -4.326 3.251 6.159 17.348 44.622 10.485 36.534 163.873 -10.990 ms -12 145.2
Server Offset 151.236.20.166 -7.947 -5.621 -3.416 0.364 5.984 9.517 13.621 9.399 15.138 3.092 0.765 ms 0.5972 3.916
Server Offset 155.248.196.28 -7.263 -4.833 -2.819 0.165 4.387 7.586 11.821 7.206 12.418 2.282 0.520 ms 0.7572 5.018
Server Offset 157.245.125.229 1.618 1.618 1.618 2.114 3.912 3.912 3.912 2.294 2.294 0.986 2.548 ms 0.5751 1.5
Server Offset 161.35.230.200 -2.730 -2.730 -1.127 1.511 390.595 395.667 395.667 391.722 398.397 147.881 68.930 ms 1.72 3.961
Server Offset 162.159.200.1 -33.205 -5.539 -1.239 5.482 8.982 11.637 16.373 10.221 17.176 3.898 4.765 ms -3.203 30.1
Server Offset 162.159.200.123 -1,990.740 -3.828 -1.053 5.787 8.818 12.008 41.636 9.871 15.836 54.668 3.802 ms -36.3 1324
Server Offset 170.187.147.56 1.026 1.199 3.846 6.744 9.809 11.373 12.448 5.963 10.174 1.897 6.818 ms -0.2684 3.74
Server Offset 171.66.97.126 -111.117 -111.117 -111.117 -1.864 2.857 2.857 2.857 113.973 113.973 55.954 -54.736 ms 0.002046 1.003
Server Offset 172.233.155.39 -1.467 -1.004 0.504 3.923 6.683 9.443 9.891 6.178 10.447 1.888 3.780 ms -0.1655 3.462
Server Offset 172.234.25.10 -378.349 -377.277 -1.613 7.945 13.980 16.005 16.638 15.592 393.281 71.028 -5.439 ms -5.005 26.14
Server Offset 172.234.37.140 -384.852 -377.114 -10.309 2.206 9.952 35.580 41.762 20.261 412.695 46.143 -2.705 ms -7.84 64.55
Server Offset 172.235.60.8 -1,994.828 -7.193 -2.951 1.687 6.652 8.955 47.412 9.602 16.148 100.097 -3.238 ms -19.74 391.2
Server Offset 172.238.164.57 -20.678 -5.109 -3.388 1.693 6.481 7.573 11.018 9.869 12.682 3.241 1.724 ms -0.3793 3.926
Server Offset 172.245.210.108 -261.506 -261.506 -251.411 0.386 170.775 173.801 173.801 422.186 435.307 82.626 -6.480 ms -0.7581 6.622
Server Offset 173.255.230.96 -4.019 -1.915 0.365 4.658 8.077 9.189 28.541 7.712 11.104 2.614 4.581 ms 2.225 26.93
Server Offset 185.234.20.134 -207.966 -198.229 8.539 43.432 54.518 222.317 228.892 45.980 420.546 43.466 39.110 ms -0.8489 21.78
Server Offset 192.48.105.15 -38.144 -16.120 -11.322 4.337 8.624 13.335 24.385 19.946 29.455 6.098 2.898 ms -2.025 11.15
Server Offset 194.0.5.123 -1,993.360 -8.509 -3.462 4.470 7.817 12.344 390.115 11.279 20.852 70.101 1.248 ms -27.4 778.4
Server Offset 198.137.202.56 -206.226 -6.792 -4.823 -1.585 2.970 6.864 17.267 7.794 13.656 10.679 -1.881 ms -16.46 302.5
Server Offset 198.46.254.130 -11.109 -10.105 -8.900 -0.000 6.524 48.594 50.250 15.424 58.699 6.597 0.210 ms 4.556 35.9
Server Offset 198.71.50.75 -21.461 -16.971 -10.397 -4.651 -1.037 1.083 5.931 9.360 18.054 3.141 -4.906 ms -1.601 9.855
Server Offset 199.68.201.237 -54.221 -4.457 -2.342 2.245 5.491 7.434 14.187 7.833 11.890 3.323 1.891 ms -8.342 141.8
Server Offset 204.2.134.173 -330.587 -1.995 0.505 4.402 7.005 7.870 8.684 6.500 9.866 24.915 2.289 ms -13.06 173.8
Server Offset 206.210.192.99 3.732 3.732 3.732 10.882 12.986 12.986 12.986 9.255 9.255 2.868 9.737 ms -0.9345 2.785
Server Offset 209.177.158.85 -30.375 -4.599 -3.528 0.644 5.660 6.592 10.469 9.189 11.191 3.484 1.079 ms -2.528 23.23
Server Offset 212.227.240.160 -12.742 -12.742 -12.742 -3.409 1.156 1.156 1.156 13.898 13.898 4.103 -3.640 ms -1.253 3.789
Server Offset 216.229.4.66 -17.026 -11.915 -9.323 -0.727 3.365 13.045 13.185 12.689 24.960 3.711 -1.195 ms -0.3257 7.429
Server Offset 216.250.115.174 -50.737 -50.737 -50.737 -22.856 369.510 369.510 369.510 420.246 420.246 153.331 42.225 ms 1.636 3.702
Server Offset 216.66.48.42 -57.714 -48.968 -41.803 -10.099 4.232 45.537 48.178 46.035 94.505 15.518 -12.901 ms 0.07764 5.238
Server Offset 216.82.35.115 -29.297 -29.297 -9.388 -1.589 392.815 392.815 392.815 402.203 422.112 140.650 54.907 ms 1.952 4.828
Server Offset 23.142.248.8 -3.042 1.210 6.116 10.762 12.869 13.726 15.979 6.753 12.515 2.256 10.325 ms -1.928 8.756
Server Offset 23.142.248.9 -263.459 -263.459 -262.784 -5.526 168.098 168.098 168.098 430.883 431.557 135.791 -14.334 ms -0.3337 2.497
Server Offset 23.150.41.122 -3.912 -0.906 1.567 5.532 9.044 10.304 12.219 7.477 11.210 2.174 5.373 ms -0.477 4.713
Server Offset 23.150.41.123 -22.902 -6.841 -4.011 7.985 11.290 27.089 32.724 15.301 33.931 6.002 6.415 ms -0.1132 6.673
Server Offset 23.155.72.147 -392.987 -391.252 -12.441 -6.112 -0.837 1.703 7.397 11.604 392.955 61.955 -16.524 ms -5.782 34.56
Server Offset 23.159.16.194 -332.773 -2.949 1.895 12.336 15.900 21.536 27.238 14.005 24.484 25.353 9.220 ms -12.89 173.5
Server Offset 23.161.104.133 -2,049.972 -101.968 -80.336 -10.292 8.933 16.421 36.039 89.268 118.389 73.298 -20.257 ms -23.94 661.5
Server Offset 23.168.24.210 -30.994 -9.946 -0.456 4.953 9.479 14.370 15.899 9.935 24.316 3.912 4.627 ms -3.016 28.6
Server Offset 23.186.168.123 -18.265 -9.033 -4.573 1.968 4.196 5.440 24.970 8.768 14.473 2.913 1.183 ms -1.453 9.185
Server Offset 23.186.168.125 -336.573 -2.857 -1.290 2.156 4.173 5.028 21.753 5.462 7.885 12.191 1.436 ms -26.88 738.4
Server Offset 23.186.168.126 -114.793 -114.793 -114.793 -5.494 -0.844 -0.844 -0.844 113.950 113.950 54.847 -57.177 ms -0.005087 1.013
Server Offset 23.186.168.129 -100.937 -99.110 -94.535 -0.231 26.999 28.752 33.560 121.534 127.862 23.833 -4.843 ms -3.043 12.37
Server Offset 23.95.35.34 -27.613 -6.330 -4.084 -0.692 1.519 7.411 20.501 5.603 13.742 2.639 -0.860 ms -1.428 41.63
Server Offset 2602:f590::23:161:104:133 (isere.sd.ysun.co) -471.581 -385.176 -54.827 -11.476 0.126 5.242 28.182 54.953 390.419 61.385 -26.183 ms -5.774 37.6
Server Offset 34.147.28.4 -2,001.428 -123.441 -64.427 -8.775 4.087 9.142 11.849 68.513 132.582 117.993 -21.514 ms -16.19 271.5
Server Offset 38.45.64.130 -257.312 -73.003 -9.597 5.725 9.142 13.153 177.823 18.739 86.156 24.534 3.845 ms -3.142 73.78
Server Offset 40.160.28.79 -52.835 -52.513 -34.382 -5.004 1.626 5.643 7.374 36.008 58.156 10.906 -8.229 ms -2.157 7.89
Server Offset 44.190.5.123 -7.144 -7.144 -5.951 -0.158 3.398 3.755 3.755 9.349 10.899 2.890 -0.778 ms -0.2377 2.111
Server Offset 45.33.53.84 -46.045 -0.594 1.252 5.059 7.317 7.897 8.597 6.064 8.490 2.909 4.640 ms -9.672 161.8
Server Offset 45.55.58.103 -110.343 -110.343 -110.343 0.562 3.360 3.360 3.360 113.703 113.703 54.930 -52.554 ms -0.005973 1.01
Server Offset 45.63.54.13 -5.411 -1.284 1.511 5.531 7.546 8.410 9.171 6.035 9.693 1.905 5.168 ms -1.347 6.272
Server Offset 45.77.126.122 2.520 2.520 2.520 7.490 10.132 10.132 10.132 7.613 7.613 2.779 7.072 ms -0.4913 1.881
Server Offset 45.83.234.123 -92.017 -92.017 -53.358 -1.514 30.819 37.116 37.116 84.178 129.133 21.169 -7.277 ms -0.9842 5.63
Server Offset 47.85.203.40 -11.482 -4.542 -0.158 5.077 10.458 14.417 15.104 10.616 18.959 3.390 5.170 ms -0.3312 5.456
Server Offset 49.12.103.123 -104.453 -96.809 -69.563 -6.827 5.026 15.191 21.860 74.590 112.001 23.583 -15.248 ms -1.71 5.611
Server Offset 5.161.111.190 -18.177 -13.919 -7.797 -3.175 1.189 3.412 7.582 8.985 17.330 3.150 -3.351 ms -0.7991 5.935
Server Offset 5.161.65.34 -8.208 -8.208 -5.991 -2.626 391.162 391.162 391.162 397.153 399.370 139.388 55.456 ms 1.96 4.843
Server Offset 5.161.94.12 -26.311 -6.789 -5.364 -1.781 1.988 4.296 14.347 7.351 11.084 2.473 -1.710 ms -0.7917 18.97
Server Offset 50.117.3.95 -13.393 -13.270 -8.900 -1.296 1.731 4.497 6.235 10.631 17.767 3.214 -1.929 ms -1.378 5.671
Server Offset 50.218.103.254 -39.877 -17.266 -8.068 0.775 5.720 46.263 49.954 13.788 63.530 7.440 0.730 ms 2.027 26.4
Server Offset 51.81.226.229 -3.807 -1.522 1.150 5.163 7.606 8.830 11.602 6.456 10.352 1.992 4.926 ms -0.7831 4.9
Server Offset 64.251.10.152 -9.929 -6.388 -4.004 -0.535 3.189 7.131 10.599 7.193 13.520 2.557 -0.405 ms 0.497 5.923
Server Offset 65.182.224.39 -19.040 -5.987 -1.484 1.519 6.164 11.148 17.628 7.648 17.136 3.038 1.696 ms -0.02657 18.42
Server Offset 65.182.224.60 -4.897 -4.897 -2.203 1.449 6.846 10.883 10.883 9.048 15.780 2.958 1.749 ms 0.4925 3.551
Server Offset 66.118.228.14 -333.165 -10.163 -2.631 4.084 8.349 9.848 12.691 10.980 20.011 25.449 1.791 ms -12.74 167.1
Server Offset 66.118.229.14 -46.204 -13.396 -8.297 4.542 8.438 12.813 14.060 16.735 26.209 5.776 3.279 ms -3.792 28.07
Server Offset 67.217.246.204 -33.203 -13.840 -6.321 -1.577 2.341 5.436 13.727 8.662 19.277 3.265 -1.879 ms -1.993 17.59
Server Offset 69.89.207.199 -132.300 -132.300 -132.300 -82.315 12.317 12.317 12.317 144.616 144.616 60.181 -69.022 ms 0.2283 1.231
Server Offset 69.89.207.99 -38.922 -5.235 -2.966 0.525 2.859 4.153 5.952 5.826 9.389 2.447 0.240 ms -7.231 113.7
Server Offset 72.14.182.49 -1.532 -0.973 0.417 4.164 7.308 8.085 8.396 6.891 9.058 1.895 4.150 ms -0.3723 3.354
Server Offset 72.14.186.59 -10.962 -10.962 -6.498 5.272 7.467 8.444 8.444 13.965 19.405 4.884 3.065 ms -1.172 3.134
Server Offset 73.185.182.209 -385.027 -380.946 -6.151 1.376 7.161 9.409 12.049 13.313 390.355 55.425 -6.810 ms -6.565 44.31
Server Offset 77.37.97.124 -64.960 -64.960 -62.814 -13.281 12.547 12.582 12.582 75.362 77.541 22.383 -16.669 ms -0.5829 2.612
Server Offset 77.42.37.85 -83.037 -83.037 -83.037 -1.405 13.595 13.595 13.595 96.633 96.633 29.560 -20.475 ms -0.8498 2.319
Server Offset 79.160.225.13 -64.543 -64.543 -64.543 -6.827 0.842 0.842 0.842 65.386 65.386 19.265 -16.275 ms -1.272 3.416
Server Offset 83.228.206.15 -137.287 -106.678 -85.463 -5.076 5.321 28.735 31.867 90.784 135.413 27.600 -16.729 ms -1.765 5.927
Server Offset 99.28.14.242 -1,995.690 -9.227 -2.599 3.709 6.341 11.025 51.057 8.939 20.252 126.659 -4.965 ms -15.62 245.1
TDOP 0.450 0.510 0.560 0.770 1.200 1.570 3.610 0.640 1.060 0.219 0.808 2.484 17.77
Temp /dev/sda 18.000 20.000 20.000 25.000 26.000 28.000 33.000 6.000 8.000 2.273 24.416 °C
Temp LM0 31.000 32.000 35.000 37.000 40.000 42.000 59.000 5.000 10.000 1.903 36.978 °C
Temp LM1 29.000 30.000 31.000 34.000 38.000 43.000 54.000 7.000 13.000 2.322 34.340 °C
Temp LM2 26.000 26.000 34.000 37.000 40.000 41.000 46.000 6.000 15.000 2.120 37.022 °C
Temp LM3 0.000 0.000 3.000 39.000 40.000 41.000 43.000 37.000 41.000 17.403 25.992 °C
Temp LM4 0.000 0.000 0.000 0.000 39.000 41.000 51.000 39.000 41.000 17.055 13.399 °C
Temp LM5 27.000 29.000 31.000 33.000 38.000 38.000 39.000 7.000 9.000 2.865 33.781 °C
Temp LM6 28.000 32.000 33.000 35.000 37.000 37.000 44.000 4.000 5.000 1.208 34.578 °C
Temp LM7 31.000 33.000 34.000 36.000 38.000 39.000 46.000 4.000 6.000 1.265 36.252 °C
Temp LM8 26.800 26.800 35.000 37.000 38.000 39.000 46.000 3.000 12.200 1.641 36.237 °C
Temp LM9 26.800 26.800 35.000 37.000 38.000 39.000 46.000 3.000 12.200 1.641 36.237 °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 26.800 26.800 34.000 36.000 38.000 38.000 46.000 4.000 11.200 1.546 35.646 °C
Temp ZONE2 29.000 29.000 32.000 37.000 38.000 38.000 38.000 6.000 9.000 2.400 35.632 °C
Temp ZONE3 30.000 32.000 34.000 36.000 38.000 43.000 54.000 4.000 11.000 1.763 35.623 °C
Temp ZONE4 26.800 26.800 34.000 36.000 38.000 38.000 46.000 4.000 11.200 1.546 35.646 °C
Temp ZONE5 30.000 31.000 32.000 36.000 41.000 42.000 58.000 9.000 11.000 2.688 36.341 °C
Temp ZONE6 27.000 30.000 31.000 32.000 37.000 38.000 44.000 6.000 8.000 2.160 33.092 °C
nSats 8.000 10.000 11.000 14.000 18.000 19.000 22.000 7.000 9.000 2.091 14.149 nSat 0.3186 2.713
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!