Major incident
Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regions
Apr 1, 2026, 19:52 UTC
started
03:21 UTC
resolved July 16, 2026
105 days 7 h
duration
Affected: Confluent Cloud
Current status of Confluent Cloud: Operational — live Confluent Cloud status
Timeline
- Mar 20, 2026, 13:58 UTCmonitoringAWS 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.
- Apr 1, 2026, 19:52 UTCmonitoringProvisioning 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 2, 2026, 15:40 UTCmonitoringPer 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.
- Jul 16, 2026, 03:21 UTCresolvedResolved.
Updates as published by Confluent Cloud (original).
More Confluent Cloud incidents
- October 20, 2026 Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
- October 16, 2026 Delay in Kafka cluster provisioning
- October 15, 2026 Confluent Cloud Console (UI) degraded functionality
- October 9, 2026 Possible outage in AWS us-east-1
- October 9, 2026 Experiencing high error rate in AZURE in West Europe region
- October 8, 2026 Experiencing high error rate in AZURE in Germany West Central region