Major AWS Outage Disrupts Internet Services Across the USA

A significant disruption hit Amazon Web Services (AWS) early on October 20, 2025, causing widespread outages for popular apps and websites, mainly in the USA but with some international effects. This event, linked to issues in the US-EAST-1 region, affected everything from social media to gaming and finance, but recovery was achieved by mid-morning.

Key Points

• The outage began around 3:11 AM ET, stemming from elevated error rates and a DNS resolution issue with AWS’s DynamoDB service, leading to cascading failures.
• Affected platforms included Snapchat, Roblox, Fortnite, Venmo, and many others, with user reports peaking in the early hours.
• Recovery started showing signs by 5:37 AM ET, with most services back online by 8:20 AM ET, though some lingering delays occurred.
• No evidence of malicious activity; it highlights risks in cloud dependency, prompting calls for better redundancy.

What Happened

Early reports indicated problems in AWS’s US-EAST-1 region, a key hub for internet infrastructure. Users faced login issues, app crashes, and service unavailability starting around midnight PT. Outage trackers like Downdetector saw spikes in complaints for services reliant on AWS.

Recovery Efforts

AWS acknowledged the issue quickly and reported progress toward resolution. By mid-morning, the company stated the problem was fully mitigated, with backlogs cleared. Some services, like Ring, took longer to stabilize.

Implications

This incident disrupted daily activities, from payments to entertainment, and echoed past events like the 2024 CrowdStrike outage. It underscores the need for diversified tech setups to avoid similar widespread impacts. For more on AWS architecture.

On October 20, 2025, a major outage at Amazon Web Services (AWS) sent shockwaves through the digital world, temporarily knocking out numerous popular apps and websites across the United States and beyond. Originating in the US-EAST-1 region in Northern Virginia—a critical nerve center for global internet operations—the disruption began around 3:11 AM ET (12:11 AM PT), triggered by increased error rates, latencies, and a specific DNS resolution issue affecting the DynamoDB API, a vital database service for quick data handling in countless applications. This event not only frustrated millions of users but also spotlighted the vulnerabilities inherent in our heavy reliance on cloud computing providers, prompting renewed discussions on building more resilient systems.

The outage’s timeline unfolded rapidly in the pre-dawn hours. AWS first noted the problem on its health dashboard shortly after onset, with impacts extending to at least 28 services, including DynamoDB, SQS, EventBridge, and CloudTrail. User reports flooded platforms like Downdetector, peaking around 7:50 AM ET with over 50,000 complaints across Amazon-related services, including Alexa and Ring. While primarily concentrated in the USA, the global nature of affected apps led to secondary disruptions in regions like Europe and Asia, where users of services such as Snapchat and Fortnite experienced intermittent issues.

As the situation escalated, AWS engineers sprang into action, providing regular updates via their status page. Initial recovery signs appeared by 5:37 AM ET, with partial stabilization in certain availability zones and clearances of backlogs in services like SQS. By 6:00 AM ET, significant progress was evident, and the company advised users to retry failed requests, avoid specific zones, or flush DNS caches to aid restoration. Full mitigation was announced around 8:20 AM ET, marking roughly five hours of peak disruption, though some residual delays persisted due to queued operations. Notably, devices like Ring doorbells faced extended outages, affecting users in the US and UK even as broader platforms recovered. AWS committed to conducting a thorough root cause analysis post-resolution, emphasizing that the incident appeared technical in nature with no signs of cyberattacks.

The breadth of impacted services was staggering, touching over 40 platforms that depend on AWS for backend support. Social media apps like Snapchat and Signal suffered from login failures and messaging glitches, while gaming behemoths including Roblox, Fortnite, Pokémon GO, Clash Royale, and Clash of Clans dealt with server disconnects and loading errors, leaving players stranded. Financial tools such as Venmo, Coinbase, Robinhood, and Chime experienced transaction halts and app crashes, potentially stalling payments and trades during critical hours. Entertainment services like Hulu, Disney+, and Prime Video faced buffering and content loading problems, disrupting streaming sessions. Productivity and other apps, including Zoom, Canva, Lyft, McDonald’s, Perplexity, and Wordle, reported various issues from meeting interruptions to order failures and search malfunctions. Executives from affected companies, such as Perplexity’s CEO Aravind Srinivas, publicly confirmed the AWS link via social media.

To provide a clear overview, the following table aggregates key categories of affected services, specific examples, reported issues, and approximate peak report volumes based on outage trackers and media reports:

Category	Affected Services	Reported Issues	Peak Reports (Approx.)
Social Media	Snapchat, Signal, WhatsApp	Login failures, message delivery errors, app crashes.	10,000+
Gaming	Roblox, Fortnite, Pokémon GO, Clash Royale, Clash of Clans, Epic Games Store	Server disconnections, inability to join games, loading failures.	15,000+
Finance/Payments	Venmo, Coinbase, Robinhood, Chime, Lloyd’s Bank	Transaction failures, balance inaccessible, app not loading.	8,000+
Entertainment	Hulu, Disney+, Prime Video, Tidal	Streaming interruptions, content not loading, buffering issues.	5,000+
Productivity/Other	Zoom, Slack, Canva, Duolingo, Lyft, Ring, Alexa, McDonald’s, Perplexity, Wordle, Gov.uk, Strava	Meeting disruptions, file access issues, device malfunctions, search failures, order problems.	12,000+

This compilation draws from sources like Downdetector and company statements, illustrating the outage’s extensive reach—collectively surpassing 50,000 reports at its height. The USA experienced the most severe effects due to the region’s location, but interconnected global services amplified the fallout.

Beyond technical glitches, the outage had tangible economic and social consequences. Businesses incurred productivity losses from halted operations, while everyday users grappled with disrupted routines—ranging from unprocessed Venmo transfers to aborted Zoom calls and failed McDonald’s orders. In the financial realm, platforms like Robinhood and Coinbase’s downtime could have influenced market activities, though no major volatility was reported. Secure communication apps like Signal being offline raised concerns about implications for sensitive discussions, including free speech in volatile situations. Social media platforms that remained functional, such as X (formerly Twitter), became hubs for user venting, with memes and complaints about “half the internet” going dark proliferating.

Experts likened this to previous high-profile disruptions, such as the 2024 CrowdStrike incident, which similarly exposed systemic fragilities. The event has fueled calls for greater diversification beyond dominant providers like AWS, Microsoft Azure, and Google Cloud, advocating for multi-cloud strategies, enhanced redundancy, and regular infrastructure audits. In retrospect, the relatively swift resolution—within hours—highlights AWS’s robust response mechanisms, yet it also reveals persistent risks in centralized cloud ecosystems. As AWS proceeds with its analysis, stakeholders are encouraged to explore hybrid approaches to safeguard against future incidents, ensuring the digital backbone remains reliable in an increasingly connected world.

Frequently Asked Questions (FAQs)