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

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-03-02 07:19 UTC · Resolved: 2026-03-20 00:55 UTC · Duration: 18 d
- Updates: 6 · Affected components: Confluent Cloud
- [Vendor status page: https://stspg.io/695lzy5z6fl2](https://stspg.io/695lzy5z6fl2)
- [Company: Confluent](https://rewindex.com/company/confluent.md)

## 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, sol)_
## Timeline of updates

- **investigating** 2026-03-02 07:19 UTC: 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.
- **investigating** 2026-03-02 08:32 UTC: 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.
- **monitoring** 2026-03-02 10:35 UTC: 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.
- **monitoring** 2026-03-02 15:37 UTC: 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.
- **monitoring** 2026-03-03 05:34 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.
- **resolved** 2026-03-20 00:55 UTC: This incident has been resolved.

## Rewindex changes for this incident

- 2026-03-02 07:19 UTC: [Major incident: Elevated error rates in AWS me-south-1 and me-central-1 regions](https://rewindex.com/change/i216a555df77571.md)


---
Canonical: https://rewindex.com/company/confluent/incidents/gd5qrkk6bdhc · Markdown: https://rewindex.com/company/confluent/incidents/gd5qrkk6bdhc.md · JSON: https://rewindex.com/api/v1/companies/confluent/incidents/gd5qrkk6bdhc · Generated 2026-10-18T12:23:23.253Z