AWS outage hits much of the internet, impacting a long list of websites and apps, from Reddit to McDonald’s

Key Takeaways:

• The outage began around midnight Pacific Time, causing widespread access issues.
• The US-EAST-1 Region was hit, but the effects were felt internationally.
• Popular sites including Reddit, McDonald’s, and Lyft experienced issues.
• AWS posted critical updates as the event unfolded.
• By 3:35 a.m. PDT, AWS announced DNS issues were mitigated but throttling could persist.

The Outage Unfolds

In the early hours of the morning Pacific time, internet users across the globe began encountering errors and slowdowns on some of the most popular websites and apps. Restaurant apps, ride-sharing services, streaming platforms, and social media sites were all plagued by inconsistent performance, confusion, and sporadic downtime.

Key Updates from AWS

AWS first acknowledged the disruption on its Health Dashboard at 12:11 a.m. PDT, stating that it was “investigating increased error rates and latencies for multiple AWS services in the US-EAST-1 Region.” Subsequent notifications at 12:51 a.m. and 1:26 a.m. PDT confirmed the persistent nature of the outage, pointing particularly to “significant error rates” in requests made to the DynamoDB endpoint.

Why US-EAST-1 Affects the World

Despite the apparent concentration of the problem in one AWS region, the impact was global. Any website or application routing data through US-EAST-1 could suffer from downtime or lag. This cascading effect was felt by users far beyond the region’s physical location, underscoring the far-reaching reliance on AWS for critical online infrastructure.

Widespread Disruptions

Reports compiled by internet monitoring services like DownDetector revealed dozens of prominent platforms were experiencing issues. Reddit, Apple Music, Delta Air Lines, McDonald’s, Chime, and other household names appeared on the outage list. Some platforms were merely sluggish, while others were rendered temporarily inaccessible.

Mitigation and Aftermath

AWS posted its final major update at 3:35 a.m. PDT, declaring that “the underlying DNS issue has been fully mitigated.” However, the advisory also warned some throttling might still affect requests as services recovered. While many users saw their favorite sites come back online, sporadic outages continued to ripple throughout the morning.

Lingering Uncertainties

As of the latest reports, questions remain about the precise cause of the DNS disruptions, and AWS has not yet offered a detailed breakdown. The incident underscores just how dependent major platforms are on single points of data routing, with one localized failure sending shockwaves around the globe.

Table: AWS Health Dashboard Timeline

The events of this outage highlight the complexity of modern, cloud-based infrastructures and serve as a reminder of the interconnected nature of the internet. For now, AWS’s main advice to users is to check back if they continue to face roadblocks—and expect lingering throttling as normal operations resume.