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

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

Summary

Confluent reported a major Confluent Cloud outage affecting all new dedicated Kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2. It lasted 6 h 1 min, from 2026-02-26 19:56 UTC to 2026-02-27 01:57 UTC; the issue was identified, a fix was being implemented, and the incident was subsequently resolved.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-02-26 19:56 UTC
AddedResolved time#5
Before: not present
After: 2026-02-27 01:57 UTC
AddedAffected components#6
Before: not present
After: Confluent Cloud
AddedUpdateinvestigating#7
Before: not present
After: Azure is investigating the issue and we will post an update soon.
AddedUpdateidentified#8
Before: not present
After: The issue has been identified and a fix is being implemented.
AddedUpdateresolved#9
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing (this change)
Confluent reported a major Confluent Cloud outage affecting all new dedicated Kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2. It lasted 6 h 1 min, from 2026-02-26 19:56 UTC to 2026-02-27 01:57 UTC; the issue was identified, a fix was being implemented, and the incident was subsequently resolved.
Major incident

All Confluent changes → · Confluent profile · Markdown · JSON