- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
- Down Index
- 51of 100
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 4h 31m it lasted.
Anything that failed between 2026-02-11 22:14 UTC and 2026-02-12 02:45 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 5
- investigating
Confluent has been experiencing failures creating all new clusters in Azure westus3, southcentralus, and eastus2. The impact started at 09:50 UTC on Wednesday, February 11, 2026. We are investigating and will provide another update in 30 minutes or sooner if mitigation has been achieved.
provider
- investigating
We are continuing to investigate. Our next update will be in 90 minutes or sooner if mitigation has been achieved.
provider
- identified
The issue has been identified with Azure support and working on mitigating failed cluster creations. We will provide another update in the next 90 minutes or sooner if mitigation has been achieved.
provider
- identified
We are continuing to work on mitigation for new cluster creations. We will provide another update in the next 60 minutes or sooner.
provider
- resolved
The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.
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-d513cc81a4
Is Confluent Cloud still down?
No, this incident was resolved 2026-02-12 02:45 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
4h 31m, from 2026-02-11 22:14 UTC to 2026-02-12 02:45 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.