Update:
June 13 6:30 p.m. PDT: The Associated Press reports that Amazon says AWS is operating normally.
Below is a report from AWS, showing its outages over the past 24 hours.
Update from AWS:
Jun 13 3:42 p.m PDT Between 11:49 AM PDT and 3:37 PM PDT, we experienced increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region. Our engineering teams were immediately engaged and began investigating. We quickly narrowed down the root cause to be an issue with a subsystem responsible for capacity management for AWS Lambda, which caused errors directly for customers (including through API Gateway) and indirectly through the use of other AWS services. Additionally, customers may have experienced authentication or sign-in errors when using the AWS Management Console, or authenticating through Cognito or IAM STS. Customers may also have experienced issues when attempting to initiate a Call or Chat to AWS Support. As of 2:47 PM PDT, the issue initiating calls and chats to AWS Support was resolved. By 1:41 PM PDT, the underlying issue with the subsystem responsible for AWS Lambda was resolved. At that time, we began processing the backlog of asynchronous Lambda invocations that accumulated during the event, including invocations from other AWS services.
As of 3:37 PM PDT, the backlog was fully processed. The issue has been resolved and all AWS Services are operating normally.
Jun 13 2:29 p.m PDT Lambda synchronous invocation APIs have recovered. We are still working on processing the backlog of asynchronous Lambda invocations that accumulated during the event, including invocations from other AWS services (such as SQS and EventBridge). Lambda is working to process these messages during the next few hours and during this time, we expect to see continued delays in the execution of asynchronous invocations.
Amazon Web Services (AWS) earlier today has confirmed an outage affecting a large number of companies and websites that rely on the cloud provider. From 11:49 am PDT, customers started experiencing errors and latencies with multiple cloud services within its US-EAST-1 Region. A little more than two hours later, at 2:00 pm PDT, AWS claimed many AWS services were fully recovered and it was continuing to work on the full recovery.
According to the cloud provider, the root cause of the issue was traced to “a subsystem responsible for capacity management for AWS Lambda, which caused errors directly for customers (including through API Gateway) and indirectly through the use by other AWS services.”
AWS Lambda is a serverless computing service that enables customers to run codes for diverse applications. Beyond AWS Lambda, other services like CloudFormation and Connect were reported to be suffering service degradations.
“Customers may experience authentication or sign-in errors when using the AWS Management Console, or authenticating through Cognito or IAM STS. Customers may also experience intermittent issues when attempting to call or initiate a chat to AWS Support,” the company noted.
The first confirmation of the outage came shortly after 12 pm PDT, according to the AWS Service Health dashboard, which specified the cloud provider was investigating increased error rates and latencies had been identified in the Northern Virginia region. As of 2:00 PM PDT, the provider confirmed that “many AWS services are now fully recovered and marked Resolved on this event. We are continuing to work to fully recover all services.”
However, it remains unclear when full cloud services will be completely restored.