Amazon Web Services (AWS) successfully restored its cloud operations in the US-EAST-1 region on November 15 following a significant outage that affected account signups, authentication processes, and network connectivity. The disruption began at 3:05 a.m. PST and was fully resolved by 6:21 a.m. PST, impacting some users for over three hours.
Impact on Cloud Services
The outage disrupted several AWS services, including the IAM Identity Center used for accessing the AWS Console and other services like Kiro and Amazon Connect. AWS also reported issues with account sign-ups during the incident. Initial reports from AWS indicated that their engineers were addressing connectivity problems and issues related to account access and new registrations.
According to AWS Support, the disruption was being actively investigated, with updates provided to customers via social media channels. The affected services included authentication and network connectivity, both of which were critical for users relying on AWS for business operations.
Timeline of Recovery Efforts
AWS engineers were promptly deployed at 3:10 a.m. PST, shortly after the outage commenced. Their efforts focused on identifying the root cause and restoring services. By 5:20 a.m. PST, authentication issues were largely resolved, and most AWS services returned to normal functionality, as per AWS’s updates.
Despite resolving authentication problems, network connectivity took longer to restore, especially for users dependent on Network Load Balancers (NLBs) within a specific cell. These users continued to face connectivity challenges until 6:21 a.m. PST, illustrating that while authentication was restored, network issues persisted for certain services.
Context and Historical Outages
The latest outage in the US-EAST-1 region follows previous incidents, such as delays in EC2 deployments in October 2025 that affected related container services. Although this historical context provides insight into regional challenges, there is no evidence linking these incidents to a common cause.
Notably, the AWS disruption occurred after a significant Microsoft 365 outage, which impacted services like Exchange Online and Teams. These occurrences underscore how vulnerabilities in cloud infrastructure can simultaneously affect multiple business and security services.
AWS’s statement did not elaborate on a specific root cause or suggest a cyberattack. The findings focused on authentication and connectivity issues, suggesting the event was a service availability problem rather than a security breach. Further technical details are awaited to provide a comprehensive understanding of the incident.
For organizations relying on cloud services, such incidents highlight the importance of robust contingency planning and real-time threat intelligence to mitigate potential impacts effectively.
