Delay in Kafka cluster provisioning
Affected: Confluent Cloud
Confluent Outage History
Confluent is up right nowConfluent had 57 outages in the last 2 years totaling 142h 48m of downtime — averaging 2.3 incidents per month.
There were 57 Confluent outages since October 17, 2025 totaling 142h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.
Confluent Cloud Console (UI) degraded functionality
Affected: Confluent Cloud
Timeline · 2 updates
- monitoring Oct 15, 2026, 04:01 PM UTC
Between 14:23 and 15:35 UTC on Oct 15, 2026, some users of the Confluent Cloud Console experienced 502 errors and degraded page functionality. No other services were affected. The issue has been mitigated and no further problems have been observed. Confluent is investigating root cause and monitoring. No customer action is required.
- resolved Oct 15, 2026, 06:46 PM UTC
This incident has been resolved.
Possible outage in AWS us-east-1
Affected: Confluent Cloud
Timeline · 3 updates
- investigating Oct 09, 2026, 11:27 PM UTC
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.
- monitoring Oct 09, 2026, 11:43 PM UTC
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.
- resolved Oct 10, 2026, 12:23 AM UTC
This incident has been resolved. All affected services have fully recovered.
Experiencing high error rate in AZURE in West Europe region
Affected: Confluent Cloud
Timeline · 12 updates
Experiencing high error rate in AZURE in Germany West Central region
Affected: Confluent Cloud
Timeline · 3 updates
- investigating Oct 08, 2026, 11:00 AM UTC
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.
- monitoring Oct 08, 2026, 11:38 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 08, 2026, 11:56 AM UTC
This incident has been resolved.
Missing Metrics on Confluent Cloud
Timeline · 1 update
- resolved Sep 27, 2026, 05:17 PM UTC
Confluent Cloud Metrics were delayed from 00:33 to 02:15 UTC on Sep 27. Queries for recent metrics during this time duration may return incomplete or no data. This incident has been resolved as of 02:15 UTC.
Elevated error rates in Azure East US
Affected: Confluent Cloud
Timeline · 5 updates
- investigating Sep 26, 2026, 06:40 AM UTC
We are currently investigating an issue related to elevated error rates in Azure East US
- identified Sep 26, 2026, 08:00 AM UTC
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.
- identified Sep 26, 2026, 01:23 PM UTC
Systems are continuing to recover and are being monitored
- identified Sep 26, 2026, 07:43 PM UTC
We are continuing to work on a fix for this issue.
- resolved Sep 26, 2026, 07:43 PM UTC
This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.
Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
Affected: Confluent Cloud
Timeline · 4 updates
- identified Sep 23, 2026, 11:47 AM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 23, 2026, 02:18 PM UTC
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
- monitoring Sep 23, 2026, 03:57 PM UTC
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.
- resolved Sep 23, 2026, 11:17 PM UTC
This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.
Elevated error rates in Azure Germany West Central region
Affected: Confluent Cloud
Timeline · 3 updates
- investigating Sep 22, 2026, 03:09 PM UTC
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.
- monitoring Sep 22, 2026, 07:35 PM UTC
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.
- resolved Sep 22, 2026, 07:58 PM UTC
This incident has been resolved. Clusters in the Azure's Germany West Central region are now fully operational.
Confluent Cloud Metrics API experienced elevated latency and error rates
Timeline · 1 update
- resolved Sep 17, 2026, 05:49 PM UTC
Confluent Cloud Metrics API experienced elevated latency and error rates between 9:55 AM PDT to 10:10 AM PDT.
Multiple Confluent Cloud services are in a degraded state - All regions
Affected: Confluent Cloud
Timeline · 4 updates
- investigating Sep 15, 2026, 11:59 PM UTC
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.
- identified Sep 16, 2026, 12:00 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 16, 2026, 12:22 AM UTC
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).
- resolved Sep 16, 2026, 01:21 AM UTC
This incident has been resolved.
Connectivity degradation - AWS us-east-1
Affected: Confluent Cloud
Timeline · 5 updates
- investigating Sep 08, 2026, 08:01 PM UTC
We are investigating a service disruption affecting client connectivity in AWS us-east-1. Customers may see produce/consume failures
- investigating Sep 08, 2026, 08:13 PM UTC
We are continuing to investigate this issue.
- identified Sep 08, 2026, 08:20 PM UTC
A possible root cause has been identified and the Confluent Cloud team is implementing a fix
- monitoring Sep 08, 2026, 08:30 PM UTC
A fix has been implemented and the team is monitoring recovery.
- resolved Sep 09, 2026, 01:01 PM UTC
The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.
Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
Affected: Confluent Cloud
Timeline · 10 updates
Investigating Elevated Errors in GCP us-central1
Affected: Confluent Cloud
Timeline · 2 updates
- investigating Sep 01, 2026, 04:27 PM UTC
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 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 available.
- resolved Sep 01, 2026, 05:14 PM UTC
The GCP issue affecting the us-central1 region has been mitigated and all Confluent Cloud services in the region have returned to normal operation. Provisioning capability, error rates and latency have recovered to expected levels. Customers should no longer experience impact. If you continue to see any issues, please contact Confluent Support.
Elevated error rates and latencies in Azure Southeast Asia region
Affected: Confluent Cloud
Timeline · 3 updates
- investigating Aug 25, 2026, 04:17 AM UTC
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.
- monitoring Aug 25, 2026, 05:28 AM UTC
We are seeing recovery of Confluent services in the affected Azure Southeast Asia region and are continuing to monitor the situation.
- resolved Aug 25, 2026, 07:29 AM UTC
Confluent services in the Azure Southeast Asia region are now healthy and operating normally.
Confluent Cloud logging degradation - Connect and Flink
Timeline · 1 update
- resolved Aug 24, 2026, 03:49 PM UTC
Between 21:15 – 22:30 UTC and 00:05 – 01:15 UTC on Aug 23–24, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue has been mitigated.
Elevated error rates and latency in GCP us-west1
Affected: Confluent Cloud
Timeline · 3 updates
- investigating Aug 20, 2026, 05:10 PM UTC
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.
- investigating Aug 20, 2026, 07:18 PM UTC
We are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour.
- resolved Aug 20, 2026, 08:18 PM UTC
The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.
Flink statements degraded in GCP us-central1 region
Affected: Confluent Cloud
Timeline · 4 updates
- investigating Jul 17, 2026, 10:01 PM UTC
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.
- identified Jul 17, 2026, 10:54 PM UTC
Engineers have identified and implemented a fix.
- monitoring Jul 17, 2026, 10:55 PM UTC
Currently, we are monitoring the results after rolling out the fix.
- resolved Jul 18, 2026, 12:59 AM UTC
All the statements should be running now.
Kafka cluster performance degradation for clusters in AWS region eu-central-1
Affected: Confluent Cloud
Timeline · 2 updates
- investigating Jul 15, 2026, 11:33 PM UTC
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.
- resolved Jul 16, 2026, 01:14 PM UTC
The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.
Confluent Cloud Metrics API is currently experiencing elevated latency and error rates.
Affected: Confluent Cloud
Timeline · 3 updates
- identified Jul 13, 2026, 02:25 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 13, 2026, 02:36 PM UTC
A fix has been implemented and we are monitoring the results
- resolved Jul 13, 2026, 04:04 PM UTC
This incident has been resolved.
Kafka consumer and producer degradation in Azure spaincentral
Affected: Confluent Cloud
Timeline · 2 updates
- identified Jun 29, 2026, 05:44 PM UTC
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.
- resolved Jun 29, 2026, 08:36 PM UTC
This incident has been resolved.
Confluent Cloud Metrics API is currently experiencing elevated error rates
Affected: Confluent Cloud
Timeline · 4 updates
- investigating Jun 29, 2026, 11:58 AM UTC
We are currently investigating this issue.
- identified Jun 29, 2026, 12:04 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 29, 2026, 12:05 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 29, 2026, 12:50 PM UTC
This incident has been resolved.
Increased error rates in Metrics API
Affected: Confluent Cloud
Timeline · 3 updates
- investigating Jun 25, 2026, 03:59 PM UTC
We are currently investigating this issue.
- monitoring Jun 25, 2026, 04:12 PM UTC
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.
- resolved Jun 25, 2026, 05:53 PM UTC
This incident has been resolved.
Confluent Cloud Metrics API unavailable
Timeline · 1 update
- resolved Jun 23, 2026, 07:30 AM UTC
On June 23rd, between 7:00 to 7:16 UTC the Confluent Cloud Metrics API was unavailable. Confluent has identified the issue and restored functionality.
Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
Affected: Confluent Cloud
Timeline · 4 updates
- identified Jun 21, 2026, 07:14 AM UTC
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.
- monitoring Jun 21, 2026, 08:31 AM UTC
The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability.
- monitoring Jun 21, 2026, 09:19 AM UTC
We are continuing to monitor for any further issues.
- resolved Jun 21, 2026, 09:19 AM UTC
This incident has been resolved.