mmmmmmmmm, this smells like an overloaded router flushing its buffers and starting over cleanly,
notice the trend in the ping rtt leading up to the timeout, and then the immediate 'fresh' result following the timeout. Its all rather disturbing!
Reply from 64.233.171.104: bytes=32 time=1991ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2498ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1180ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1720ms TTL=236
Reply from 64.233.171.104: bytes=32 time=778ms TTL=236
<font color="red">Reply from 64.233.171.104: bytes=32 time=1177ms TTL=236 </font id="red">
<font color="red">Reply from 64.233.171.104: bytes=32 time=1399ms TTL=236 </font id="red">
<font color="red">Reply from 64.233.171.104: bytes=32 time=1800ms TTL=236 </font id="red">
<font color="red">Reply from 64.233.171.104: bytes=32 time=1998ms TTL=236 </font id="red">
<font color="red">Reply from 64.233.171.104: bytes=32 time=2198ms TTL=236 </font id="red">
Request timed out.
<font color="green">Reply from 64.233.171.104: bytes=32 time=996ms TTL=236
Reply from 64.233.171.104: bytes=32 time=418ms TTL=236
Reply from 64.233.171.104: bytes=32 time=376ms TTL=236
Reply from 64.233.171.104: bytes=32 time=356ms TTL=236
Reply from 64.233.171.104: bytes=32 time=497ms TTL=236
Reply from 64.233.171.104: bytes=32 time=993ms TTL=236 </font id="green">
<font color="red"> Reply from 64.233.171.104: bytes=32 time=1395ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1699ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1485ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1713ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1685ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2533ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2776ms TTL=236 </font id="red">
Request timed out.
<font color="green"> Reply from 64.233.171.104: bytes=32 time=798ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1000ms TTL=236 </font id="green">
<font color="red">Reply from 64.233.171.104: bytes=32 time=1718ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1880ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2319ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2480ms TTL=236
Reply from 64.233.171.104: bytes=32 time=3038ms TTL=236
Reply from 64.233.171.104: bytes=32 time=3139ms TTL=236
Reply from 64.233.171.104: bytes=32 time=3457ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2183ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1774ms TTL=236
Reply from 64.233.171.104: bytes=32 time=3003ms TTL=236 </font id="red">
Request timed out.
Reply from 64.233.171.104: bytes=32 time=1599ms TTL=236
Reply from 64.233.171.104: bytes=32 time=519ms TTL=236
The trend continues, over 1000ms (1 second) up till around 3000ms, where timeouts occur, after timeout, rtt starts at under 1000, and slowly climbs, to next timeout.
In my limited experience/knowledge of networks, this spells some seriously underpowered routers!!
Another illustration that not all problems can be solved by more bandwidth!!
notice the trend in the ping rtt leading up to the timeout, and then the immediate 'fresh' result following the timeout. Its all rather disturbing!
Reply from 64.233.171.104: bytes=32 time=1991ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2498ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1180ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1720ms TTL=236
Reply from 64.233.171.104: bytes=32 time=778ms TTL=236
<font color="red">Reply from 64.233.171.104: bytes=32 time=1177ms TTL=236 </font id="red">
<font color="red">Reply from 64.233.171.104: bytes=32 time=1399ms TTL=236 </font id="red">
<font color="red">Reply from 64.233.171.104: bytes=32 time=1800ms TTL=236 </font id="red">
<font color="red">Reply from 64.233.171.104: bytes=32 time=1998ms TTL=236 </font id="red">
<font color="red">Reply from 64.233.171.104: bytes=32 time=2198ms TTL=236 </font id="red">
Request timed out.
<font color="green">Reply from 64.233.171.104: bytes=32 time=996ms TTL=236
Reply from 64.233.171.104: bytes=32 time=418ms TTL=236
Reply from 64.233.171.104: bytes=32 time=376ms TTL=236
Reply from 64.233.171.104: bytes=32 time=356ms TTL=236
Reply from 64.233.171.104: bytes=32 time=497ms TTL=236
Reply from 64.233.171.104: bytes=32 time=993ms TTL=236 </font id="green">
<font color="red"> Reply from 64.233.171.104: bytes=32 time=1395ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1699ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1485ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1713ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1685ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2533ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2776ms TTL=236 </font id="red">
Request timed out.
<font color="green"> Reply from 64.233.171.104: bytes=32 time=798ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1000ms TTL=236 </font id="green">
<font color="red">Reply from 64.233.171.104: bytes=32 time=1718ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1880ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2319ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2480ms TTL=236
Reply from 64.233.171.104: bytes=32 time=3038ms TTL=236
Reply from 64.233.171.104: bytes=32 time=3139ms TTL=236
Reply from 64.233.171.104: bytes=32 time=3457ms TTL=236
Reply from 64.233.171.104: bytes=32 time=2183ms TTL=236
Reply from 64.233.171.104: bytes=32 time=1774ms TTL=236
Reply from 64.233.171.104: bytes=32 time=3003ms TTL=236 </font id="red">
Request timed out.
Reply from 64.233.171.104: bytes=32 time=1599ms TTL=236
Reply from 64.233.171.104: bytes=32 time=519ms TTL=236
The trend continues, over 1000ms (1 second) up till around 3000ms, where timeouts occur, after timeout, rtt starts at under 1000, and slowly climbs, to next timeout.
In my limited experience/knowledge of networks, this spells some seriously underpowered routers!!
Another illustration that not all problems can be solved by more bandwidth!!