Confluent Cloud

All Systems Operational

About This Site

Welcome to Confluent Cloud's status page. Here you will find high level availability information for the Confluent Cloud managed service. Visit https://confluent.cloud to manage your Confluent Cloud clusters.

Confluent Cloud ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Nov 9, 2025

No incidents reported today.

Nov 8, 2025

No incidents reported.

Nov 7, 2025

No incidents reported.

Nov 6, 2025
Resolved - All affected clusters are now fully operational.
Nov 6, 21:39 UTC
Monitoring - Issues observed with Azure Europe West are now resolved. Most impacted services have recovered and are operational. We are working on resolving issues impacting performance for few customers.
Nov 6, 14:03 UTC
Update - We are monitoring Azure updates and recovery closely. We are noticing partial recovery in a subset of affected resources and will provide an update as more information becomes available.
Nov 6, 01:48 UTC
Update - Azure has provided an update on it's Status Page (https://azure.status.microsoft/en-us/status) stating that recovery efforts are in progress. We will provide an update within 60 minutes.
Nov 5, 22:29 UTC
Update - Azure posted outage details on its status page: https://azure.status.microsoft/en-us/status. No material changes since last update. We continue monitoring the situation from our side and will provide the next update within 60 minutes or when the status changes.
Nov 5, 21:13 UTC
Identified - The issue was localized to a single Availability Zone in Azure West Europe region. Only Single Zone Kafka Clusters are affected at this time. Multi-Zone clusters experienced intermittent availability and elevated latency for produce and fetch requests but auto-recovered within minutes. We are continuing to work with Microsoft Azure for resolution of affected single zone clusters. We will post next update by 1:00 PST.
Nov 5, 19:51 UTC
Update - We are continuing to investigate this issue.
Nov 5, 19:22 UTC
Update - We are beginning to see some recovery of the affected Kafka clusters.
Nov 5, 18:47 UTC
Investigating - We are currently experiencing an issue that appears to be related to an ongoing incident with Microsoft Azure. We are actively working with the Azure team to confirm the impact and will provide updates as soon as more information becomes available.
Nov 5, 18:19 UTC
Nov 5, 2025
Nov 4, 2025

No incidents reported.

Nov 3, 2025

No incidents reported.

Nov 2, 2025

No incidents reported.

Nov 1, 2025

No incidents reported.

Oct 31, 2025

No incidents reported.

Oct 30, 2025
Resolved - Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.
Oct 30, 00:42 UTC
Update - Flink statements in Azure have recovered following Microsoft’s rollback of a recent network configuration change. Confluent systems are fully operational at this time, though Microsoft is continuing to monitor the rollback and validate stability. We will remain in monitoring until Microsoft confirms full recovery.
Oct 29, 20:35 UTC
Monitoring - Microsoft has indicated they have completed rolling back the network configuration change. Degraded Flink statements have begun recovering.
Oct 29, 18:59 UTC
Identified - Confluent has confirmed that Flink statements running in Azure are currently degraded. Microsoft is actively working to roll back the configuration change.
Oct 29, 18:39 UTC
Update - We are continuing to investigate this issue.
Oct 29, 18:12 UTC
Investigating - Confluent engineers are engaged on the incident.
The impact is related to the ongoing Azure incident. You can find more information here: https://azure.status.microsoft/en-us/status

Oct 29, 16:55 UTC
Oct 29, 2025
Resolved - Some customers in AWS us-east-1 may have experienced unavailability of produce requests for Enterprise SKU clusters from 3:40 to 4:05 PM UTC.
Oct 29, 17:00 UTC
Oct 28, 2025

No incidents reported.

Oct 27, 2025
Resolved - This incident has been resolved.
Oct 27, 18:13 UTC
Update - We are currently investigating the issue. In the meantime, customers can use the CLI to manage the resources.
Oct 27, 17:56 UTC
Investigating - We are currently investigating the root cause.
Oct 27, 17:48 UTC
Oct 26, 2025

No incidents reported.