- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on CloudBees. 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 51m it lasted.
Anything that failed between 2021-11-22 23:32 UTC and 2021-11-23 01:23 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 3
- investigating
The CloudBees CI update center (jenkins-updates.cloudbees.com) is timing out due to increased load. Engineers are working to resolve the issue.
provider
- identified
The root cause has been identified - a fix is being developed.
provider
- resolved
A fix for the underlying issue has been released and the system is now performing normally.
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-352bcfa0e7
Is CloudBees still down?
No, this incident was resolved 2021-11-23 01:23 UTC. For CloudBees's live state, see https://down.guide/jenkins.
How long did it last?
1h 51m, from 2021-11-22 23:32 UTC to 2021-11-23 01:23 UTC, by the times CloudBees posted.
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.