Twitter Experiences Site Instability Following Google, Microsoft Outages

by Michael Floyd on May 14, 2011 |

Twitter is the latest to experience downtime when yesterday the company issued a status update indicating instability within the site. This was the second such report from Twitter this week and follows on the heels of outages experienced this week by Google’s Blogger service and Microsoft’s Business Productivity Online Suite (BPOS).

Mid morning yesterday Twitter issued a status report stating that:

We are currently experiencing site stability issues. There may be intermittent issues loading and Twitter clients.  We’re working to fix it as soon as possible.

Reports from Twitter’s public status page, which is monitored by Watchmouse, indicated there were also problems accessing Twitter API’s over HTTP related to OAuth and/or the statuses/home_timeline method. Calling statuses/home_timeline with a GET request requires the requesting application to authenticate the user, then returns the 20 most recent status updates including retweets.

A similar message was displayed on the Twitter status page on Tuesday, with Watchmouse reporting similar OAuth API availability issues. Anectdotally, InfoQ experienced intermittent problems on Friday when accessing Twitter.

Earlier in the week Google apologized for problems associated with Blogger. In a blog post Eddie Kessler, Technical Lead for Blogger, explained that:

...during scheduled maintenance work Wednesday night, we experienced some data corruption that impacted Blogger’s behavior.

Google rolled back the blogger service to a pre-maintenance state and placed the service into read-only mode while the company worked through the problem, making it impossible to post to Blogger.

Microsoft also offered up an explanation for outages related to BPOS, pointing to both an Exchange problem handling malformed email, and an unrelated DNS server problem. Both the Microsoft and Google outages were reported on by InfoWeek.

Last month Cloud Foundry experienced storage failure problems on the heels of the widely publicized Amazon EC2 outage.

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

General Feedback
Marketing and all content copyright © 2006-2016 C4Media Inc. hosted at Contegix, the best ISP we've ever worked with.
Privacy policy

We notice you're using an ad blocker

We understand why you use ad blockers. However to keep InfoQ free we need your support. InfoQ will not provide your data to third parties without individual opt-in consent. We only work with advertisers relevant to our readers. Please consider whitelisting us.