Confluent Cloud Outage History
Uptime record, past incidents, and downtime history for Confluent Cloud.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 0% | 25 | 25 |
| April 2026 | 0% | 30 | 30 |
| March 2026 | 16.1% | 31 | 26 |
| February 2026 | 20% | 5 | 4 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
Started: May 8, 1:14 AM
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.
May 12, 6:51 PM
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.
May 9, 1:19 PM
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
May 8, 1:55 AM
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.
May 8, 1:14 AM
Scheduled Confluent Cloud maintenance on May 6, 2026
Started: May 6, 10:12 PM
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.
May 6, 10:12 PM
April 2026
Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements
Started: Apr 24, 5:18 PM
monitoring
A fix has been implemented and we are monitoring for next hour.
Apr 24, 11:06 PM
identified
Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.
Apr 24, 10:27 PM
identified
The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.
Apr 24, 8:14 PM
investigating
We are currently investigating this issue.
Apr 24, 5:18 PM
Experiencing delays in Tableflow external catalog syncs in AWS
Started: Apr 21, 9:34 AM
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.
Apr 21, 9:34 AM
Elevated error rates in AWS me-south-1 and me-central-1 regions
Started: Apr 1, 7:52 PM
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.
Apr 2, 3:40 PM
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.
Apr 1, 7:52 PM
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.
Mar 20, 1:58 PM
March 2026
Elevated error rates in AWS me-south-1 and me-central-1 regions
Started: Mar 2, 7:19 AM
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.
Mar 3, 5:34 AM
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.
Mar 2, 3:37 PM
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.
Mar 2, 10:35 AM
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.
Mar 2, 8:32 AM
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.
Mar 2, 7:19 AM