Gmail: Down?

[ViviTheMage]

hahaha

Tracing route to google.com [209.85.171.100]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms xxxxxxxxxxxxxx hidden
2 1 ms 1 ms 1 ms min-edge-10.inet.qwest.net [207.225.128.73]
3 3 ms 1 ms 1 ms min-core-02.inet.qwest.net [205.171.128.153]
4 11 ms 11 ms 11 ms cer-core-02.inet.qwest.net [67.14.8.22]
5 11 ms 11 ms 12 ms chp-brdr-01.inet.qwest.net [205.171.139.150]
6 67 ms 69 ms 56 ms 205.171.1.138
7 13 ms 12 ms 12 ms sl-st30-chi-0-0-0-0.sprintlink.net [144.232.1.15
]
8 * * * Request timed out.
9 301 ms * 305 ms 209.85.254.120
10 393 ms * 315 ms 72.14.233.116
11 * 314 ms 308 ms 209.85.241.211
12 * * 316 ms 64.233.174.127
13 312 ms 315 ms 315 ms 64.233.174.97
14 344 ms * 322 ms 74.125.30.130
15 * 315 ms 305 ms cg-in-f100.google.com [209.85.171.100]

Trace complete.

this is going to CA IP

 

[shopbruin]

Perfectly fine here in CA.

 

[Queasy]

Looks like this is affecting more than just Gmail. Any site that I go to that uses google analytics or even ajax.googleapis.com is having problems.

 

[Superself]

Damn, the google counter is broken....

Lots of space
Over 2757.272164 megabytes (and counting) of free storage so you'll never need to delete another message.


It was at 7+ gigs yesterday.

 

[Saint Nick]

Its the apocolypse.

 

[mcmilljb]

Interesting. They took google news down so they could.... bring you news feeds on youtube!

http://news.cnet.com/8301-1023_3-10240709-93.html

Thanks for the early warning! :beer:

 

[SN4p]

Pinging www.l.google.com [74.125.67.99] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.125.67.99:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)


I don't know what to do now. Gmail loads, in about 3 minutes, but is unresponsive. Can't send anything from my iphone gmail account either.

The world is coming to an end.

 

[ViviTheMage]

comcast seems to be doing a better job...

Tracing route to google.com [209.85.171.100]
over a maximum of 30 hops:

1 5 ms 15 ms 8 ms 73.236.170.1
2 4 ms 3 ms 3 ms ge-9-11-ur02.swmpls.mn.minn.comcast.net [68.85.1
65.85]
3 6 ms 6 ms 7 ms te-2-1-ur01.swmpls.mn.minn.comcast.net [68.86.23
2.101]
4 6 ms 3 ms 6 ms te-8-1-ur02.smpls.mn.minn.comcast.net [68.86.232
.110]
5 6 ms 6 ms 5 ms te-2-1-ur01.smpls.mn.minn.comcast.net [68.86.232
.113]
6 7 ms 7 ms 6 ms te-9-1-ar02.roseville.mn.minn.comcast.net [68.86
.232.122]
7 13 ms 16 ms 13 ms te-0-4-0-0-cr01.chicago.il.ibone.comcast.net [68
.86.91.137]
8 15 ms 17 ms 15 ms xe-9-0-0.edge1.Chicago2.Level3.net [4.71.248.33]

9 15 ms 16 ms 17 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
10 34 ms 35 ms 45 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61]
11 58 ms 70 ms 72 ms ae-2.ebr2.Seattle1.Level3.net [4.69.132.53]
12 56 ms 58 ms 58 ms ae-21-52.car1.Seattle1.Level3.net [4.68.105.34]

13 77 ms 77 ms 78 ms GOOGLE-INC.car1.Seattle1.Level3.net [4.79.104.74
]
14 103 ms 101 ms 101 ms 209.85.249.32
15 110 ms 83 ms 110 ms 216.239.46.208
16 84 ms 84 ms 84 ms 64.233.174.127
17 89 ms 82 ms 89 ms 209.85.251.133
18 116 ms 111 ms 93 ms 74.125.31.2
19 88 ms 86 ms 86 ms cg-in-f100.google.com [209.85.171.100]

Trace complete.

 

[OpenThirdEye]

Funny: downforeveryoneorjustme.com uses Google Analytics.

Soooo...guess what can't tell me if Google is down for everyone or just me?

 

[jteef]

meh. i get no gmail or other websites that use doubleclick / google ads. google.com itself loaded, albeit very slowly. I hope they are losing customers.

 

[adlep]

Youtube down, gmail down. Metro Detroit
Need to send email

 

[ViviTheMage]

gmail works fine, rather slow though...same with google.

 

[SN4p]

I got into gmail, needed to download a PDF,it is so slow.

 

[adlep]

seems better now.
woot

 

[Darkstar757]

Back up for me!

 

[ViviTheMage]

sweet! back to 15MS ping times again....they must have fixed it.

 

[codeyf]

Does seem better, but trace gives:

1 <1 ms <1 ms <1 ms 10.2.23.3
2 1 ms 1 ms 1 ms 4.23.83.254
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 68 ms 68 ms 68 ms gw-in-f100.google.com [74.125.67.100]

:brokenheart:

 

[Demo24]

Working fine now.

 

[Modelworks]

Google is a bit weird for me right now. It is working but not at the usual speed.
Trace looks okay though.

