- Level
- confirmed
- Worst impact
- Degraded
- Components
- Advisor Server
- Down Index
- 18of 100
What to do
Check whether you use CloudBees Advisor Server. 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 1h 2m it lasted.
Anything that failed between 2020-01-17 18:39 UTC and 2020-01-17 19:40 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
- identified
The issue has been identified and a fix is being implemented
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-34ccbb101d
Is CloudBees still down?
No, this incident was resolved 2020-01-17 19:40 UTC. For CloudBees's live state, see https://down.guide/providers/jenkins.
How long did it last?
1h 2m, from 2020-01-17 18:39 UTC to 2020-01-17 19:40 UTC, by the times CloudBees posted.
What was affected?
CloudBees named Advisor Server.
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.