Major impactResolvedDatabases

Confluent Cloud outage: All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing

Confluent Cloud reported this major-impact incident on its official status page on Feb 26, 2026, 19:56 UTC. It was resolved after 6h 1m.

Right now Confluent Cloud is operational. Live Confluent Cloud status →

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Feb 26, 2026, 19:56 UTC
started
Feb 27, 2026, 01:57 UTC
resolved
6h 1m
duration
Major
impact

Affected components

  • Confluent Cloud

Timeline

updates from Confluent Cloud's status page ↗
  1. resolvedFeb 27, 2026, 01:57 UTC

    This incident has been resolved.

  2. identifiedFeb 26, 2026, 23:07 UTC

    The issue has been identified and a fix is being implemented.

  3. investigatingFeb 26, 2026, 19:56 UTC

    Azure is investigating the issue and we will post an update soon.

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.

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

← Previous: Network provisioning service in Azure East US region is degraded (Feb 26, 2026)Next: Elevated Error Rates in AWS me-central-1 region (Mar 1, 2026) →
Confluent Cloud outage on Feb 26, 2026: All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing · APIStatus.watch