AWS Restores Services in US-EAST-1 After Hours-Long Outage Disrupts Cloud Operations

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Amazon Web Services restored operations in its US-EAST-1 region on November 15 after an outage disrupted account signups, authentication, and network connections. Problems began at 3:05 a.m. PST, and the last network issue was resolved at 6:21 a.m. PST, leaving some customers affected for more than three hours.

The disruption affected customers using IAM Identity Center to access the AWS Console and services including Kiro and Amazon Connect. AWS also reported failed sign-up requests. Its initial service notice confirmed that engineers were investigating connectivity issues alongside problems with account access and new registrations.

Authentication Restored Before Network Recovery

AWS engineers were automatically engaged at 3:10 a.m. PST, five minutes after the incident began. Teams investigated the cause while working to restore service. Authentication issues were fully resolved by 5:20 a.m. PST, when most affected AWS services also returned to normal operation, according to the company’s update.

However, network recovery took longer for a subset of customers using Network Load Balancers, or NLBs, within a single cell. Those customers continued to experience connectivity problems until 6:21 a.m. PST. The separate recovery times show why successful authentication alone did not mean every affected service connection had recovered.

In its final recovery statement, AWS listed the main disruption window as 3:05 a.m. to 6:10 a.m. PST while separately confirming the final NLB fix at 6:21 a.m. PST. The company advised customers to retry failed requests and said all AWS services were operating normally.

Previous Cloud Outages

The incident follows earlier problems in the same region. Cyber Security News previously covered AWS US-EAST-1 delays affecting EC2 deployments, which also disrupted related container services in October 2025. That event provides historical context, but available evidence does not establish a shared cause with the latest outage.

The disruption also came after a major Microsoft 365 outage affected Exchange Online, Teams, SharePoint, Copilot, and Defender XDR. Microsoft reported unavailable servers, failed health checks, and capacity problems during recovery. The separate incidents highlight how failures in shared cloud systems can interrupt access to several business and security services at once.

AWS’s recovery statement did not disclose a detailed root cause or identify a cyberattack. Its findings described authentication and connectivity failures. Until further technical details emerge, the incident should be treated as a service availability event rather than evidence of malicious activity or a confirmed security breach.

Give your SOC the alert context to stops incidents quickly. Integrate Threat Intel from 16K SOCs.

The post AWS Restores Services in US-EAST-1 After Hours-Long Outage Disrupts Cloud Operations appeared first on Cyber Security News.