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

Confluent: Major incident: Elevated error rates in AWS me-south-1 and me-central-1 regions

Summary

Confluent Cloud’s major incident in AWS me-south-1 and me-central-1 started 2026-04-01 19:52 UTC and resolved 2026-07-16 03:21 UTC, lasting 105 days 7 h. New workload provisioning was disabled in both regions; me-south-1 became completely unavailable, preventing cluster access. Confluent communicated migration steps and advised relocating me-central-1 workloads to another region.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Elevated error rates in AWS me-south-1 and me-central-1 regions
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-04-01 19:52 UTC
AddedResolved time#5
Before: not present
After: 2026-07-16 03:21 UTC
AddedAffected components#6
Before: not present
After: Confluent Cloud
AddedUpdatemonitoring#7
Before: not present
After: 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.
AddedUpdatemonitoring#8
Before: not present
After: 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.
AddedUpdatemonitoring#9
Before: not present
After: 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.
AddedUpdateresolved#10
Before: not present
After: Resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Elevated error rates in AWS me-south-1 and me-central-1 regions (this change)
Confluent Cloud’s major incident in AWS me-south-1 and me-central-1 started 2026-04-01 19:52 UTC and resolved 2026-07-16 03:21 UTC, lasting 105 days 7 h. New workload provisioning was disabled in both regions; me-south-1 became completely unavailable, preventing cluster access. Confluent communicated migration steps and advised relocating me-central-1 workloads to another region.
Major incident

All Confluent changes → · Confluent profile · Markdown · JSON