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

Affected components

• Confluent Cloud

1. resolvedMar 20, 2026, 00:55 UTC

   This incident has been resolved.

2. monitoringMar 3, 2026, 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.

3. monitoringMar 2, 2026, 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.

4. monitoringMar 2, 2026, 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.

5. investigatingMar 2, 2026, 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.

6. investigatingMar 2, 2026, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snowflake: AWS - Middle East (UAE): INC0152681Critical · Mar 1, 2026, 13:33 UTC
• Grafana Cloud: Complete outage in prod-me-central-1Critical · Mar 2, 2026, 06:43 UTC
• Convex: high error rates on customer backendsCritical · Mar 4, 2026, 17:28 UTC
• Bitbucket: Disrupted Bitbucket availabilityCritical · Mar 6, 2026, 02:44 UTC
• Upstash: Region ap-northeast-1 outage on Upstash GlobalCritical · Mar 6, 2026, 13:50 UTC
• Datadog: Web Application Not LoadingCritical · Mar 13, 2026, 09:26 UTC
• Smartsheet: Brandfolder Monthly Reports DelayedMajor · Feb 27, 2026, 21:55 UTC
• MongoDB Atlas: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)Major · Mar 1, 2026, 19:30 UTC
• MongoDB Atlas: MongoDB Atlas: Email notifications may be failingMajor · Mar 2, 2026, 15:50 UTC
• New Relic: Data IrregularitiesMajor · Mar 3, 2026, 00:19 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history