Twitter does it again, it has gone down worldwide because of some unknown reason. Users are reporting inaccessibility to the website through PC and mobile app. We tried it on our Android Twitter app and nothing getting loaded on it. Its second time Twitter going down this year, previous time the cause of the issue was a “cascaded bug”.
Twitter is aware of the issues and made an announcement at (Jul 26, 2012 08:42 UTC-7) that “Users may be experiencing issues accessing Twitter. Our engineers are currently working to resolve the issue.”
Twitter homepage is now showing a dowmtime message acknowledging the issue. The message reads “Twitter is currently down for <%= reason %>. We expect to be back in <%= deadline %>. For more information, check out Twitter Status. Thanks for your patience!“.
While checking on the Twitter status, we could see Performance issues on most of the Twitter services like search,favorites,friends,users/show and critical Service disruption on Twitter major services like stream and statuses/home_timeline.
Ironically Twitter downtime comes just after Google’s Gtalk chat service hit by a worldwide outage, which now seems to be partially resolved. As far as Twitter remains down, you can track realtime update on the status by following the Google+ hashtag #Twitter.
Update: Twitter services are now back online. Twitter is now accessible on web, Mobile and apps after more than 1 hours of downtime.
Official Statement – Twitter Official statement on the outage
“We are sorry. Many of you came to Twitter earlier today expecting, well, Twitter. Instead, between around 8:20am and 9:00am PT, users around the world got zilch from us. By about 10:25am PT, people who came to Twitter finally got what they expected: Twitter.
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.
I wish I could say that today’s outage could be explained by the Olympics or even acascading bug. Instead, it was due to this infrastructural double-whammy. We are investing aggressively in our systems to avoid this situation in the future.
On behalf of our infrastructure team, we apologize deeply for the interruption you had today. Now — back to making the service even better and more stable than ever.“ - Mazen Rawashdeh, VP, Engineering (@mazenra)