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

  1. Mar 20, 2026, 13:58 UTC
    monitoring
    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.
  2. Apr 1, 2026, 19:52 UTC
    monitoring
    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.
  3. Apr 2, 2026, 15:40 UTC
    monitoring
    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.
  4. Jul 16, 2026, 03:21 UTC
    resolved
    Resolved.

Updates as published by Confluent Cloud (original).

More Confluent Cloud incidents