- 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 105d 7h it lasted.
Anything that failed between 2026-04-01 19:52 UTC and 2026-07-16 03:21 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
- 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
- monitoring
Provisioning new workloads in AWS me-central-1 and me-south-1 regions is disabled. Migration steps to other AWS regions have been communicated to impacted customers.
provider
- monitoring
Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 are strongly advised to relocate them to an alternative region.
provider
- resolved
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-3d399c251c
Is Confluent Cloud still down?
No, this incident was resolved 2026-07-16 03:21 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
105d 7h, from 2026-04-01 19:52 UTC to 2026-07-16 03:21 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.