Cloudera incident

Intermittent Performance Issues - US Control Plane

Notice Resolved View vendor source →

Cloudera experienced a notice incident on May 11, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 11, 2026, 06:12 PM UTC
Resolved
May 11, 2026, 10:00 AM UTC
Duration
Detected by Pingoru
May 11, 2026, 06:12 PM UTC

Update timeline

  1. resolved May 11, 2026, 06:12 PM UTC

    Our teams have identified a potential performance issue on our US control plane. Our teams have successfully deployed a fix to address the issue. 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.

  2. postmortem May 22, 2026, 07:29 PM UTC

    On March 10, 2026, between 15:23 UTC to 17:09 UTC, users may have experienced intermittent connectivity issues accessing the workloads in the Cloudera Management Console of the US region. This disruption was traced to the termination of jumpgate-proxy pods, which entered an OOMKilled status after memory utilization exceeded configured limits. This, in turn, impacted connectivity between the control plane and the workloads within the Cloudera Management Console. Service consistency was restored by increasing the memory limits and replica counts for the jumpgate-proxy deployment. To prevent recurrence, we will implement alerting mechanisms for jumpgate pod memory utilization and pod states \(such as CrashLoopBackoff or OOMKilled events\). This will enable us to proactively detect and mitigate memory pressure before it impacts service availability. We will implement autoscaling to autoheal and respond to increased load. We sincerely apologise for any inconvenience this service disruption may have caused. We appreciate your patience as we worked to restore service functionality.