What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Confluent Cloud now? Check the current status

Affected services

Confluent Cloud

Updates (6)

Mar 20, 2026, 12:55 AM
Elevated error rates in AWS me-south-1 and me-central-1 regions
This incident has been resolved.
Confluent Cloud ↗
Mar 3, 2026, 05:34 AM
Elevated error rates in AWS me-south-1 and me-central-1 regions
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.
Confluent Cloud ↗
Mar 2, 2026, 03:37 PM
Elevated error rates in AWS me-south-1 and me-central-1 regions
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.
Confluent Cloud ↗
Mar 2, 2026, 10:35 AM
Elevated error rates in AWS me-south-1 and me-central-1 regions
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.
Confluent Cloud ↗
Mar 2, 2026, 08:32 AM
Elevated error rates in AWS me-south-1 and me-central-1 regions
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.
Confluent Cloud ↗
Mar 2, 2026, 07:19 AM
Elevated error rates in AWS me-south-1 and me-central-1 regions
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.
Confluent Cloud ↗

What to do next

Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
Watch the provider going forward. Follow Confluent Cloud's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.