- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 27of 100
What to do
Check whether you use CloudBees in us. 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 9h 58m it lasted.
Anything that failed between 2020-09-08 15:22 UTC and 2020-09-09 01:20 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
- investigating
Existing SAML users can login, however re-linking your SAML user and new SAML user invites are currently not working.
provider
- resolved
We are closing this incident as the nature of the limitation has been identified. We will post an updated note when the system limitation is resolved (this is a high priority issue with multiple engineers working to resolve the issue). Until that time, please deactivate SAML restricted mode and create a new user on your account to maintain access. If you have any questions or concerns - please contact us via https://support.cloudbees.com
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-cf4da267f2
Is CloudBees still down?
No, this incident was resolved 2020-09-09 01:20 UTC. For CloudBees's live state, see https://down.guide/jenkins.
How long did it last?
9h 58m, from 2020-09-08 15:22 UTC to 2020-09-09 01:20 UTC, by the times CloudBees posted.
What was affected?
CloudBees named in us.
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.