Confluent incident
All new cluster creations in Azure westus3, southcentralus, and eastus2 are failing
Resolved after 4 hours 30 minutes, affecting Confluent Cloud, on February 11, 2026.
The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.
Affected components
Update timeline
- investigating Feb 11, 2026, 10:14 PM UTC
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 Feb 11, 2026, 10:50 PM UTC
We are continuing to investigate. Our next update will be in 90 minutes or sooner if mitigation has been achieved.
- identified Feb 12, 2026, 12:07 AM UTC
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 Feb 12, 2026, 01:58 AM UTC
We are continuing to work on mitigation for new cluster creations. We will provide another update in the next 60 minutes or sooner.
- resolved Feb 12, 2026, 02:45 AM UTC
The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.
Your product runs on more than Confluent
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services