Technology news and discussion on TalkFuse.
AWS disruption in us-east-1 drew little attention before dawn on Sunday
AWS experienced a significant incident in its us-east-1 region on 15 November, disrupting many of its key services, but it drew little public attention. The article argues that the quiet response reflected the timing and nature of the disruption, alongside bigger outages that dominated the news.
AWS reported sign-up, authentication and connectivity problems from 3:05am Pacific time; engineers were engaged five minutes later, while its status page took 93 minutes to post an incident notice. The all-clear came at 6:53am. The most affected service, IAM Identity Center, is used by engineers to access AWS accounts, and the incident happened before dawn on a Sunday, limiting consumer reports to Downdetector. The article also notes that a Microsoft 365 outage and a nationwide air traffic ground stop were attracting attention at the time.
In short
- AWS services were disrupted in us-east-1 on 15 November.
- The incident lasted from early morning until 6:53am Pacific time.
- Its timing and limited consumer impact kept it out of the spotlight.
Read the full article at the source →
Originally published by The Register as “AWS got hit by an outage too. Here’s why you didn’t hear about it”.