On Monday, it was Amazon Web Services . On Friday, Google App Engine crashed and burned.
Update: This just posted to the GAE status thread:
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.
Both #Tumblr and Google App Engine, #GAE, are down. What gives?—
Dylan Hurd (@dylanhurd) October 26, 2012
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:
BreakingNews.com and our mobile apps are temporarily offline due to a hosting outage at Google. Coverage continues here on @BreakingNews—
Breaking News (@BreakingNews) October 26, 2012
Hey, the Google Apps Engine (#GAE) is down-ish. Millions of apps failing. Keep track of the outage here: code.google.com/status/appengi…—
Matthew A. Peskay (@mpeskay) October 26, 2012
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.