Confluent incident

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

Major Resolved View vendor source →

Confluent experienced a major incident on February 26, 2026 affecting Confluent Cloud, lasting 6h 1m. The incident has been resolved; the full update timeline is below.

Started
Feb 26, 2026, 07:56 PM UTC
Resolved
Feb 27, 2026, 01:57 AM UTC
Duration
6h 1m
Detected by Pingoru
Feb 26, 2026, 07:56 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Feb 26, 2026, 07:56 PM UTC

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

  2. identified Feb 26, 2026, 11:07 PM UTC

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

  3. resolved Feb 27, 2026, 01:57 AM UTC

    This incident has been resolved.