- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 100
Summary
Harness says apidocs.harness.io was not responding to HTTPS requests, starting around 00:59 UTC on 2026-11-06. The provider identified the issue and implemented a fix, and it reports the incident resolved at 07:13 UTC the same day.
Written by anthropic/claude-haiku-5.5 from Harness's own updates.
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 6h 14m it lasted.
Anything that failed between 2026-11-06 00:59 UTC and 2026-11-06 07:13 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 this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
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-a466f00bf4
Is Harness still down?
No, this incident was resolved 2026-11-06 07:13 UTC. For Harness's live state, see https://down.guide/harness.
How long did it last?
6h 14m, from 2026-11-06 00:59 UTC to 2026-11-06 07:13 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.