AWS North Virginia data center outage – resolved

Posted by christhecaribou 1 day ago

230 points | 156 commentspage 3

OhMeadhbh 14 hours ago|

[flagged]

tomhow 13 hours ago|

Please don't do this here.

BugsJustFindMe 13 hours ago||

[flagged]

tailscaler2026 14 hours ago||

us-east-1 is down? shocking! stop putting SPOF services there. this location has had frequent issues for the past 15 years.

unethical_ban 11 hours ago|

This is correct... unless there is a specific requirement to be in that location for some kind of IXP or ultra low latency, I can't imagine putting mission-critical things in only that region.

rswail 4 hours ago|

So in the comments here we have the usual about us-east-1, it's centralized, it's a SPOF for AWS, they should fix it, don't put your stuff there, etc.

This was one data centre in one zone of a multi-zone region.

Yes IAM/R53 and others are centralized there, yes, reworking those service to be decentralized and cross-region would be a Good Thing. But us-east-1 is already multi-zone (6 with a seventh marked as "coming in 2026") with multi DC within zones. From memory, when a global service like IAM is out, it's more likely to be bugs in the implementation or dependency than a "if this was cross-region it wouldn't have died" issue.

But this wasn't an outage of any AWS global service this time. The only one that seemed to have more impact was/is MSK. Which is likely to be more of an issue with Kafka than anything AWS related.