AWS MINOR
Elevated API error rates and connectivity issues in the AP-SOUTH-2 Region
May 29, 2025 · 05:29 PM UTC – 06:13 PM UTC · Duration: 44min
Affected Services
AWS Private Certificate AuthorityAmazon API GatewayAWS AppSyncAmazon AthenaAWS BackupAWS Certificate ManagerAWS CloudFormationAWS Cloud WANAmazon CloudWatchAmazon CognitoAWS DataSyncAmazon DocumentDBAWS Elastic Disaster RecoveryAmazon DynamoDBAmazon Elastic Compute CloudAWS Systems ManagerAmazon Elastic Container ServiceAmazon Elastic Kubernetes ServiceAmazon Elastic Load BalancingAmazon Elastic MapReduceAmazon EventBridgeAWS FargateAWS GlueAWS Identity and Access Management Roles AnywhereAmazon Managed Streaming for Apache KafkaAmazon Kinesis Data StreamsAmazon Managed Service for Apache FlinkAWS Key Management ServiceAWS LambdaAWS NAT GatewayAWS Private CA Connector for SCEPAWS Private CA Connector for Active DirectoryAWS VPCE PrivateLinkAWS Resource Access ManagerAmazon Relational Database ServiceAmazon RedshiftAWS Resource ExplorerAmazon Route 53 ResolverAmazon CloudWatch RUMAmazon Simple Storage ServiceAmazon SageMakerAmazon EventBridge SchedulerAmazon Simple Notification ServiceAmazon Simple Queue ServiceAWS Step FunctionsAWS Security Token ServiceAmazon Simple Workflow ServiceTraffic MirroringAWS Transit Gateway
Timeline
05:29 PM
We are investigating elevated API Error rates and connectivity issues in the AP-SOUTH-2 Region.
05:45 PM
We are experiencing elevated API Error rates and connectivity issues in the AP-SOUTH-2 Region. We have identified the cause and are working to mitigate this issue now. We will provide you with another update by 11:15 AM PDT.
06:00 PM
We are seeing recovery for the elevated API Error rates and connectivity issues in the AP-SOUTH-2 Region, and monitoring for full recovery.
06:13 PM
At 10:08 AM PDT, we began experiencing elevated API error rates and connectivity issues in the AP-SOUTH-2 Region. We were automatically notified of the issue at 10:13 AM when we began to investigate the root cause so we could identify a mitigation strategy. We were able to isolate the root cause at 10:22 AM and began implementing a mitigation. We began to see early signs of recovery at 10:55 AM and full recovery by 11:06 AM. The issue has been resolved and the services are operating normally.