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
Feb 12, 2026
Resolved - The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.
Feb 12, 02:45 UTC
Update - We are continuing to work on mitigation for new cluster creations. We will provide another update in the next 60 minutes or sooner.
Feb 12, 01:58 UTC
Identified - The issue has been identified with Azure support and working on mitigating failed cluster creations. We will provide another update in the next 90 minutes or sooner if mitigation has been achieved.
Feb 12, 00:07 UTC
Update - We are continuing to investigate. Our next update will be in 90 minutes or sooner if mitigation has been achieved.
Feb 11, 22:50 UTC
Investigating - Confluent has been experiencing failures creating all new clusters in Azure westus3, southcentralus, and eastus2. The impact started at 09:50 UTC on Wednesday, February 11, 2026. We are investigating and will provide another update in 30 minutes or sooner if mitigation has been achieved.
Feb 11, 22:14 UTC
Feb 11, 2026
Feb 10, 2026

No incidents reported.

Feb 9, 2026

No incidents reported.

Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

Feb 6, 2026

No incidents reported.

Feb 5, 2026

No incidents reported.

Feb 4, 2026
Resolved - The issue has been resolved and services are operating normally. The root cause was a networking configuration change in the us-west-2 region that caused client connection issues starting at approximately 21:33 UTC, resulting in intermittent service disruption across several Confluent Cloud services, including Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication. The change was reverted, and as of 00:20 UTC, services have been fully restored.
Feb 4, 00:48 UTC
Monitoring - Confluent has identified the cause of the issue and reverted the related configuration change. During the incident, some Kafka clusters experienced intermittent connectivity issues, and some control plane services, including metrics, logging, authentication, and new cluster provisioning, were briefly impacted. The issue has been mitigated, services are stable, and we continue to monitor.
Feb 4, 00:08 UTC
Identified - We’ve identified the cause of the connection issues and are reverting a recent configuration change. Service stability is improving as the rollback progresses. We’ll continue monitoring and provide an update once all services are confirmed restored.
Feb 3, 23:25 UTC
Investigating - We are currently investigating this issue.
Feb 3, 21:33 UTC
Feb 3, 2026
Feb 2, 2026

No incidents reported.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.