- Level
- confirmed
- Worst impact
- Degraded
- Components
- Continuous Delivery - Next Generation (CDNG)
- Down Index
- 19of 100
What to do
Check whether you use Harness Continuous Delivery - Next Generation (CDNG). 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 2h 15m it lasted.
Anything that failed between 2026-07-07 10:22 UTC and 2026-07-07 12:36 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 3
- investigating
We are currently investigating an issue in Prod3 cluster where pipeline components are loading slower than expected.
provider
- monitoring
A fix has been implemented in one of our microservice responsible for dealing with pipeline templates which has resolved the issue. We are continuing to monitor the issue.
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-501f6e8bd9
Is Harness still down?
No, this incident was resolved 2026-07-07 12:36 UTC. For Harness's live state, see https://down.guide/harness.
How long did it last?
2h 15m, from 2026-07-07 10:22 UTC to 2026-07-07 12:36 UTC, by the times Harness posted.
What was affected?
Harness named Continuous Delivery - Next Generation (CDNG).
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.