- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
- Regions
- apac
What to do
Check whether you use Confluent Cloud Confluent Cloud in apac. 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 12m it lasted.
Anything that failed between 2026-08-25 04:17 UTC and 2026-08-25 07:29 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 3
- investigating
We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in the Azure Southeast Asia region, beginning at approximately 03:13 UTC on 25 Aug 2026. Affected customers may experience degraded produce/consume availability or intermittent connectivity for clusters in this region. This is associated with an ongoing Microsoft Azure service disruption in the Southeast Asia region. We are actively engaged with Microsoft Azure.
provider
- monitoring
We are seeing recovery of Confluent services in the affected Azure Southeast Asia region and are continuing to monitor the situation.
provider
- resolved
Confluent services in the Azure Southeast Asia region are now healthy and operating normally.
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-3aa755d70c
Is Confluent Cloud still down?
No, this incident was resolved 2026-08-25 07:29 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
3h 12m, from 2026-08-25 04:17 UTC to 2026-08-25 07:29 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud in apac.
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.