On March 10, 2025, Twitter users across the globe experienced widespread disruptions in service while attempting to access their accounts. The outage impacted users worldwide, but a significant portion of the disruptions were concentrated in the western regions, particularly the United States.
As the downtime persisted, many frustrated users took to platforms like Down Detector, a website that tracks and reports service outages, to share their experiences and stay updated on the situation.
In terms of timing, the issue began to affect Asian users around 3 PM local time, while users in the West noticed disruptions earlier in the day, depending on their geographical location. The error message displayed to users was a simple, yet puzzling one: “Something web wrong, try reloading the page.”
Naturally, speculation about the cause of the outage began to spread quickly. Some users immediately assumed the disruption was the result of a cyber-attack targeting Twitter’s infrastructure. Many of these theories gained traction on platforms like Signal and Telegram, where some users suggested that state-sponsored threat actors from Ukraine might have been behind the attack, citing tensions between Ukrainian President Volodymyr Zelenskyy and former U.S. President Donald Trump from a recent diplomatic incident.
However, these rumors were soon debunked. A source from Twitter clarified that the issue was not caused by an external attack but by a technical glitch stemming from a software rollout. The problematic update was promptly rolled back, restoring services to normal.
The duration of the downtime varied depending on the user’s location, with interruptions lasting anywhere from 24 to 60 minutes. Despite this, some users, particularly those on Facebook, expressed frustration, claiming they had been unable to access their accounts for several hours.
In conclusion, while many users were quick to jump to conclusions about a cyber-attack, it turned out that the Twitter outage was caused by a simple IT glitch rather than any form of malicious interference. The issue was swiftly addressed, and services were restored without further incident.
Ad
Join our LinkedIn group Information Security Community!
