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 02, 2026 - 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 01, 2026 - 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, 2026 - 13:58 UTC
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.
Resolved -
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.
Jun 23, 07:00 UTC
Resolved -
This incident has been resolved.
Jun 21, 09:19 UTC
Update -
We are continuing to monitor for any further issues.
Jun 21, 09:19 UTC
Monitoring -
The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability.
Jun 21, 08:31 UTC
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.
Jun 21, 07:14 UTC
Resolved -
No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.
Jun 16, 17:58 UTC
Update -
No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.
Jun 16, 17:58 UTC
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.
Jun 16, 16:43 UTC
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.
Jun 16, 16:02 UTC
Resolved -
This incident has been resolved.
Jun 12, 11:55 UTC
Monitoring -
We have deployed a mitigation for the intermittent inter-region connectivity issues affecting AWS us-west-2, which began at approximately 04:00 UTC. Customers with clusters in or communicating with this region may have experienced delays or errors with Cluster Linking, Flink processing, and accessing logs in the Confluent Cloud UI. We are monitoring to confirm full restoration.
Jun 12, 09:53 UTC
Update -
We continue to investigate intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking, Flink processing and logs for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.
Jun 12, 09:11 UTC
Investigating -
We are investigating intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking and Apache Flink processing for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.
Jun 12, 07:42 UTC
Completed -
The scheduled maintenance has been completed.
Jun 12, 00:00 UTC
Update -
Let's Encrypt has addressed the problem they had previously identified with their cross-signed CA certificates (see https://community.letsencrypt.org/t/upcoming-let-s-encrypt-profile-changes-on-may-13/247049/4). Confluent is now resuming this maintenance operation to replace the intermediate certificates. No downtime is expected. We will provide updates as necessary.
May 28, 19:23 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 00:00 UTC
Update -
Starting May 13, 2026, TLS certificates used to connect to Confluent Cloud will start using new intermediate certificates provided by Let's Encrypt.
No downtime is expected.
No action is needed if you haven't pinned intermediate certificates. However, if you've pinned intermediate certificates, you need to update your clients' certificates before May 13th or remove the intermediate certificate pinning to avoid connection issues.
Scheduled -
Starting May 13, 2026, TLS certificates used to connect to Confluent Cloud will start using new intermediate certificates provided by Let's Encrypt.
No downtime is expected.
No action is needed if you haven't pinned intermediate certificates. However, if you've pinned intermediate certificates, you need to update your clients' certificates before May 13th or remove the intermediate certificate pinning to avoid connection issues.