Confluent Cloud Incident History

Flink metrics and billing within us-west-2 may be delayed or incomplete; triaging is ongoing to identify the nature of the issue.

We are currently experiencing an issue where multiple customers are unable to view any clusters on the Cloud UI console, Terraform, or API, with Networking Services returning HTTP 500 errors. We are continuing to investigate this issue.

We are continuing to investigate HTTP 500 errors in production networking environments causing Clusters to not be visible in the Confluent UI.

We are continuing to investigate this issue.

We are currently investigating HTTP 500 errors in production networking environments

We are continuing to investigate HTTP 500 errors in production networking environments causing Clusters to not be visible in the Confluent UI.

We are continuing to investigate this issue.

We are currently investigating HTTP 500 errors in production networking environments

We are currently investigating HTTP 500 errors in production networking environments

From 21:59 UTC to 22:21 UTC customers observed errors in the Confluent Cloud UI, CLI and Terraform when making calls to control plane API endpoints. The issue has been resolved and there was no impact on data plane services or to other regions.

From 21:59 UTC to 22:21 UTC customers observed errors in the Confluent Cloud UI, CLI and Terraform when making calls to control plane endpoints. The issue has been resolved and there was no impact on data plane services or to other regions.

From approximately 02:23 - 02:43 UTC on 4/2/25, customers connecting to Kafka clusters in Azure/canadacentral may have experienced errors.

We are currently investigating this issue.

On March 28, 2025, between 14:23 and 16:40 UTC, the provisioning of Kafka clusters and networks were delayed. The root cause has been resolved and Kafka clusters and networks are being deployed. There is no customer action required.

This incident has been resolved.

Customers may experience delays in provisioning new Kafka clusters in Confluent Cloud. Confluent engineering has identified the root cause and is working on the fix.

The scheduled maintenance has been completed.

Scheduled maintenance is still in progress. We will provide updates as necessary.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Confluent Cloud is currently having a scheduled maintenance operation from 1:00 A.M to 3:00 A.M. UTC on March 21, 2025. During this time, managing Stream Shares and topic Access Requests will be disabled. All other Control Plane APIs and Data Plane APIs are not affected. Regular operations will resume shortly after. Learn more here: https://support.confluent.io/hc/en-us/articles/34941970895636-March-21st-2025-1-00-3-00-AM-UTC-Scheduled-Maintenance-of-Confluent-Cloud?ajs_aid=e7adf4e6-b539-43e6-ba66-7055abf695f9&ajs_uid=1122684

Azure has mitigated the networking issues and all errors on Confluent's end are recovered. See https://azure.status.microsoft/en-us/status for more details.

Azure is working to restore the networking issues, see https://azure.status.microsoft/en-us/status for more details. We are seeing recovery on our end and actively monitoring the situation.

Azure has identified a networking issue in eastus, see https://azure.status.microsoft/en-us/status for more details. Customers may also run into issues provisioning new clusters in eastus at this time.

Confluent engineering is investigating availability degradation on Azure eastus clusters. Customers using this region may experience unavailability and elevated latencies. In addition, customers may have issues using Schema Registry in this region.

This incident has been resolved.

Hot fix is ready to be deployed across the clusters and we are monitoring the progress.

All the affected workloads are mitigated and compute pools are provisioned.

We are experiencing degraded performance in provisioning for Flink customers in us-east1. Existing workloads should be fine. Engineers have identified the root cause and working on the fix.