Cloudera Status Page

Sep 3, 2026 · resolved Sep 4

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.

May 11, 2026 · resolved May 11

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.

Mar 10, 2026 · resolved Mar 10

On March 10, 2026, around 19:56 UTC users may have started experiencing intermittent timeouts accessing the Cloudera Management Console across the US, EU, and AP regions.  This disruption was traced to an internal service certificate expiration where, despite a successful renewal initiation, a misalignment in the deployment sequence prevented the updated credentials from propagating to the active service mesh. The impact was strictly limited to administrative console and API access; all existing data workloads and running environments continued to operate without interruption.  Service consistency was restored by regenerating and manually applying the certificates across all affected clusters. To prevent recurrence, we have audited all regional clusters and are transitioning to an automated lifecycle for mesh-level certificates.  We sincerely apologize for any inconvenience this service disruption may have caused. We are addressing monitoring gaps to detect these issues before they impact you, our customers. We appreciate your patience as we worked to restore service functionality.

Sep 25, 2025 · resolved Sep 25

The intermittent performance and access issues with the Cloudera Management Console and FreeIPA were triggered by a scheduled service upgrade intended to improve platform stability. Our investigation determined that a change in a core component introduced a latent configuration issue. This specific condition was not exposed in our testing environments, preventing dependent services from applying dynamic configuration updates in production and leading to the outage. We've taken immediate action to prevent this issue from recurring: System Fix: The problematic component change was rolled back, and a permanent patch was deployed to restore proper dynamic configuration functionality. Process Overhaul: We've implemented a more rigorous upgrade process with mandatory, near-production scale validation steps that specifically test for these types of configuration failures. Enhanced Monitoring: We significantly improved our monitoring and alerting capabilities to detect these abnormal service behaviours much earlier, ensuring a faster response time. We are dedicated to providing a reliable platform and will continue to invest in our infrastructure and processes. Thank you again for your patience and understanding

Sep 24, 2025 · resolved Sep 25

The intermittent performance and access issues with the Cloudera Management Console and FreeIPA were triggered by a scheduled service upgrade intended to improve platform stability. Our investigation determined that a change in a core component introduced a latent configuration issue. This specific condition was not exposed in our testing environments, preventing dependent services from applying dynamic configuration updates in production and leading to the outage. We've taken immediate action to prevent this issue from recurring: System Fix: The problematic component change was rolled back, and a permanent patch was deployed to restore proper dynamic configuration functionality. Process Overhaul: We've implemented a more rigorous upgrade process with mandatory, near-production scale validation steps that specifically test for these types of configuration failures. Enhanced Monitoring: We significantly improved our monitoring and alerting capabilities to detect these abnormal service behaviours much earlier, ensuring a faster response time. We are dedicated to providing a reliable platform and will continue to invest in our infrastructure and processes. Thank you again for your patience and understanding

Is Cloudera down right now?

No — Cloudera is up. All systems operational as of Oct 12, 7:41 AM UTC.

What is Cloudera's current status?

Cloudera: All Systems Operational. Alert24 checks Cloudera's status page continuously and can notify you the moment it changes.

How do I get alerted when Cloudera goes down?

Alert24 monitors Cloudera and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.