What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Confluent Cloud now? Check the current status

Affected services

Confluent Cloud

Updates (4)

Jul 16, 2026, 03:21 AM
Elevated error rates in AWS me-south-1 and me-central-1 regions
Resolved.
Confluent Cloud ↗
Apr 2, 2026, 03:40 PM
Elevated error rates in AWS me-south-1 and me-central-1 regions
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.
Confluent Cloud ↗
Apr 1, 2026, 07:52 PM
Elevated error rates in AWS me-south-1 and me-central-1 regions
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.
Confluent Cloud ↗
Mar 20, 2026, 01:58 PM
Elevated error rates in AWS me-south-1 and me-central-1 regions
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.
Confluent Cloud ↗

What to do next

Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
Watch the provider going forward. Follow Confluent Cloud's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.