Confluent Cloud Incident History
Confluent Cloud is currently operational with all systems functioning normally.
Incident History
Showing incidents from the last 15 days
Report: "Flink statements degraded in GCP us-central1 region"
Last updateAll the statements should be running now.
Currently, we are monitoring the results after rolling out the fix.
Engineers have identified and implemented a fix.
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.
Report: "Kafka cluster performance degradation for clusters in AWS region eu-central-1"
Last updateThe issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.
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.
Report: "Elevated error rates in AWS me-south-1 and me-central-1 regions"
Last updateResolved.
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.
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.
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.