Major impactResolvedDatabases

Confluent Cloud outage: Elevated error rates in AWS me-south-1 and me-central-1 regions

Confluent Cloud reported this major-impact incident on its official status page on Apr 1, 2026, 19:52 UTC. It was resolved after 105d 7h.

Right now Confluent Cloud is operational. Live Confluent Cloud status →

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Apr 1, 2026, 19:52 UTC
started
Jul 16, 2026, 03:21 UTC
resolved
105d 7h
duration
Major
impact

Affected components

  • Confluent Cloud
  1. resolvedJul 16, 2026, 03:21 UTC

    Resolved.

  2. monitoringApr 2, 2026, 15:40 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.

  3. monitoringApr 1, 2026, 19:52 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.

  4. monitoringMar 20, 2026, 13:58 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history

Confluent Cloud outage on Apr 1, 2026: Elevated error rates in AWS me-south-1 and me-central-1 regions · APIStatus.watch