Reddit, Roblox and Ring are just a tiny fraction of the 1,000-plus sites and services that were affected when Amazon Web Services went down, causing a major internet blackout.
The internet kicked off the week the way that many of us often feel like doing: by refusing to go to work. An outage at Amazon Web Services rendered huge portions of the internet unavailable on Monday morning. Sites and services including Snapchat, Fortnite, Venmo, the PlayStation Network and, predictably, Amazon, were unavailable off and on through the start of the day.
The outage began shortly after midnight PT, and took Amazon around 3.5 hours to fully resolve. Social networks and streaming services were among the 1,000-plus companies affected, and critical services such as online banking were also taken down.
The issues seemed to have been largely resolved as the US East Coast was coming online, but spiked again dramatically after 8 a.m. PT as work began on the West Coast.
AWS, a cloud services provider owned by Amazon, props up huge portions of the internet. So when it went down, it took many of the services we know and love with it. As with the Fastly and Crowdstrike outages over the past few years, the AWS outage shows just how much of the internet relies on the same infrastructure — and how quickly our access to the sites and services we rely on can be revoked when something goes wrong.
The reliance on a small number of big companies to underpin the web is akin to putting all of our eggs in a tiny handful of baskets. When it works, it’s great, but only one small thing needs to go wrong for the internet to come to its knees in a matter of minutes.How widespread was the AWS outage?
Just after midnight PT on Oct. 20, AWS first registered an issue on its service status page, saying it was «investigating increased error rates and latencies for multiple AWS services in the US-East-1 Region.» Around 2 a.m. PT, it said it had identified a potential root cause of the issue. Within half an hour, it had started applying mitigations that were resulting in significant signs of recovery.
«The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now», AWS said at 3.
