- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
What to do
Check whether you use Confluent Cloud Confluent Cloud. 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 56m it lasted.
Anything that failed between 2026-10-08 11:00 UTC and 2026-10-08 11:56 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
Users in Germany West Central region of Azure could face elevated error rates. We are currently investigating the issue and attempting to mitigate or provide a work-around.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-43d5b53bcf
Is Confluent Cloud still down?
No, this incident was resolved 2026-10-08 11:56 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
56m, from 2026-10-08 11:00 UTC to 2026-10-08 11:56 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud.
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.