[ale] Anyone know what's wrong with Google?

[Randy]

Jeff Lightner wrote:
>
> And of course now it appears to be Ok – wonder what the issue was.
>
> ------------------------------------------------------------------------
>
> *From:* ale-bounces at ale.org [mailto:ale-bounces at ale.org] *On Behalf Of 
> *Jeff Lightner
> *Sent:* Thursday, May 14, 2009 11:57 AM
> *To:* Atlanta Linux Enthusiasts - Yes! We run Linux!
> *Subject:* [ale] Anyone know what's wrong with Google?
>
> There is chatter on another forum that Google is hosed. On checking I 
> found it is. Some attempts go right in but others hang and only 
> partially draw screen. Others in that forum confirmed they are seeing 
> this as well.
>
> //Please consider our environment before printing this e-mail or 
> attachments.//
>
> ----------------------------------
> CONFIDENTIALITY NOTICE: This e-mail may contain privileged or 
> confidential information and is for the sole use of the intended 
> recipient(s). If you are not the intended recipient, any disclosure, 
> copying, distribution, or use of the contents of this information is 
> prohibited and may be unlawful. If you have received this electronic 
> transmission in error, please reply immediately to the sender that you 
> have received the message in error, and delete it. Thank you.
> ----------------------------------
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>   
The path to them were hosed and hosed big time. Our site which relies on 
google analytics was have major connection issues. As you see below, 
from Atlanta, we had ping time for both at about 300ms. Now they are 
about 150 which is still bad even though most think this is over.

http://twitter.com/#search?q=%23googlefail

http://blogs.zdnet.com/BTL/?p=18064
http://isc.sans.org/diary.html?storyid=6388&rss

They appear to have had a route/network issue.

>From Atlanta: Hopping to Japan it appears.

13  as-3.r21.snjsca04.us.bb.gin.ntt.net (129.250.4.25)  68.460 ms   67.749 ms   67.780 ms
14  as-0.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.5.82)  168.402 ms as-2.r20.lsanca03.us.bb.gin.ntt.net (129.250.2.168)  57.277 ms   56.881 ms
15  as-5.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.3.23)  171.049 ms   171.025 ms   171.033 ms
16  xe-2-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.110)  173.880 ms * *
26  ww-in-f147.google.com (209.85.229.147)  307.032 ms 216.239.49.45 (216.239.49.45)  305.917 ms   305.933 ms

>From South Florida: Since this shows Bellsouth as a potential problem, some routing stuff hosed?

traceroute www.google.com
traceroute to www.google.com (66.102.1.104), 30 hops max, 40 byte packets
 1  fwgw-bell.local.livedatagroup.com (192.168.2.20)  0.421 ms   0.420 ms   0.246 ms
 2  adsl-074-228-048-193.sip.bct.bellsouth.net (74.228.48.193)  1.001 ms   0.673 ms   0.674 ms
 3  65.14.252.23 (65.14.252.23)  60.868 ms   62.135 ms   63.456 ms
 4  65.14.252.209 (65.14.252.209)  59.300 ms   57.229 ms   17.712 ms
 5  axr01mia-7-0-0-1.bellsouth.net (65.83.237.50)  23.516 ms   23.501 ms   20.106 ms
 6  pxr00ash-so-1-0-0.bellsouth.net (65.83.236.180)  127.284 ms   129.382 ms   128.441 ms
 7  pxr00chi-so-2-0-0.bellsouth.net (65.83.236.120)  168.208 ms   208.677 ms   199.363 ms

17  he-in-f104.google.com (66.102.1.104)  310.970 ms * *

Another Colo South Florida:

13  64.233.174.46 (64.233.174.46)  18.663 ms   28.026 ms   20.043 ms

This colo never saw the problem.