- Level
- confirmed
- Worst impact
- Degraded
- Components
- CloudBees Unify, Workflow Execution
- Down Index
- 18of 100
What to do
Check whether you use CloudBees CloudBees Unify, Workflow Execution. 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 33m it lasted.
Anything that failed between 2025-10-20 10:19 UTC and 2025-10-20 10:52 UTC may need a replay.Subscribe to CloudBees's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=jenkins works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from CloudBees 2
- monitoring
Some components might experience slowness due to issue with upstream Cloud Provider. We are working on mitigations
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-6e02b0de45
Is CloudBees still down?
No, this incident was resolved 2025-10-20 10:52 UTC. For CloudBees's live state, see https://down.guide/jenkins.
How long did it last?
33m, from 2025-10-20 10:19 UTC to 2025-10-20 10:52 UTC, by the times CloudBees posted.
What was affected?
CloudBees named CloudBees Unify, Workflow Execution.
What caused it?
CloudBees hasn't published a root cause. If it does, it shows here.
Where does this come from?
CloudBees's official status page, https://www.cloudbeesstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.