aws[RESOLVED] Increased error rates and increased latencies
Started
Aug 13, 2025, 5:56 PM UTC
Resolved
Aug 13, 2025, 7:15 PM UTC
Duration
1h 19m
Services impacted
1
Event reference: arn:aws:health:us-gov-east-1::event/DYNAMODB/AWS_DYNAMODB_OPERATIONAL_ISSUE/AWS_DYNAMODB_OPERATIONAL_ISSUE_17E2E_6744B0582C8
awsdown.com independently monitors the public AWS Health Dashboard. How we source data.
Impact
Between 9:24 AM and 11:31 AM PDT we experienced increased latency and error rates affecting DynamoDB Streams in the US-GOV-EAST-1 Region. Our engineers were engaged by 9:40 AM and began investigating. By 10:43 AM root cause was understood to have been caused by a planned configuration change to the network that supports DynamoDB Streams and work to correct this configuration began. During this time, attempts to read data from DynamoDB Streams would have failed. Services which depend on DynamoDB Streams have caught up on processing data that was published to streams during this time. At this time the issue is resolved and the service is operating normally.
Affected services (1)
Affected regions
Timeline
Verbatim updates as published by AWS, newest first (times in UTC).
- Resolved
Between 9:24 AM and 11:31 AM PDT we experienced increased latency and error rates affecting DynamoDB Streams in the US-GOV-EAST-1 Region. Our engineers were engaged by 9:40 AM and began investigating. By 10:43 AM root cause was understood to have been caused by a planned configuration change to the network that supports DynamoDB Streams and work to correct this configuration began. During this time, attempts to read data from DynamoDB Streams would have failed. Services which depend on DynamoDB Streams have caught up on processing data that was published to streams during this time. At this time the issue is resolved and the service is operating normally.
- Monitoring
We are beginning to see signs of recovery and seeing Streams processing traffic catch up. Services that depend on DynamoDB streams will recover as they catch up. We continue to monitor the situation and will update this post within the next 30 minutes.
- Monitoring
At 9:20 AM PDT we began experiencing increased latency and error rates impacting DynamoDB Streams. Engineers were engaged shortly after and began investigating the issue. We have identified the root cause to be related to a planned configuration change to the supporting network. Work has started on mitigating this impact and we expect to know more within the next 30 minutes. At this time there are no workarounds available.
- Investigating
We are investigating increased error rates and increased latencies in the US-GOV-EAST-1 Region.
Resolution
Between 9:24 AM and 11:31 AM PDT we experienced increased latency and error rates affecting DynamoDB Streams in the US-GOV-EAST-1 Region. Our engineers were engaged by 9:40 AM and began investigating. By 10:43 AM root cause was understood to have been caused by a planned configuration change to the network that supports DynamoDB Streams and work to correct this configuration began. During this time, attempts to read data from DynamoDB Streams would have failed. Services which depend on DynamoDB Streams have caught up on processing data that was published to streams during this time. At this time the issue is resolved and the service is operating normally.