Overview
- The incident began around 3:11 a.m. ET with increased error rates and latencies across multiple AWS services centered on the US‑EAST‑1 region in Northern Virginia.
- AWS said a DNS resolution problem affecting the DynamoDB API was the likely root cause, reported the core issue fully mitigated by about 6:35 a.m. ET, and cautioned that some requests would remain throttled during recovery.
- Follow‑on effects included connectivity issues, backlogs and rate limits on new EC2 instance launches, with AWS advising customers to avoid pinning deployments to specific Availability Zones to aid stabilization.
- Dozens of platforms experienced disruptions, including Snapchat, Roblox, Fortnite, Coinbase, Robinhood, Amazon’s own services, UK government site HMRC, and banking and airline systems reported by users and monitors.
- Monitoring firms and experts noted impacts concentrated in US‑EAST‑1 with global ripple effects, and early assessments pointed to a technical fault rather than a cyberattack, renewing calls for stronger cloud resilience.