CloudBees status history
Current state: operational — “All Systems Operational” per https://www.cloudbeesstatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do CloudBees incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: Cloudbees Unify is not accessible — 98 min (2026-06-23 07:17 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-06-23 07:17 UTC | Cloudbees Unify is not accessible | resolved | none | 1 h 38 min |
| 2026-05-08 10:57 UTC | Unify AI assistant unavailable. | resolved | none | 6 min |
| 2025-10-20 10:19 UTC | Cloud Provider issues affecting our services | resolved | none | 33 min |
| 2025-10-05 08:30 UTC | Customer(s) could not login to the https://app.rollout.io/cloudbees/login | resolved | minor | 0 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch CloudBees with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"cloudbees"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
