Companies / Confluent / incidents
Confluent: All new cluster creations in Azure westus3, southcentralus, and eastus2 are failing
Confluent reported a major outage preventing all new Confluent Cloud cluster creations in Azure westus3, southcentralus, and eastus2, with customer impact starting February 11, 2026 at 09:50 UTC. The recorded incident lasted 4 h 30 min and was resolved at 2026-02-12 02:45 UTC; Confluent identified the issue with Azure support and confirmed cluster creation was fixed.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Confluent Cloud
Timeline of updates
- 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.
- investigating
We are continuing to investigate. Our next update will be in 90 minutes or sooner if mitigation has been achieved.
- 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.
- identified
We are continuing to work on mitigation for new cluster creations. We will provide another update in the next 60 minutes or sooner.
- resolved
The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.
Rewindex changes for this incident
- Major incident: All new cluster creations in Azure westus3, southcentralus, and eastus2 are failing 2026-02-11 22:14 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON