Vendor reports: partial outageResolved · vendor status “resolved”Official status API
All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing
Reported by Confluent Cloud · Data & Analytics · source last read 2 min ago
- Vendor start
- Feb 26, 2026, 19:56 UTC
- Vendor's clock
- Resolved
- Feb 27, 2026, 01:57 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 6 h 1 min
- From vendor start and resolution
Affected scope
Not stated by the vendor
The vendor's feed gives no region for this incident. It is not assumed to be global.
Potential relevance
Confluent Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Feb 26, 2026, 19:56 UTCVendor-reported startVendor time
- Feb 27, 2026, 01:57 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.