Companies / Confluent / incidents
Confluent: Elevated error rates in AWS me-south-1 and me-central-1 regions
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 archived incident (Sol). Check the timeline before relying on it.
Affected components: Confluent Cloud
Timeline of updates
- 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.
- 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.
- 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.
- resolved
Resolved.
Rewindex changes for this incident
- Major incident: Elevated error rates in AWS me-south-1 and me-central-1 regions 2026-04-01 19:52 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON