Confluent incident

Elevated error rates in AWS me-south-1 and me-central-1 regions

Major Ongoing View vendor source →

Confluent is currently experiencing a major incident affecting Confluent Cloud, which began 77d ago. The vendor's full update timeline is below.

Started
Apr 01, 2026, 07:52 PM UTC
Resolved
Ongoing
Duration
● 77d 5h
Detected by Pingoru
Apr 01, 2026, 07:52 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. 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.

  2. 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.

  3. 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.