- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on CloudBees. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 20h 37m it lasted.
Anything that failed between 2019-11-05 15:46 UTC and 2019-11-06 12: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 4
- investigating
Engineers are investigating problems with pushing configurations to SDKs. We've disabled push configuration for now.
provider
- identified
Engineers are working on a solution but it will take some time to resolve and test. Push configuration will remain disabled for now. Please reach out to support with any concerns.
provider
- monitoring
Engineering has implemented a fix and are monitoring while we progressively roll out push configurations to users.
provider
- resolved
Push configuration service has been restored and enabled for all customers
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-bc62cbbb67
Is CloudBees still down?
No, this incident was resolved 2019-11-06 12:23 UTC. For CloudBees's live state, see https://down.guide/providers/jenkins.
How long did it last?
20h 37m, from 2019-11-05 15:46 UTC to 2019-11-06 12: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.