- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 28m it lasted.
Anything that failed between 2023-06-07 14:16 UTC and 2023-06-07 14:44 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
We are aware that there are issues logging in to the CloudBees Feature Management web interface. We are investigating.
provider
- investigating
Logins to the web interface are working again. We are continuing to investigate.
provider
- resolved
A configuration setting caused specific traffic to be rejected by our firewall, causing issues with authentication. The problem has been corrected and the incident is now 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-41923b3840
Is CloudBees still down?
No, this incident was resolved 2023-06-07 14:44 UTC. For CloudBees's live state, see https://down.guide/jenkins.
How long did it last?
28m, from 2023-06-07 14:16 UTC to 2023-06-07 14:44 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.