- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data processing
- Down Index
- 17of 100
What to do
Check whether you use Harness Data processing. 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 44m it lasted.
Anything that failed between 2026-04-13 16:47 UTC and 2026-04-13 17:31 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 2
- monitoring
Feature flag metrics impact calculations were not updating. This issue does not impact experiment calculation. Fix is being rolled out. There is no data loss.
provider
- resolved
After monitoring post fixing the issue, all systems are back to normal and processing metrics impact calculations regularly. We will provide an RCA soon.
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-f1c3576e76
Is Harness still down?
No, this incident was resolved 2026-04-13 17:31 UTC. For Harness's live state, see https://down.guide/harness.
How long did it last?
44m, from 2026-04-13 16:47 UTC to 2026-04-13 17:31 UTC, by the times Harness posted.
What was affected?
Harness named Data processing.
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.