aws[RESOLVED] Increased error rates and latency
Started
Aug 27, 2025, 7:01 PM UTC
Resolved
Aug 27, 2025, 7:16 PM UTC
Duration
14m
Services impacted
1
Event reference: arn:aws:health:global::event/IAM/AWS_IAM_OPERATIONAL_ISSUE/AWS_IAM_OPERATIONAL_ISSUE_A5508_C0E97449FDD
awsdown.com independently monitors the public AWS Health Dashboard. How we source data.
Impact
Between 11:35 AM and 11:58 AM PDT, we experienced increased API error rates for the IAM service in the EU-SOUTH-2 Region. Engineers were automatically alerted at 11:37 AM and began working on investigating root cause and mitigating impact. By 11:43 AM we understood the issue to be related to a planned networking configuration change. The change was reverted and we began seeing significant signs of recovery at 11:58 AM. During this time, other AWS services' APIs and workflows may also have experienced increased error rates and latencies. The issue is resolved and all AWS services are operating normally.
Affected services (1)
Affected regions
Timeline
Verbatim updates as published by AWS, newest first (times in UTC).
- Resolved
Between 11:35 AM and 11:58 AM PDT, we experienced increased API error rates for the IAM service in the EU-SOUTH-2 Region. Engineers were automatically alerted at 11:37 AM and began working on investigating root cause and mitigating impact. By 11:43 AM we understood the issue to be related to a planned networking configuration change. The change was reverted and we began seeing significant signs of recovery at 11:58 AM. During this time, other AWS services' APIs and workflows may also have experienced increased error rates and latencies. The issue is resolved and all AWS services are operating normally.
- Monitoring
We are seeing initial signs of recovery. We will provide an additional update by 12:20 PM PDT.
- Investigating
We are investigating increased error rates and latency issues in the EU-SOUTH-2 Region.
Resolution
Between 11:35 AM and 11:58 AM PDT, we experienced increased API error rates for the IAM service in the EU-SOUTH-2 Region. Engineers were automatically alerted at 11:37 AM and began working on investigating root cause and mitigating impact. By 11:43 AM we understood the issue to be related to a planned networking configuration change. The change was reverted and we began seeing significant signs of recovery at 11:58 AM. During this time, other AWS services' APIs and workflows may also have experienced increased error rates and latencies. The issue is resolved and all AWS services are operating normally.