- Level
- confirmed
- Worst impact
- Degraded
- Components
- Cloud Cost Management (CCM), Cloud Cost Management (CCM), Cloud Cost Management (CCM)
- Regions
- me, me-south-1
What to do
Check whether you use Harness Cloud Cost Management (CCM), Cloud Cost Management (CCM), Cloud Cost Management (CCM) in me, me-south-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 1h it lasted.
Anything that failed between 2026-04-01 06:44 UTC and 2026-04-02 08:40 UTC may need a replay.Subscribe to Harness's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=harness works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Harness 4
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
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.
provider
- monitoring
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.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ffbdfe5b35
Is Harness still down?
No, this incident was resolved 2026-04-02 08:40 UTC. For Harness's live state, see https://down.guide/harness.
How long did it last?
1d 1h, from 2026-04-01 06:44 UTC to 2026-04-02 08:40 UTC, by the times Harness posted.
What was affected?
Harness named Cloud Cost Management (CCM), Cloud Cost Management (CCM), Cloud Cost Management (CCM) in me, me-south-1.
What caused it?
Harness hasn't published a root cause. If it does, it shows here.
Where does this come from?
Harness's official status page, https://status.harness.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.