Twitter: a "double-whammy" caused latest outage

Earlier today, the over 140 million users of Twitter found that for the better part of an hour today, the service simply was not working. This was the second time in about five weeks that Twitter had suffered a system wide extended outage. It got hit with a few hours of downtime in late June. After its systems were repaired, Twitter said the issue was due to "a cascaded bug in one of our infrastructure components."

So what happened today? In a post on its official blog, Twitter's vice president of engineering Mazen Rawashdeh stated:

The cause of today’s outage came from within our data centers. Data centers are designed to be redundant: when one system fails (as everything does at one time or another), a parallel system takes over. What was noteworthy about today’s outage was the coincidental failure of two parallel systems at nearly the same time.

Rawashdeh called the issue an "infrastructural double-whammy" which we assume is a highly technical and little used term. He apologized for the downtime and added, "We are investing aggressively in our systems to avoid this situation in the future." It will be interesting to see how Twitter holds up during the next two weeks, when the 2012 Olympics in London will be front and center on social networking sites.

Source: Twitter blog

Report a problem with article
Previous Story

Battlefield 3: Aftermath DLC officially revealed

Next Story

Zuckerberg shoots down Facebook phone rumors

8 Comments

Commenting is disabled on this article.

I didn't even notice it was down. The only issue I had yesterday was that TweetDeck stopped pulling in Facebook updates for a few hours last night (I'm running the old pre-acquisition Adobe Air version though, so who knows, it might be a bug).

MightyJordan said,
I didn't even notice it was down. The only issue I had yesterday was that TweetDeck stopped pulling in Facebook updates for a few hours last night (I'm running the old pre-acquisition Adobe Air version though, so who knows, it might be a bug).

why not use the HTML5-based chrome app? it's really fast and lightweight.

FalseAgent said,

why not use the HTML5-based chrome app? it's really fast and lightweight.

There's a few features in the old Adobe Air version which are keeping me from switching: realtime updates (that's a huge one, BTW), showing retweets in the mentions column, and being able to show the follower count below each user's tweet.

That's just off the top of my head; there's probably one or two more. Personally, I'm willing to put up with the regular freezing and slow startup for those features; they've become invaluable to me.

MightyJordan said,

There's a few features in the old Adobe Air version which are keeping me from switching: realtime updates (that's a huge one, BTW), showing retweets in the mentions column, and being able to show the follower count below each user's tweet.

That's just off the top of my head; there's probably one or two more. Personally, I'm willing to put up with the regular freezing and slow startup for those features; they've become invaluable to me.


I see. The HTML5 version has support for live updates now. No retweets in the mention column yet, though.

Dot Matrix said,
Two systems failing at nearly the same time? Suspicious...

Well it happened to amazon too.

cyberdrone2000 said,
"aploized"?

This just in, writers make mistakes, more at 7! Now to the weather, Ollie what's it like down town?
"COLD!"
Thanks Ollie