Confluent incident
Elevated error rates in AWS me-south-1 and me-central-1 regions
Resolved after 117 days 13 hours, affecting Confluent Cloud, on March 20, 2026.
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.
Affected components
Update timeline
- monitoring Mar 20, 2026, 01:58 PM UTC
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.
- monitoring Apr 01, 2026, 07:52 PM UTC
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.
- monitoring Apr 02, 2026, 03:40 PM UTC
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.
- resolved Jul 16, 2026, 03:21 AM UTC
Resolved.
Your product runs on more than Confluent
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services