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 affected AWS me-south-1 and me-central-1, including a complete outage in me-central-1 caused by AWS regional infrastructure failure. Errors began approximately 05:00 AM UTC on March 2; the recorded start was 2026-03-02 07:19 UTC. me-south-1 was mitigated, and the incident resolved 2026-03-20 00:55 UTC after 17 days 17 h.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Elevated error rates in AWS me-south-1 and me-central-1 regions
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-03-02 07:19 UTC
Before: not present
After: 2026-03-20 00:55 UTC
Before: not present
After: Confluent Cloud
Before: not present
After: We are experiencing increased error rates in some of our Confluent Cloud services in AWS me-south-1 and me-central-1 regions. This began at approximately 05:00 AM UTC today and is linked to disruptions in AWS’s availability zones in these regions (mec1-az1, mec1-az3 and mes1-az2). Team is currently working on mitigating these and will provide updates as the situation evolves.
Before: not present
After: Confluent Cloud services in AWS me-central-1 region are experiencing a major outage. They are linked to AWS's me-central-1 regional outage
Confluent Cloud services in AWS me-south-1 are being mitigated.
Before: not present
After: Confluent cloud services in AWS me-south-1 are mitigated. They are currently being monitored.
Confluent Cloud Services in AWS me-central-1 are still disrupted owing to regional outage at AWS.
Before: not present
After: Confluent Cloud services in AWS me-south-1 remain stable and operating normally following mitigation. We continue to monitor for any residual issues.
Confluent Cloud services in AWS me-central-1 continue to experience a complete outage due to the ongoing AWS regional infrastructure failure in that region.
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.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Elevated error rates in AWS me-south-1 and me-central-1 regions (this change) Confluent Cloud’s major incident affected AWS me-south-1 and me-central-1, including a complete outage in me-central-1 caused by AWS regional infrastructure failure. Errors began approximately 05:00 AM UTC on March 2; the recorded start was 2026-03-02 07:19 UTC. me-south-1 was mitigated, and the incident resolved 2026-03-20 00:55 UTC after 17 days 17 h. | Major incident |
All Confluent changes → · Confluent profile · Markdown · JSON