Confluent Cloud outage: All new cluster creations in Azure westus3, southcentralus, and eastus2 are failing

Affected components

• Confluent Cloud

1. resolvedFeb 12, 2026, 02:45 UTC

   The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.

2. identifiedFeb 12, 2026, 01:58 UTC

   We are continuing to work on mitigation for new cluster creations. We will provide another update in the next 60 minutes or sooner.

3. identifiedFeb 12, 2026, 00:07 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.

4. investigatingFeb 11, 2026, 22:50 UTC

   We are continuing to investigate. Our next update will be in 90 minutes or sooner if mitigation has been achieved.

5. investigatingFeb 11, 2026, 22:14 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• LaunchDarkly: Observability – Degraded OTel Telemetry ProcessingMinor · Feb 11, 2026, 13:03 UTC
• Datadog: Delayed Traces in APM Trace SearchMinor · Feb 11, 2026, 20:56 UTC
• Datadog: Delayed Traces in APMMinor · Feb 12, 2026, 00:57 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history