Cloudera incident
Cloudera Management Console not accessible in US Control Plane
Cloudera experienced a minor incident on September 3, 2026 affecting Cloudera Management Console, lasting 3h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 03, 2026, 11:18 PM UTC
We are currently investigating a potential issue accessing the Cloudera Management Console. An update will be provided within 90 minutes. Customer Experience: Customer may observe Error message: "no healthy upstream" while accessing Cloudera Management Console.
- investigating Sep 03, 2026, 11:18 PM UTC
We are continuing to investigate this issue.
- investigating Sep 04, 2026, 12:55 AM UTC
Current Status: Our teams are actively investigating the root cause of the issue. We expect to provide another update within 90 minutes.
- resolved Sep 04, 2026, 02:47 AM UTC
Current Status: Our teams have successfully implemented a solution to resolve the issue. Our teams are currently monitoring the solution and will provide another update once confirmed. Customer Experience: Customer may have observed an Error message: "no healthy upstream" while accessing Cloudera Management Console. If you are still experiencing issues or have any questions, please raise a support case with us. A Root Cause Analysis (RCA) will be published within seven business days.
- postmortem Sep 17, 2026, 06:25 PM UTC
Between 22:22 UTC on September 3, 2026, and 02:20 UTC on September 4, 2026, customers attempting to access the Cloudera Management Console in the US Control Plane experienced connectivity errors and service degradation. Root Cause: The incident was caused by an upstream Cloud Service Provider experiencing increased API error rates in the region. This disruption affected our internal security token validation layer, preventing dependent platform management services from authenticating. Existing data processing workloads running within customer environments continued to run without interruption throughout the event. Resolution: Our engineering teams performed a rolling restart of the security token infrastructure to clear stale session states and restore authentication. Full access to the Cloudera Management Console was restored, and all control plane services were confirmed to be operating normally. We have enhanced our automated recovery mechanisms and threshold alerting to prevent similar upstream dependencies from causing extended recovery windows in the future. We sincerely apologise for any inconvenience this service disruption may have caused. We appreciate your patience as we worked to restore service functionality.