- Level
- confirmed
- Worst impact
- Major outage
- Components
- Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery - Next Generation (CDNG), Cloud Cost Management (CCM), Continuous Error Tracking (CET), Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Custom Dashboards, Feature Flags (FF), Security Testing Orchestration (STO), Service Reliability Management (SRM), Chaos Engineering, Internal Developer Portal (IDP), Infrastructure as Code Management (IaCM), Software Supply Chain Assurance (SSCA), Software Engineering Insights (SEI) / AI DLC Insights, Code Repository, Artifact Registry, Platform, FME
- Down Index
- 45of 100
What to do
Check whether you use Harness Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery - Next Generation (CDNG), Cloud Cost Management (CCM), Continuous Error Tracking (CET) and 17 more. 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 4h 54m it lasted.
Anything that failed between 2026-05-07 08:00 UTC and 2026-05-07 12:54 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 8
- investigating
We are currently investigating this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
We have identified the root cause as elevated queue depth and throughput saturation on the MongoDB layer, leading to processing latency. A fix is being implemented to optimize handling and restore database stability
provider
- identified
Executions are running fine now. However, there is still some slowness in the execution graph generation so we might see some delay in the execution updates to show up in UI. But executions would work without any delay/slowness.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
A fix has been implemented and we are monitoring the system.
provider
- monitoring
We are continuing to monitor for any further issues.
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-38c71e8f4a
Is Harness still down?
No, this incident was resolved 2026-05-07 12:54 UTC. For Harness's live state, see https://down.guide/harness.
How long did it last?
4h 54m, from 2026-05-07 08:00 UTC to 2026-05-07 12:54 UTC, by the times Harness posted.
What was affected?
Harness named Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery - Next Generation (CDNG), Cloud Cost Management (CCM), Continuous Error Tracking (CET) and 17 more.
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.