Autostopping service degraded in AWS (Middle East South 1)

Update timeline

1. identified Apr 01, 2026, 06:16 AM UTC

   The issue has been identified and a fix is being implemented.

2. identified Apr 01, 2026, 06:44 AM UTC

   Status update : CCM AutoStopping functionality for the AWS cloud provider is currently impacted due to increased latency from AWS in the me-south-1 region. This is affecting multiple operations, including warm-up, cool-down, schedule execution, and traffic detection. In addition, CCM Asset Governance functionality is also impacted for resources in the me-south-1 region. We are actively working on isolating/excluding the affected region to restore functionality for the remaining customers. Resources within the me-south-1 region may continue to experience issues until the region fully recovers.

3. monitoring Apr 01, 2026, 08:20 AM UTC

   Update: AutoStopping functionality for AWS has been restored for all regions except me-south-1. The issue was caused by elevated latency from AWS in the affected region, impacting operations such as warm-up, cool-down, schedule execution, and traffic detection. We have now isolated this region to prevent impact on other customers. Resources in me-south-1 will continue to experience the issue until the region fully recovers. We are actively monitoring the situation and will provide further updates as available.

4. resolved Apr 02, 2026, 08:40 AM UTC

   This incident has been resolved.

5. postmortem Apr 14, 2026, 03:30 AM UTC

   The issue was caused by elevated latency from AWS in the affected region, impacting operations such as warm-up, cool-down, schedule execution, and traffic detection. We have now isolated this region to prevent impact on other customers. Resources in me-south-1 will continue to experience the issue until the region fully recovers. We are actively monitoring the situation and will provide further updates as available.