AWS Outage Explained: What Went Wrong and Why Half the Internet Crashed

A large-scale outage at Amazon Web Services (AWS) on Monday disrupted major online platforms and essential digital services across the world. The breakdown, traced to a fault in AWS's core network, left millions of users without access to apps, websites, and even critical financial services. The incident highlighted how dependent the global internet has become on a single cloud provider.

Massive Outage Brings Global Internet to a Halt

Amazon's cloud division, AWS, experienced a widespread technical failure that caused several popular platforms, including Snapchat, WhatsApp, Reddit, and Signal, to go offline for hours. Users across continents faced problems sending messages, streaming content, and conducting online transactions.

Financial and trading platforms such as Coinbase, Robinhood, and Venmo were also hit, along with UK banking sites like Lloyds Bank and Bank of Scotland. Even Amazon's own services, including Alexa, Ring, and Prime Video, were disrupted.

The outage started in AWS's US-EAST-1 region in northern Virginia, one of its oldest and most vital data hubs. Amazon initially reported "significant error rates and latencies" before identifying the main cause as a Domain Name System (DNS) malfunction that prevented websites and applications from reaching their servers.

Millions of Users and Services Affected

The disruption affected several sectors including finance, education, media, and entertainment. Popular platforms such as Reddit, Roblox, Fortnite, Disney+, Airbnb, and Duolingo stopped functioning. In the UK, services from Vodafone, BT, and HMRC also went offline. Smart devices such as Ring doorbells and Kindle services were temporarily impacted.

According to Downdetector, more than 11 million users reported AWS-related problems. Ookla noted that over 4 million individual users faced disruptions. Thousands of companies relying on AWS for cloud hosting and data storage had to pause or reduce operations.

Root Cause: DNS and Network Health Failure

AWS confirmed that the outage resulted from a failure in its DNS system combined with a malfunction in its network health monitoring subsystem. This problem affected key services such as Elastic Compute Cloud (EC2) and Network Load Balancer.

Amazon's engineers began mitigation efforts shortly after identifying the issue around 0711 GMT. By 1030 GMT, the company announced that the DNS fault had been "fully mitigated," but clearing the data backlog took several more hours. AWS later confirmed that "all services have returned to normal operations," though minor delays persisted in some internal systems.

Experts compared the recovery process to restoring electricity after a major blackout, explaining that systems needed to be brought back gradually to prevent overload. AWS also advised customers to clear DNS caches to regain full connectivity.

Recurring Problem and Broader Implications

This was the third major AWS outage linked to the US-EAST-1 region since 2020. The data center serves as the default region for many AWS services, making it an essential but vulnerable part of global digital infrastructure.

"The world now runs on the cloud," said Patrick Burgess of the UK's Chartered Institute for IT. "When a major provider like AWS goes down, the ripple effects are immediate and widespread."

Experts cautioned that the internet's increasing reliance on a few cloud providers such as AWS, Microsoft Azure, and Google Cloud creates potential risks. Although Amazon confirmed that there was no data loss or cyberattack, analysts estimate that the downtime caused massive global financial losses due to halted transactions and reduced productivity.

Amazon said it would release a detailed post-incident report soon. The event serves as a reminder of how fragile global digital systems can be and how disruptions in one major provider can affect millions worldwide.