5 Comments

Summary:

It’s a bad week to stop sniffing glue — and to run big cloud services. Google App Engine took a hit Friday, just days after Amazon Web Services suffered another very public snafu.

GAE status page error

On Monday, it was Amazon Web Services. On Friday, Google App Engine crashed and burned.

Update: Google’s latest update posted at  10:52 pm PDT said the company was working to correct ongoing issues but still sees slow response times and elevated error rates.

“The malfunction appears to be limited to a single component which routes requests from users to the application instance they are using, and does not affect the application instances themselves.”

Update: This posted to the GAE status thread at 9:33 a.m. PDT:

“At approximately 7:30am Pacific time this morning, Google began experiencing slow performance and dropped connections from one of the components of App Engine.  The symptoms that service users would experience include slow response and an inability to connect to services.  We currently show that a majority of App Engine users and services are affected.  Google engineering teams are investigating a number of options for restoring service as quickly as possible, and we will provide another update as information changes, or within 60 minutes.”

The outage was noted all over Twitter and a visit to the GAE status page around noon eastern time turned up an error message. To be fair there appears to be more going on beyond GAE: Both Dropbox and Tumblr have had widespread availability issues today.

A few minutes later the status page was up again, bearing this message:

Oct 26 2012, 07:30 AM – Oct 26 2012, 11:59 PM
posted by alevi

App Engine is currently experiencing serving issues. The team is actively working on restoring the service to full strength. Please follow this thread for updates:

https://groups.google.com/forum/?fromgroups=#!topic/google-appengine-downtime-notify/SMd2pDJsCPo

We’ll update this post as we learn more about the nature of the outage, and let us know if you or your business is having problems.

You’re subscribed! If you like, you can update your settings

  1. It appears some of the App engine status pages… run on the App engine. Brilliant!

    http://s12.postimage.org/4ok871gwb/Screen_Shot_2012_10_26_at_10_01_26_AM.png

    1. yes the screen grab i used as feature art is the error message i got wehn i tried to access GAE status page. But it was back up a few minutes later.

  2. Seems like a key difference between the AWS and App Engine outages is that with AWS you can architect your application to handle failures because you have machine level access and the ability to deploy across availability zones and regions. Since App Engine is more of a platform you simply outsource this part and let Google deal with redundancy, much like Heroku.

  3. Looks like GAE is back up and running!

Comments have been disabled for this post