Harness: IDP Workflows and Backend failures

What to do

Check whether you use Harness Internal Developer Portal (IDP), Internal Developer Portal (IDP). 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 1h 6m it lasted.
Anything that failed between 2026-06-17 16:44 UTC and 2026-06-17 17:50 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.

investigatingJun 17, 2026, 4:44 PM UTC
We are currently investigating this issue.
provider
identifiedJun 17, 2026, 4:45 PM UTC
The issue has been identified and a fix is being implemented.
provider
identifiedJun 17, 2026, 4:45 PM UTC
IDP Systems' communication was interrupted due to an update. Harness is rolling back changes. Impacted environments - prod0, prod1, prod2
provider
monitoringJun 17, 2026, 4:47 PM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedJun 17, 2026, 5:50 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Harness still down?

No, this incident was resolved 2026-06-17 17:50 UTC. For Harness's live state, see https://down.guide/harness.

How long did it last?

1h 6m, from 2026-06-17 16:44 UTC to 2026-06-17 17:50 UTC, by the times Harness posted.

What was affected?

Harness named Internal Developer Portal (IDP), Internal Developer Portal (IDP).

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.