We are getting reports that Twitter is down for many users including us. At the moment we are not sure about the extent of the outage. The disruption in services comes nearly hours after Google reported a worldwide outage of its Gtalk IM services. We are not sure weather the two incidents are related to each other. Also Read - Samsung Galaxy A22 5G India launch nearing as support page goes live
Earlier in the day, Gtalk users started reporting a disruption in the service, however an hour ago Google claims to have partially restored the service. Google is yet to determine the cause of the outage and it is actively updating its Google apps dashboard with news regarding the outage. Also Read - PS5 restock June 2021: Sony PlayStation 5 goes out of stock within minutes of going live
We are tracking the development and will post updates accordingly. Also Read - Beware! Delete these 20 malicious apps promising Minecraft mods immediately
UPDATE: Phew! We continue to live! Twitter is back and has acknowledged the outage and has blamed failure of two parallel systems in its datacenters. Here’s the official statement the company posted on its blog.
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)