- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Harness. 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 0m it lasted.
Anything that failed between 2026-05-08 17:08 UTC and 2026-04-22 21:35 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 1
- resolved
On April 22, 2026, couple of customers experienced feature flags returning default treatments due to invalid empty segment membership responses being cached and served to SDKs. The issue was isolated to couple of customers under specific high-concurrency conditions involving Large Segments.
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-54003fd49a
Is Harness still down?
No, this incident was resolved 2026-04-22 21:35 UTC. For Harness's live state, see https://down.guide/harness.
How long did it last?
0m, from 2026-05-08 17:08 UTC to 2026-04-22 21:35 UTC, by the times Harness posted.
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.