Daily provider-status observations and published incident history for Confluent Cloud.
Component incident
Confluent Cloud has an active component incident; no global outage is indicated. 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
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
Incident History
October 2026
Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
We are continuing to monitor for any further issues.
monitoring
The underlying GCP issue has been mitigated. Confluent Cloud Kafka clusters in the affected zone are fully operational and Connect and Flink workloads have recovered. We are monitoring to confirm stability and working to restore the few remaining impacted resources.
investigating
We are currently working to restore the impacted services. Most customers should be able to use Confluent Cloud services normally.
investigating
Some customer may observe issues with Confluent Cloud services in EU-West2 region. This is due to ongoing issues with GCP EU-West2
We are continuing to monitor for any further issues.
monitoring
We have mitigated the issue that was causing delays in Kafka cluster provisioning and we are now monitoring the health of new cluster provisioning. Existing clusters were not affected. We will post our next update by 07:30 UTC, or sooner if there is new information
identified
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Clusters provisioned during this window may take longer than usual to become available. Our next update will be posted by 6:30 UTC or as more information becomes available
identified
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Our next update will be posted by 5:30 UTC or as more information becomes available
identified
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Our next update will be posted by 5:30 UTC or as more information becomes available
identified
We have identified the cause of the delays in Kafka cluster provisioning in all regions and are working on mitigation. Existing clusters continue to operate normally. Our next update will be posted by 4:30 UTC or as more information becomes available.
investigating
We are still investigating the delays in Kafka cluster provisioning in all regions and are actively working on mitigation. Existing clusters continue to operate normally. Our next update will be posted by 3:30 UTC or as more information becomes available.
investigating
We are investigating an issue that is causing delays in Kafka cluster provisioning in all regions. Existing clusters are not affected and continue to operate normally.
We will provide another update within 60 minutes.
The observed elevated error rates seen in AWS us-east-1 have subsided and all services have recovered. No action is required from customers at this point and we are monitoring and investigating further to understand the root cause with the provider.
investigating
We are investigating an incident affecting services in the AWS us-east-1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates.
Experiencing high error rate in AZURE in West Europe region
A fix has been implemented and we are monitoring the results.
identified
Confluent continues to work closely with Azure, and we are seeing recovery across a number of affected clusters. Azure has not yet provided a specific ETA for full resolution. We will continue to provide updates as more information becomes available.
identified
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 03:00 UTC, or sooner, as updates are available.
identified
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 01:00 UTC, or sooner, as updates are available.
identified
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 00:00 UTC, or sooner, as updates are available.
identified
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 23:00 UTC, or sooner, as updates are available.
identified
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 22:00 UTC, or sooner, as updates are available.
identified
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 21:00 UTC, or sooner, as updates are available.
identified
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 20:00 UTC, or sooner, as updates are available.
identified
Azure has identified the issue and recovery actions are underway
investigating
Users in West Europe region of Azure could face elevated error rates and experience degraded performance.
We are currently investigating the issue and attempting to mitigate or provide a work-around.
Experiencing high error rate in AZURE in Germany West Central region
A fix has been implemented and we are monitoring the results.
investigating
Users in Germany West Central region of Azure could face elevated error rates.
We are currently investigating the issue and attempting to mitigate or provide a work-around.
Systems are continuing to recover and are being monitored
identified
Microsoft Azure has confirmed an outage impacting their Azure East US region, which is the root cause of the elevated error rates affecting Confluent services. Confluent will provide another update as soon as we receive further details.
investigating
We are currently investigating an issue related to elevated error rates in Azure East US
Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
All affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident.
identified
Flink in AWS us-west-2 is continues to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period.
All other services including Connect, ConfluentCloud UI are mitigated and operational
identified
The issue has been identified and a fix is being implemented.
Elevated error rates in Azure Germany West Central region
The Azure regional disruption has ended, and Confluent Cloud mitigation was achieved as of 18:00 UTC. Clusters in the Azure's Germany West Central region are now fully operational. We will monitor for residual impact before marking this incident resolved.
investigating
We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in Microsoft Azure's Germany West Central region, beginning at approximately 13:00 UTC on 22 Sep 2026. Affected customers may experience degraded availability or intermittent connectivity for clusters in the region.
This is associated with an ongoing Microsoft Azure service disruption in that region. We are actively engaged with Microsoft Azure.
Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
All affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident.
identified
Confluent is continuing to monitor recovered services and complete recovery for a small number of Flink customers in AWS us-west-2 that may still be experiencing degraded jobs. We are actively working to fully restore them and will post the next update by 00:30 UTC, or sooner if service is fully restored.
identified
All affected services have recovered with the exception of a small number of Flink customers in AWS us-west-2 that may still experience degraded jobs while we complete recovery. We are actively working to fully restore them and will post the next update by 00:00 UTC, or sooner if service is fully restored.
identified
Flink in AWS us-west-2 is still recovering as we continue to restore full service: while some jobs may start to recover, others may remain degraded and new job submissions may still fail. Previously affected services have recovered and are being monitored for stability. We will post the next update by 23:30 UTC or sooner if recovery completes sooner.
identified
Flink in AWS us-west-2 is still recovering as we continue to restore full service: running jobs may remain degraded and new job submissions may still fail. Previously affected services have recovered and are being monitored for stability. We will post the next update by 22:30 UTC or sooner if recovery completes sooner.
identified
Most affected services are recovering and we are continuing to monitor for stability. Flink in AWS us-west-2 is still recovering and running jobs may remain degraded with new submissions still failing. We will post the next update by 22:00 UTC or sooner if the situation changes.
identified
We have applied a mitigation and most affected services are beginning to recover. Flink in AWS us-west-2 will continue to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period. We will post the next update by 21:30 UTC, or sooner if service is restored.
investigating
We are continuing to work to resolve the incident and do not yet have a confirmed mitigation. Impact remains as previously described. We will post the next update by 20:30 UTC, or sooner if the situation changes.
investigating
We are continuing to validate several proposed mitigations to address the ongoing incident affecting the Confluent Cloud UI and other services in the AWS us-west-2 region. We do not yet have a confirmed fix in place. We will post the next update by 20:00 UTC, or sooner if service is restored.
investigating
We are continuing to investigate an incident affecting the Confluent Cloud UI and other services in the AWS us-west-2 region. Several potential mitigations remain under active testing and validation. We do not yet have a confirmed fix in place. We will post the next update by 19:30 UTC, or sooner if service is restored.
investigating
We are testing and validating several potential mitigations in parallel to restore the Confluent Cloud Console and affected services. We do not yet have a confirmed fix in place and are continuing to investigate. We will post the next update by 19:00 UTC, or sooner if service is restored.
investigating
We have refined the scope of customer impact and continue to work on a mitigation.
Impacted Services:
- Confluent Cloud Console (web UI), all regions: broad degradation. Customers may be unable to view or manage their resources in the Console.
- Schema Registry, AWS us-west-2: a subset of Schema Registry clusters are unavailable.
- Flink, AWS us-west-2: all running jobs are degraded, and new job submissions will fail.
- Cluster Linking, AWS us-west-2: links to Enterprise clusters are impacted.
- Topic operations, AWS us-west-2: unavailable for Freight and some Basic and Standard clusters.
- Tableflow, AWS us-west-2: All operations are unavailable (additionally, topics utilizing the us-west-2 Schema Registry may be impacted)
- Connect, AWS us-west-2: Some connectors dependent on unavailable Schema Registry clusters may be affected
- Notifications, all regions: delivery is delayed. Customers may not receive notifications and alerts until the backlog clears.
Confirmed not impacted:
- Regular produce and consume operations on Kafka clusters are not affected.
- Topic-related operations on Enterprise and Dedicated clusters are not affected.
We are actively applying a mitigation. We will post the next update by 18:30 UTC, or sooner if service is restored.
investigating
We are confirming a contributing factor and applying a mitigation intended to restore Confluent Cloud services. We will post an update by 17:45 UTC, or sooner if service is restored.
investigating
We have made progress in identifying the cause of the disruption in AWS us-west-2 and are working to confirm the safest path to mitigation. Some customers in this region may continue to experience errors or degraded performance. We will post the next update by 17:00 UTC, or sooner if mitigation is achieved.
investigating
Multiple Confluent Cloud services in the AWS us-west-2 region are experiencing elevated error rates and service disruption. Impacted customers may see failed or slow requests to Kafka clusters, Connect, and Flink in this region. The Confluent Cloud UI is also degraded and visibility to clusters outside of us-west-2 may be impacted as well. We are actively investigating and will post the next update by 16:30 UTC, or sooner if we have new information.
investigating
Starting today at 15:26 UTC, Confluent Cloud is experiencing an incident involving multiple service disruptions in the AWS us-west-2 region. We are investigating the issue and will provide further updates shortly.
Multiple Confluent Cloud services are in a degraded state - All regions
The mitigation has been deployed and the degraded services are recovering as of 00:20 UTC on September 16th, 2026. We'll continue to monitor for any residual issues before resolving this incident in 1 hour (01:20 UTC).
identified
The issue has been identified and a fix is being implemented.
investigating
Starting on Tuesday, September 15th 2026 at 21:25 UTC, multiple Confluent Cloud services began entering a degraded state. We have identified the cause of the degradation and are actively mitigating the issue. Updates will be posted here in the next 30 minutes or when the issue is fully mitigated, whichever happens first.
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
majorSource 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
majorSource 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
minorSource 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
minorSource 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
minorSource 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
minorSource 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
majorSource 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
minorSource 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
minorSource 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.
