Looking for an update now? Check the current status, or follow Confluent Cloud for future changes.
77.2%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
73.3%
30
8
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.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We have applied a mitigation for the issue affecting Schema Registry, Authentication, ksqlDB, Flink, and Kafka operations in AWS us-east-1. Services are recovering and we are monitoring closely.
identified
Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.
identified
Confluent is continuing to work on remediating the service disruption in AWS us-east-1.
identified
We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.
identified
We continue to work on remediating the service disruption in AWS us-east-1.
Confirmed impact:
- Authentication — a subset of requests may fail
- Schema Registry — authorization errors on a subset of requests
- ksqlDB — a subset of queries/requests may be affected
- Flink — statement management operations (create/update/delete) are degraded, and some running Flink jobs may fail or restart
- Kafka operations (create, delete etc)
Not impacted: Kafka cluster data-plane operations are ...
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating a service disruption affecting multiple services in AWS us-east-1 region. Affected customers may experience authentication failures, errors accessing Schema Registry, or issues with KSQL and Flink workloads. We are actively investigating the root cause and working toward mitigation.
We are investigating elevated error rates and degraded performance for some services running in the Google Cloud (GCP) us-central1 region. This is related to an ongoing Google Cloud networking issue affecting a portion of the region.
Customers in this region may experience issues provisioning or deprovisioning clusters, intermittent connectivity issues, elevated latency, or errors. We are actively assessing the full scope of impact and will provide an update as more information becomes avail...
Legacy Incident Archive
16 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
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 latency on produce and consume operations on AWS us-east-1 AZ4
majorSource not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
majorSource not attested
Last archived state: resolved
View archived record details
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.
March 2026
Elevated error rates in AWS me-south-1 and me-central-1 regions
majorSource not attested
Last archived state: resolved
View archived record details
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.
