Re: [c-nsp] CORRECTION - Google latency, not Cisco latency (Cisco latency issues? high loss to 64.233.167.99)

2008-01-31 Thread Christian Koch
everything fine for me from direct peering and through comcast>level3 On Jan 31, 2008 5:01 PM, Alex Balashov <[EMAIL PROTECTED]> wrote: > > It is my consistent impression that this is the result of Google > rate-limiting ICMP traffic + lots of people pinging them due to their > canonical ubiquit

Re: [c-nsp] CORRECTION - Google latency, not Cisco latency (Cisco latency issues? high loss to 64.233.167.99)

2008-01-31 Thread Alex Balashov
It is my consistent impression that this is the result of Google rate-limiting ICMP traffic + lots of people pinging them due to their canonical ubiquity (in fact, the latter is likely a cause of the former), and isn't an accurate reflection of actual packet loss / throughput, etc. Both ping and

[c-nsp] CORRECTION - Google latency, not Cisco latency (Cisco latency issues? high loss to 64.233.167.99)

2008-01-31 Thread Dean Perrine
On Jan 31, 2008 1:44 PM, Dean Perrine <[EMAIL PROTECTED]> wrote: > > Anyone else seeing issues to google - 64.233.167.99? > > Trying to hit this google site and getting 50% loss, random drop offs.. > > Anyone know of something? > > = > Dean Perrine > ___