This site uses cookies to improve your experience and to provide services and advertising. By continuing to browse, you agree to the use of cookies described in our Cookies Policy. You may change your settings at any time but this may impact on the functionality of the site. To learn more see our Cookies Policy.
OK
Dublin: 7 °C Tuesday 26 March, 2019
Advertisement

Twitter explains why the site went down yesterday

Twitter suffered its second outage in five weeks yesterday, with users unable to access the site for a couple of hours. Did it affect you?

The Twitter fail whale
The Twitter fail whale

TWITTER HAS SAID that an internal problem at its data centres caused yesterday’s outage which brought the site down for around two hours.

Apologising for the major fail whale yesterday Twitter has explained in a blog post that the down time was due to an “infrastructural double-whammy”.

Engineer Mazen Rawashdeh said that he wished the outage could be explained by the Olympics or a cascading bug, which was responsible for last month’s problems.

Rawashdesh said that the cause lay within Twitter’s data centres:

Data centres 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 [yesterday's] outage was the coincidental failure of two parallel systems at nearly the same time.

Well, there you go then.

Last month’s problems were claimed to be the work of a hacker group, but Twitter denied this. Rawashdesh said that Twitter is “investing aggressively” in its systems to avoid such problems in the future.

He also tweeted (when Twitter was back up of course) that it hadn’t been the easiest day at the office:

Did yesterday’s Twitter outage affect you? Let us know how in the comments section below…


Poll Results:

No, and I don't have an account (341)
No, and I have a Twitter account (254)
Yes, it affected me (82)



Yesterday: Google says Gchat problem “should be resolved”, as Twitter goes down>

  • Share on Facebook
  • Email this article
  •  

About the author:

Emer McLysaght

Read next:

COMMENTS (18)