Cloudera status history
Current state: operational — “All Systems Operational” per https://status.cloudera.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Cloudera incidents last?
From 6 incidents with a vendor-posted start and resolve time. Longest on record: Intermittent Performance and Access Issues with the Cloudera Management Console — 21.3 h (2025-09-24 19:42 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 (6)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-03 23:18 UTC | Cloudera Management Console not accessible in US Control Plane | resolved | minor | 3 h 29 min |
| 2026-05-11 10:00 UTC | Intermittent Performance Issues - US Control Plane | postmortem | none | 0 min |
| 2026-03-10 20:00 UTC | Intermittent Management Console Access Issues Across US, EU, and AP Regions | postmortem | minor | 0 min |
| 2025-09-25 10:23 UTC | FreeIPA connectivity issues | postmortem | minor | 6 h 38 min |
| 2025-09-24 19:42 UTC | Intermittent Performance and Access Issues with the Cloudera Management Console | postmortem | minor | 21 h 19 min |
| 2025-08-13 14:33 UTC | DataHubs, DataLakes and FreeIPA are unreachable in US region | postmortem | minor | 44 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 Cloudera with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"cloudera"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}