[c-nsp] mail.google.com packet loss

[Tim Durack]

Verizon/MCI says: "We have other customers complaining of the same.
It's not us, it's Google."

I can see this taking a long time to resolve. Any Google ops people
lurking on this list?

Thanks,

Tim:>

On 1/5/07, Kevin Warwashana <kevinw at telnetww.com> wrote:
> Looking good for me.
>
> Kevin
>
>
> --- 209.85.133.83 ping statistics ---
> 16 packets transmitted, 16 packets received, 0% packet loss
> round-trip min/avg/max = 34.4/35.1/35.8 ms
>
> <user>@stout:~$ traceroute  209.85.133.83
> traceroute to 209.85.133.83 (209.85.133.83), 30 hops max, 38 byte packets
>  1  tnmi-1-200-54-69.ip.telnetww.com (69.54.200.1)  0.306 ms  0.242 ms
> 0.174 ms
>  2  unknown.Level3.net (63.209.134.17)  0.376 ms  0.319 ms  0.246 ms
>  3  so-4-3-0.mp1.Detroit1.Level3.net (4.68.115.1)  0.538 ms  0.602 ms
> 17.210 ms
>  4  as-2-0.bbr2.Washington1.Level3.net (209.247.10.130)  22.120 ms
> ae-2-0.bbr1.Washington1.Level3.net (4.68.128.201)  22.629 ms
> as-2-0.bbr2.Washington1.Level3.net (209.247.10.130)  22.306 ms
>  5  ae-11-51.car1.Washington1.Level3.net (4.68.121.18)  22.370 ms  22.456 ms
> ae-21-54.car1.Washington1.Level3.net (4.68.121.114)  22.381 ms
>  6  GOOGLE-INC.car1.Level3.net (4.79.228.38)  22.741 ms  22.272 ms  22.371
> ms
>  7  66.249.95.149 (66.249.95.149)  34.574 ms 72.14.238.136 (72.14.238.136)
> 36.023 ms 66.249.95.149 (66.249.95.149)  34.282 ms
>  8  72.14.239.17 (72.14.239.17)  35.264 ms  34.769 ms  35.110 ms
>  9  216.239.49.26 (216.239.49.26)  40.435 ms 216.239.49.22 (216.239.49.22)
> 37.596 ms 216.239.43.13 (216.239.43.13)  48.367 ms
> 10  209.85.133.83 (209.85.133.83)  34.758 ms  35.587 ms  35.497 ms
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Tim Durack
> Sent: Friday, January 05, 2007 8:50 AM
> To: Cisco-nsp
> Subject: [c-nsp] mail.google.com packet loss
>
> Anybody else seeing packet loss to mail.google.com? Doesn't seem to
> matter what that resolves to.
>
> Seems to only be affecting our MCI circuit, but I'm not seeing loss on
> the circuit itself, and all other sites seem fine.
>
> Has been ongoing since yesterday afternoon/evening.
>
>
> RTR-1>traceroute mail.google.com
>
>
>
> Type escape sequence to abort.
>
> Tracing the route to googlemail.l.google.com (209.85.133.83)
>
>
>
>   1 Serial1-4.GW3.NYC4.ALTER.NET (157.130.254.81) 12 msec 16 msec 12 msec
>
>   2 149.at-5-0-0.XR3.NYC4.ALTER.NET (152.63.24.134) 4 msec 4 msec 4 msec
>
>   3 0.so-4-0-2.XL3.NYC4.ALTER.NET (152.63.17.29) 8 msec 4 msec 4 msec
>
>   4 0.ge-4-0-0.BR2.NYC4.ALTER.NET (152.63.3.110) 0 msec 8 msec 20 msec
>
>   5  *
>
>     if-7-2.core1.NTO-NewYork.teleglobe.net (216.6.82.9) 4 msec 4 msec
>
>   6 if-4-0-0.core2.NTO-NewYork.teleglobe.net (216.6.82.66) 4 msec 4 msec 4
> msec
>
>   7 if-1-0-0.core3.AEQ-Ashburn.teleglobe.net (216.6.51.5) 12 msec 12 msec 8
> msec
>
>   8  *  *  *
>
>   9 209.85.130.16 12 msec
>
>     209.85.130.18 12 msec 28 msec
>
>  10 216.239.46.224 32 msec *
>
>     66.249.95.149 24 msec
>
>  11 72.14.232.149 28 msec
>
>     72.14.232.147 28 msec
>
>     72.14.238.136 24 msec
>
>  12 216.239.43.13 28 msec 32 msec 40 msec
>
>  13 googlemail.l.google.com (209.85.133.83) 24 msec 24 msec *
>
> RTR-1>ping 209.85.133.83
>
>
>
> Type escape sequence to abort.
>
> Sending 5, 100-byte ICMP Echos to 209.85.133.83, timeout is 2 seconds:
>
> !!..!
>
> Success rate is 60 percent (3/5), round-trip min/avg/max = 24/26/28 ms
>
>
> RTR-1#ping
>
> Protocol [ip]:
>
> Target IP address: 209.85.133.83
>
> Repeat count [5]: 100
>
> Datagram size [100]:
>
> Timeout in seconds [2]:
>
> Extended commands [n]:
>
> Sweep range of sizes [n]:
>
> Type escape sequence to abort.
>
> Sending 100, 100-byte ICMP Echos to 209.85.133.83, timeout is 2 seconds:
>
> .!!!!!!!!!!!!!!!!!!.!!!!!!!.!!!!!.!..!!!..!!!!!!!!!!.!!.!!!!.!.!!.!!!!
>
> !!!!!!!!!.!!!!!!.!!!!!!.!!..!!
>
> Success rate is 82 percent (82/100), round-trip min/avg/max = 24/84/296 ms
> _______________________________________________
> 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/
>
>
>