AWS MINOR
Increased error rates and latencies
July 3, 2025 · 01:07 AM UTC – 02:07 AM UTC · Duration: 1h
Affected Services
Amazon DynamoDBAmazon Elastic Compute CloudAmazon Elastic Container ServiceAmazon Elastic Kubernetes ServiceAmazon EMR ServerlessAWS GlueAWS Lake FormationAWS VPCE PrivateLinkAmazon RedshiftAmazon SageMakerAmazon Simple Notification ServiceAWS Transit GatewayAWS Site-to-Site VPNAmazon WorkSpaces
Timeline
01:07 AM
We are investigating increased error rates and latencies for DynamoDB, which is affecting other AWS services in the US-EAST-1 Region.
01:28 AM
We can confirm increased error rates and latencies for DynamoDB in US-EAST-1 Region. This issue is also impacting other AWS services and workflows. We have identified the root cause to be a recent change in a subsystem responsible for request routing. Engineers were immediately engaged and began working to identify the root cause. We are actively engaged and working on multiple parallel paths to mitigate the issue. We will provide additional information within the next 30-60 minutes. We recommend customers continue to retry failed API requests where applicable.
01:39 AM
We are beginning to see initial signs of recovery and continue to work toward full resolution.
02:07 AM
Between 5:22 PM and 6:36 PM PDT, we experienced increased error rates and latencies for DynamoDB in the US-EAST-1 Region. This issue also impacted other AWS Services that use DynamoDB (such as ECS Task Launch Errors, EC2 Launch Errors, etc.). Engineers were automatically engaged and immediately began working to identify the root cause. At 6:17 PM we identified the root cause to be due to an issue with an automated change to one of DynamoDB’s subsystem responsible for request routing. Engineers immediately began reverting this change. We began observing initial signs of recovery as the change was being reverted, and had fully mitigated the issue by 6:36 PM. While the underlying issue has been resolved, Cloudwatch Logs will continue to backfill over the next few hours. We do not expect this issue to reoccur. The issue has been resolved and the service is operating normally.