New Multi-region uptime checks and custom-domain status pages

Confluent Cloud Outage History

Daily provider-status observations and published incident history for Confluent Cloud.

Operational

Confluent Cloud is operational. Verified . Official provider source.

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

Jul 23Oct 20

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 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Connectivity degradation - AWS us-east-1
major Observed active window 17h 3m

View incident details and source

Started:

Confluent Cloud
monitoring
A fix has been implemented and the team is monitoring recovery.
identified
A possible root cause has been identified and the Confluent Cloud team is implementing a fix
investigating
We are continuing to investigate this issue.
investigating
We are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.
Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
minor Observed active window 29h 42m

View incident details and source

Started:

Confluent Cloud
monitoring
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.
Investigating Elevated Errors in GCP us-central1
minor Observed active window 47m

View incident details and source

Started:

Confluent Cloud
investigating
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.

August 2026
Elevated error rates and latencies in Azure Southeast Asia region
major Source not attested
Last archived state: resolved
View archived record details
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
major Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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.
Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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
major Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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.