A widespread service disruption occurred across numerous online platforms and applications following a major outage at Amazon Web Services (AWS) early Monday morning. The incident, which began around 12:11 AM ET and lasted approximately three and a half hours, stemmed from a Domain Name System (DNS) resolution issue within AWS's critical US-East-1 region in Northern Virginia, a central hub for many internet services. This event underscores the profound dependency of modern digital infrastructure on cloud providers like AWS, as the failure swiftly cascaded to impact a diverse array of consumer, financial, and AI-driven services globally.
The root cause of the outage was identified as a problem with DNS resolution affecting the DynamoDB API endpoint, which subsequently triggered a domino effect across interconnected systems. AWS acknowledged the issue by observing elevated error rates and increased latency across several of its core services, including EC2 (Elastic Compute Cloud), Lambda (serverless computing), and DynamoDB (NoSQL database service). This confirmation came after initial reports indicated widespread slowdowns and service interruptions.
The impact of the AWS failure was extensive, affecting major consumer applications such as Snapchat, Amazon's Alexa, Roblox, and Hulu. Financial services like Coinbase and Robinhood, as well as AI platforms such as Perplexity, also experienced significant disruptions. Even Amazon's own e-commerce platform, Amazon.com, and its streaming service, Prime Video, were not immune, suffering partial outages. Beyond North America, the outage's reach extended to Europe, with major banks in the UK and several government websites reporting downtime, illustrating the global interconnectedness of digital services through AWS infrastructure.
Thousands of users began reporting issues shortly after 3:00 AM ET, with the volume of complaints escalating rapidly across social media platforms. By mid-morning, over 14,000 outage reports were specifically logged for Amazon services. The disruption extended into smart home devices, with systems like Ring doorbells and Alexa-enabled devices losing functionality or connectivity. This widespread failure ignited conversations among users and industry experts alike regarding the internet's heavy reliance on a few dominant cloud providers and the potential single points of failure this concentration creates.
AWS engineers promptly initiated efforts to restore services, pursuing multiple parallel recovery paths. Their investigation pinpointed network gateway errors in the US East Coast region as a primary area of focus. By 6:35 AM ET, AWS announced that the underlying DNS issue had been fully mitigated, and most services were operating normally. However, some applications, such as Ring and Chime, experienced slower recovery times.
Amazon has advised users still encountering issues with DynamoDB service endpoints in US-EAST-1 to clear their DNS caches, noting that while the core problem is resolved, some requests might still be throttled as systems return to full operational capacity. This significant incident will undoubtedly prompt many organizations to re-evaluate their reliance on AWS, and particularly its US-East-1 region. Amazon is expected to release a comprehensive postmortem report in the coming days, detailing the precise sequence of events and lessons learned from this major internet disruption.
