- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
- Regions
- me-central-1, me-south-1
- Down Index
- 53of 100
What to do
Check whether you use Confluent Cloud Confluent Cloud in me-central-1, me-south-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 17d 17h it lasted.
Anything that failed between 2026-03-02 07:19 UTC and 2026-03-20 00:55 UTC may need a replay.Subscribe to Confluent Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=confluent works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Confluent Cloud 6
- investigating
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.
provider
- investigating
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- 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.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-db1ae1f493
Is Confluent Cloud still down?
No, this incident was resolved 2026-03-20 00:55 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
17d 17h, from 2026-03-02 07:19 UTC to 2026-03-20 00:55 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud in me-central-1, me-south-1.
What caused it?
Confluent Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Confluent Cloud's official status page, https://status.confluent.cloud, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.