Twitter was down globally from Tuesday Pacific Time 19th January (i.e. Wednesday WAT 20th January 2016) ; i.e. for those who noticed.
The Jack Dorsey led online social networking service was unavailable for up to eight hours in some regions. This affected its Web and mobile apps for a significant amount of time. Twitter first reported this issues at 10:41 AM Wednesday West African Time (Tuesday 1.41 a.m Pacific Time).
The company has come out to say it experienced an issue “related to an internal code change”. This meant that someone’s bad code caused the crash. But this has since been sorted and the company tweeted this at 4:12 AM Thursday WAT
This is not exactly what you would expect from a big company like Twitter but goes to show anything can happen anytime
The issue has now been resolved, thank you for your patience. More details: https://t.co/RqMBy0JuFE
— Twitter Support (@TwitterSupport) January 19, 2016
It turns out that Twitter that caused its Web and mobile apps to go down for a significant amount of time. In other words, someone wrote some bad code that crashed things for a while. It was an uncharacteristically long outage for Twitter, which first tweeted about it at 1:41 am PT, and didn’t confirm that everything was back up and running until more than eight hours later. Considering the real-time nature of the product, eight hours is a very long time.