3 host57.sprintnetops.net (206.107.116.57) 9.387 ms 8.871 ms 9.451 ms
4 sl-gw27-rly-3-1-3.sprintlink.net (160.81.125.97) 20.980 ms 20.212 ms 21.163 ms
5 sl-crs1-rly-0-10-0-0.sprintlink.net (144.232.14.164) 22.243 ms 21.635 ms 20.625 ms
6 sl-crs1-dc-0-8-0-0.sprintlink.net (144.232.19.213) 23.318 ms 22.155 ms 22.245 ms
7 sl-st30-ash-0-1-0-0.sprintlink.net (144.232.19.228) 24.595 ms 21.606 ms 21.631 ms
8 sl-googl11-219203-0.sprintlink.net (144.228.205.18) 21.921 ms 21.960 ms 22.065 ms
9 216.239.48.112 (216.239.48.112) 22.603 ms 21.388 ms 22.310 ms
10 216.239.48.69 (216.239.48.69) 39.379 ms 47.734 ms 39.183 ms
11 72.14.232.215 (72.14.232.215) 40.361 ms
72.14.232.213 (72.14.232.213) 40.656 ms 39.394 ms
12 209.85.253.137 (209.85.253.137) 38.583 ms 50.593 ms
209.85.253.145 (209.85.253.145) 36.511 ms
13 yx-in-f100.google.com (74.125.45.100) 36.662 ms 36.810 ms 35.988 ms

 

[Modelworks]

We were not imagining things, talk about a routing screw up
http://googleblog.blogspot.com...peaking-now-about.html

This is your pilot speaking. Now, about that holding pattern...
5/14/2009 12:15:00 PM
Imagine if you were trying to fly from New York to San Francisco, but your plane was routed through an airport in Asia. And a bunch of other planes were sent that way too, so your flight was backed up and your journey took much longer than expected. That's basically what happened to some of our users today for about an hour, starting at 7:48 am Pacific time.

An error in one of our systems caused us to direct some of our web traffic through Asia, which created a traffic jam. As a result, about 14% of our users experienced slow services or even interruptions. We've been working hard to make our services ultrafast and "always on," so it's especially embarrassing when a glitch like this one happens. We're very sorry that it happened, and you can be sure that we'll be working even harder to make sure that a similar problem won't happen again. All planes are back on schedule now.

 

[KLin]

Talk about a long flight...

 

[spidey07]

oops!

 

[StarsFan4Life]

See what I started....I figured it was our awesome internet connection here at work....

 

[James Bond]

Originally posted by: James Bond

Originally posted by: OREOSpeedwagon
it's back but slow for me now. just did a traceroute and after this:

xe-2-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.110) 159.903 ms xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.238) 186.616 ms 175.318 ms

is where it gets hung up. does google traffic usually go to tokyo?

LOL, huge routing fail.

Looks like someone accidently changed a route and sent all of Googles traffic through Asia - oops!

http://www.wired.com/epicenter...own-it-goes-down-hard/

http://www.wired.com/images_bl...nter/2009/05/lapse.png - Throughput graph

Arbor Networks knows more about the internet?s workings than possibly anyone outside the National Security Agency. Their monitoring equipment sits in nearly all Tier 1 internet providers ? and if you want data on what the internet looks like and what the top threats are, they?ve got it through their Atlas service.

So what does it look like when Google?s search, email, and calendar services, among others, stop working for two hours?

The graph above from the company?s Atlas system shows average traffic from ten top North American ISPs sending data to Google?s network. (Note this graph only shows traffic to to Google?s portion of the internet, not internet traffic generally.) Google says it messed up and routed traffic through an Asian network that couldn?t handle the flood. The outage lasted about two hours ? starting about 10:15 am Eastern time.

If I were a regulator, this graph would be piece one in evidence that Google holds a monopoly on the world?s information.

Update: Actually, the fact that Google?s slip-up causes such a stir in the media, on mailing lists and on Twitter, says much more about Google?s centrality to the internet than this graph does, even though its a really cool graph.

That drop on the right side of the graph from 15 Gbps to 1 is just astounding.

 

[Crusty]

Originally posted by: James Bond

Originally posted by: James Bond

Originally posted by: OREOSpeedwagon
it's back but slow for me now. just did a traceroute and after this:

xe-2-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.110) 159.903 ms xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.238) 186.616 ms 175.318 ms

is where it gets hung up. does google traffic usually go to tokyo?

LOL, huge routing fail.

Looks like someone accidently changed a route and sent all of Googles traffic through Asia - oops!

http://www.wired.com/epicenter...own-it-goes-down-hard/

http://www.wired.com/images_bl...nter/2009/05/lapse.png - Throughput graph

Arbor Networks knows more about the internet?s workings than possibly anyone outside the National Security Agency. Their monitoring equipment sits in nearly all Tier 1 internet providers ? and if you want data on what the internet looks like and what the top threats are, they?ve got it through their Atlas service.

So what does it look like when Google?s search, email, and calendar services, among others, stop working for two hours?

The graph above from the company?s Atlas system shows average traffic from ten top North American ISPs sending data to Google?s network. (Note this graph only shows traffic to to Google?s portion of the internet, not internet traffic generally.) Google says it messed up and routed traffic through an Asian network that couldn?t handle the flood. The outage lasted about two hours ? starting about 10:15 am Eastern time.

If I were a regulator, this graph would be piece one in evidence that Google holds a monopoly on the world?s information.

Update: Actually, the fact that Google?s slip-up causes such a stir in the media, on mailing lists and on Twitter, says much more about Google?s centrality to the internet than this graph does, even though its a really cool graph.

That drop on the right side of the graph from 15 Gbps to 1 is just astounding.

I don't see how a graph only showing traffic to google is any indication of their 'monopoly on the world?s information'. Maybe if that was ALL internet traffic and google still put a dent in the numbers that much I could see the connection.