If you woke up to broken apps and websites, you’re not alone. Today’s AWS Outage caused widespread disruption across major services. Early reports tied the event to issues in AWS’s US-EAST-1 (N. Virginia) region, with impacts rippling to popular consumer and business platforms.
What happened (in plain English)
AWS reported increased error rates across multiple services in US-EAST-1. Initial updates pointed to DNS resolution problems affecting DynamoDB API endpoints, with AWS noting full mitigation of the DNS issue in the early morning Pacific hours. Later updates and reporting also referenced EC2 networking/NLB monitoring components as contributing factors during recovery, which explains why some apps flickered in and out while others recovered steadily.
Is it over?
By late morning/early afternoon U.S. time, AWS reported significant recovery with continued work to fully restore normal operations. That means many apps may work again, but you could still see periodic slowdowns or login errors as caching clears and back-end systems catch up.
What your team can do right now
- Verify status: Check the AWS Health/Status dashboards and your vendors’ status pages for service-specific guidance. AWS Health
- Clear DNS/cache: If your app still misbehaves, clear DNS/application caches and restart critical services to pick up corrected endpoints. (AWS recommended cache flush during recovery.) Statesman
- Review runbooks: Capture what broke, what alerts fired, and where the bottlenecks were. Prioritize any single-region or single-service dependencies.
- Communicate: Set customer expectations and note that stabilization can be uneven across geographies and features.
