- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
- Regions
- me-central-1
- Down Index
- 50of 100
What to do
Check whether you use Confluent Cloud Confluent Cloud in me-central-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 3h 57m it lasted.
Anything that failed between 2026-03-01 18:08 UTC and 2026-03-01 22:05 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 4
- investigating
We are experiencing increased error rates in some of our Confluent Cloud services in the AWS me-central-1 region. This began at approximately 12:51 PM UTC today and is linked to a disruption in one of AWS’s availability zones (mec1-az2). Our team is actively applying mitigation steps and will provide updates as the situation evolves.
provider
- identified
We have identified the cause of the problem to be disruption in one of AWS’s availability zones (mec1-az2). We are taking steps to confirm the safest path to mitigation for any impacted Confluent Cloud services in this region.
provider
- monitoring
The problem has been mitigated as of 21:15 PM UTC today. All Confluent Cloud services are now healthy in me-central-1 region and we will monitor for any residual issues before resolving this incident in 1 hour.
provider
- resolved
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
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-c1604a599a
Is Confluent Cloud still down?
No, this incident was resolved 2026-03-01 22:05 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
3h 57m, from 2026-03-01 18:08 UTC to 2026-03-01 22:05 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud in me-central-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.