Is AWS Down Today? AWS Suffers Major Outage in US-East-1 as Data Center Overheating Disrupts EC2
AWS's latest US-East-1 meltdown exposes the fragility of concentrating the internet's backbone in one overheated Virginia data center.
AWS's busiest region went down Thursday because one Northern Virginia data center overheated, crippling EC2 instances and Amazon Elastic Block Store volumes for thousands of businesses, websites, and applications worldwide.
The outage began early in the morning, hitting the use1-az4 availability zone hardest with elevated error rates, failed instance launches, and latency. Engineers scrambled to restore cooling capacity while customers without multi-region setups scrambled to activate failover plans or shift traffic to on-premises systems. Smaller firms and startups suffered complete downtime for hours during peak business periods.
AWS confirmed the root cause as "elevated temperatures within a single data center facility" and reported steady progress by late afternoon, though full recovery was still hours away. No security breach or data loss occurred, but the incident reignited warnings about concentration risks in Northern Virginia, which powers a massive share of global internet workloads.
Downdetector lit up with complaints concentrated in the eastern United States. Services built on EC2 and EBS, including databases, websites, and container workloads, took the heaviest hits, while other AWS regions stayed largely operational. The company updated its Service Health Dashboard, contacted large enterprise customers directly, and signaled that service credits would follow for affected accounts.
This marks another notable incident for AWS in 2026 after previous regional disruptions. Competitors Microsoft Azure and Google Cloud wasted no time using the event in marketing to tout their own redundancy features, yet the episode underscores that every major provider faces occasional infrastructure challenges. The real problem is the convenience and ecosystem lock-in that keep organizations heavily dependent on one provider and one region.
Organizations were advised to monitor the AWS Health Dashboard, activate multi-AZ or multi-region failover, review disaster recovery plans, and document impacts for credits, practical steps that many apparently hadn't fully tested. As recovery continues, the post-incident review will matter less than whether customers finally treat these recurring reminders as proof that single-provider concentration is a choice, not an inevitability.
Original reporting: Ibtimes.com.au.
More in Business
- IMF Chief Warns of Economic Divergence and Debt Risks Amid Artificial Intelligence Boom
Kristalina Georgieva suggests that while AI could significantly boost global growth, it simultaneously threatens to widen inequality and exacerbate inflationary pressures and public debt burdens.
- California Limits Utility Profits and Expands Home Energy Role
Gov. Gavin Newsom signed laws capping utility returns on lower-risk projects and accelerating virtual power plant development.
- Lyft to Pay $272.5 Million in Record California Wage-Theft Settlement
Largest such settlement in state history resolves claims that Lyft misclassified drivers as independent contractors from 2016 to 2020, denying them core wage protections.