Confluent Cloud Outage History
Daily status observations, past incidents, and reported issue history for Confluent Cloud.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 92% | 25 | 2 |
| July 2026 | 41.9% | 31 | 18 |
| June 2026 | 0% | 30 | 30 |
| May 2026 | 0% | 5 | 5 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Elevated error rates and latencies in Azure Southeast Asia region
Started:
Confluent Cloud
monitoring
We are seeing recovery of Confluent services in the affected Azure Southeast Asia region and are continuing to monitor the situation.
investigating
We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in the Azure Southeast Asia region, beginning at approximately 03:13 UTC on 25 Aug 2026. Affected customers may experience degraded produce/consume availability or intermittent connectivity for clusters in this region.
This is associated with an ongoing Microsoft Azure service disruption in the Southeast Asia region. We are actively engaged with Microsoft Azure.
Elevated error rates and latency in GCP us-west1
Started:
Confluent Cloud
investigating
We are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour.
investigating
We are investigating an incident affecting services in the GCP us-west1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates. Our engineering teams are actively working to restore normal performance.
July 2026
Flink statements degraded in GCP us-central1 region
Started:
monitoring
Currently, we are monitoring the results after rolling out the fix.
identified
Engineers have identified and implemented a fix.
investigating
Flink statements are degraded in GCP us-central1 region.
The impact started at 18:37 UTC on July 17.
Currently, engineers are investigating the issue.
Kafka cluster performance degradation for clusters in AWS region eu-central-1
Started:
investigating
Confluent is aware of the ongoing AWS incident affecting eu-central-1. We have identified degraded performance impacting clusters in this region, and our engineers are actively working with AWS to mitigate the issue.
Confluent Cloud Metrics API is currently experiencing elevated latency and error rates.
Started:
monitoring
A fix has been implemented and we are monitoring the results
identified
The issue has been identified and a fix is being implemented.
June 2026
Kafka consumer and producer degradation in Azure spaincentral
Started:
identified
Kafka producers and consumers to some clusters in Azure spaincentral may not be able to produce and consume records from their topic partitions. An issue has been identified by Azure and is under investigation.
Confluent Cloud Metrics API is currently experiencing elevated error rates
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Increased error rates in Metrics API
Started:
monitoring
Confluent Cloud Metrics API experienced increased error rates from 2026-06-25 15:15 UTC to 2026-06-25 15:55 UTC. The incident has been mitigated and the systems have recovered. We are continuing to monitor.
investigating
We are currently investigating this issue.
Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
Started:
monitoring
The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability.
identified
The team has identified the root cause of the issues affecting standard and basic Kafka clusters in the AWS us-east-2 region. We are actively working on a mitigation strategy and will provide further updates as they become available.
Intermittent Produce/Consume Unavailability in Azure Dedicated clusters
Started:
monitoring
We have found the root cause and have mitigated the problem as of 2026-06-16 16:09 UTC. We will monitor for any residual issues before resolving this incident in 1 hour.
investigating
We are currently experiencing Intermittent Produce/Consume Unavailability in Azure Dedicated clusters. The problem started at 2026-06-16 13:20 UTC. We are currently investigating and will update as we know more.
Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2
Started:
monitoring
We have deployed a mitigation for the intermittent inter-region connectivity issues affecting AWS us-west-2, which began at approximately 04:00 UTC. Customers with clusters in or communicating with this region may have experienced delays or errors with Cluster Linking, Flink processing, and accessing logs in the Confluent Cloud UI. We are monitoring to confirm full restoration.
investigating
We continue to investigate intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking, Flink processing and logs for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.
investigating
We are investigating intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking and Apache Flink processing for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.
May 2026
Elevated error rates and latencies in Azure westus2 region
Started:
monitoring
Confluent services in the Azure West US2 region are now healthy. We are continuing to monitor for residual effects as Azure continues to address their service outage. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status
monitoring
We are monitoring the health of impacted Confluent services in the Azure West US2 region. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status
investigating
Confluent cloud services are experiencing outage in Azure West US2 region linked to Azure network connectivity degradation.
Team is continuing active investigation.
investigating
We are currently experiencing increased error rates and latencies in the Azure westus2 region. This began at approximately 5:10 AM UTC 29th May. Our team is actively investigating it.
Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
Started:
monitoring
AWS has reported the underlying infrastructure issue in us-east-1 (use1-az4) as resolved. However, some Confluent Cloud customers in the affected availability zone continue to experience connectivity issues.
Confluent is actively investigating and working to restore full connectivity for impacted customers.
monitoring
AWS has resolved the underlying infrastructure issue in us-east-1 (use1-az4). The majority of Confluent Cloud services have recovered and are operating normally.
We are continuing to monitor for any lingering effects and verifying full service restoration.
monitoring
We are monitoring the health of impacted brokers in the affected availability zone. More details about the thermal event on the AWS status page: https://health.aws.amazon.com/health/status
investigating
We are investigating data plane impact (produce/consume) resulting from elevated error rates and latencies from AWS us-east-1 resources in AZ4. EC2 instances hosted on this availability zone are impaired by loss of power during an ongoing thermal event.
Scheduled Confluent Cloud maintenance on May 6, 2026
Started:
monitoring
Confluent Cloud is undergoing a planned maintenance event between 4pm and 8pm PST on May 6, 2026. Customers might experience intermittent unavailability of certain pages in the customer portal, such as new customer sign-up, cluster creation, promo code claims, invoicing and public cost interfaces.
April 2026
Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements
Started:
monitoring
A fix has been implemented and we are monitoring for next hour.
identified
Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.
identified
The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.
investigating
We are currently investigating this issue.
Experiencing delays in Tableflow external catalog syncs in AWS
Started:
monitoring
We are experiencing delays Tableflow external catalog sync in AWS.
Our team has added a fix to resolve the situation and are monitoring the same.
Elevated error rates in AWS me-south-1 and me-central-1 regions
Started:
monitoring
Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 are strongly advised to relocate them to an alternative region.
monitoring
Provisioning new workloads in AWS me-central-1 and me-south-1 regions is disabled. Migration steps to other AWS regions have been communicated to impacted customers.
monitoring
AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers requiring immediate restoration in these two regions are encouraged to review regional failover options.
March 2026
Elevated error rates in AWS me-south-1 and me-central-1 regions
Started:
monitoring
AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers requiring immediate restoration in these two regions are encouraged to review regional failover options.
monitoring
Confluent Cloud services in AWS me-south-1 remain stable and operating normally following mitigation. We continue to monitor for any residual issues.
Confluent Cloud services in AWS me-central-1 continue to experience a complete outage due to the ongoing AWS regional infrastructure failure in that region.
monitoring
Confluent cloud services in AWS me-south-1 are mitigated. They are currently being monitored.
Confluent Cloud Services in AWS me-central-1 are still disrupted owing to regional outage at AWS.
investigating
Confluent Cloud services in AWS me-central-1 region are experiencing a major outage. They are linked to AWS's me-central-1 regional outage
Confluent Cloud services in AWS me-south-1 are being mitigated.
investigating
We are experiencing increased error rates in some of our Confluent Cloud services in AWS me-south-1 and me-central-1 regions. This began at approximately 05:00 AM UTC today and is linked to disruptions in AWS’s availability zones in these regions (mec1-az1, mec1-az3 and mes1-az2). Team is currently working on mitigating these and will provide updates as the situation evolves.