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

[Christian Koch]

everything fine for me  from direct peering
and through comcast>level3

On Jan 31, 2008 5:01 PM, Alex Balashov <abalashov at evaristesys.com> 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 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 traceroute rely on ICMP messages.
>
> On Thu, 31 Jan 2008, Dean Perrine wrote:
>
> > On Jan 31, 2008 1:44 PM, Dean Perrine <deanperrine at gmail.com> 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
> >>
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>
> --
> Alex Balashov
> Evariste Systems
> Web    : http://www.evaristesys.com/
> Tel    : +1-678-954-0670
> Direct : +1-678-954-0671
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>