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

Jul 30, 2026

No incidents reported today.

Jul 29, 2026

No incidents reported.

Jul 28, 2026

No incidents reported.

Jul 27, 2026

No incidents reported.

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

No incidents reported.

Jul 23, 2026

No incidents reported.

Jul 22, 2026

No incidents reported.

Jul 21, 2026

No incidents reported.

Jul 20, 2026

No incidents reported.

Jul 19, 2026

No incidents reported.

Jul 18, 2026

Flink statements degraded in GCP us-central1 region
Resolved - All the statements should be running now.
Jul 18, 00:59 UTC
Monitoring - Currently, we are monitoring the results after rolling out the fix.
Jul 17, 22:55 UTC
Identified - Engineers have identified and implemented a fix.
Jul 17, 22:54 UTC
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.
Jul 17, 22:01 UTC

Jul 17, 2026

Jul 16, 2026

Kafka cluster performance degradation for clusters in AWS region eu-central-1
Resolved - The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.
Jul 16, 13:14 UTC
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.
Jul 15, 23:33 UTC
Elevated error rates in AWS me-south-1 and me-central-1 regions
Resolved - Resolved.
Jul 16, 03:21 UTC
Update - Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 are strongly advised to relocate them to an alternative region.
Apr 2, 15:40 UTC
Update - Provisioning new workloads in AWS me-central-1 and me-south-1 regions is disabled. Migration steps to other AWS regions have been communicated to impacted customers.
Apr 1, 19:52 UTC
Monitoring - AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers requiring immediate restoration in these two regions are encouraged to review regional failover options.
Mar 20, 13:58 UTC
← Incident History Powered by Atlassian Statuspage