Confluent Outage History

Confluent Cloud underwent scheduled maintenance on May 6, 2026 from 4pm to 8pm PST, causing intermittent unavailability of customer portal pages including new customer sign-up, cluster creation, promo code claims, invoicing and public cost interfaces. The maintenance was completed and all services were restored after approximately 5 hours.

Confluent Cloud customers using Flink on Azure with PrivateLink connectivity experienced issues submitting new Flink statements for 7 hours. The problem affected the ability to execute new Flink operations within the Confluent Cloud service. The issue was identified and resolved through a phased fix rollout across impacted regions.

Confluent Cloud experienced delays in Tableflow external catalog syncs in AWS, affecting data synchronization operations. The engineering team implemented a fix and monitored the system for stability. The incident was resolved after 16 minutes of impact.

The Confluent Cloud Metrics API experienced a complete outage from 03:23 UTC to 03:58 UTC on March 5, 2026, making metrics data unavailable to users. The service was restored after 35 minutes, followed by a monitoring period to ensure stability. The incident was fully resolved at 07:22 UTC with all systems returning to normal operation.

Confluent Cloud services in AWS me-south-1 and me-central-1 regions experienced elevated error rates and outages due to underlying AWS infrastructure failures in multiple availability zones. The me-south-1 region was restored within days, while me-central-1 experienced a complete outage that lasted significantly longer due to extended AWS regional recovery issues. The incident was fully resolved after approximately 17 days, with customers advised to consider regional failover options during the extended outage period.

Confluent Cloud services in the AWS me-central-1 region experienced elevated error rates for 4 hours starting at 12:51 PM UTC, caused by a disruption in AWS availability zone mec1-az2. The team identified the root cause as the AWS infrastructure issue and implemented mitigation steps to restore service health. All Confluent Cloud services in the region were fully restored and healthy by 21:15 PM UTC.

Confluent Cloud experienced a major outage where all new dedicated Kafka cluster provisioning and expansion operations failed in Azure regions westus3, southcentralus, and eastus2. The issue was caused by an underlying Azure infrastructure problem that prevented new cluster deployments and scaling operations. The incident was resolved after 6 hours once Azure identified and implemented a fix for the underlying infrastructure issue.

Confluent's network provisioning service in the Azure East US region experienced degradation for 8.4 hours, causing potential failures when provisioning new networks. The issue affected Confluent Cloud services in that specific region. The incident has been resolved after investigation and remediation efforts.

Confluent Cloud customers in the GCP us-south1 region experienced elevated error rates for 61.3 hours, with single zone clusters in Zone-a being specifically impacted. The issue was identified as originating from GCP's infrastructure, and GCP worked to apply mitigation measures. The incident was resolved after implementing a fix and monitoring the results.

Confluent Cloud experienced elevated Kafka REST API errors with error code 429 in AWS us-west-2, impacting Kafka eSKU clusters in the region. The issue caused rate limiting errors for users attempting to access the Kafka REST API. The incident was resolved after 3.9 hours once the fix was identified and deployed.