Outage in Confluent
All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing
Resolved MajorIncident Report
Summary AI Generated
Confluent Cloud experienced a major outage where all new dedicated Kafka cluster provisioning and expansion operations failed in Azure regions westus3, southcentralus, and eastus2. The issue was caused by an underlying Azure infrastructure problem that prevented new cluster deployments and scaling operations. The incident was resolved after 6 hours once Azure identified and implemented a fix for the underlying infrastructure issue.
Azure is investigating the issue and we will post an update soon.
Components affected
Confluent CloudNeed to monitor Confluent outages?
- Monitor all your external dependencies in one place
- Get instant alerts when outages are detected
- Be the first to know if service is down
- Show real-time status on private or public status page
- Keep your team informed
Latest Updates ( sorted recent to last )
RESOLVED
11 days ago - at 02/27/2026 01:57AM
This incident has been resolved.
IDENTIFIED
11 days ago - at 02/26/2026 11:07PM
The issue has been identified and a fix is being implemented.
INVESTIGATING
11 days ago - at 02/26/2026 07:56PM
Azure is investigating the issue and we will post an update soon.
Latest Confluent outages
Elevated Error Rates in AWS me-central-1 region - 8 days ago
Stop wasting hours on 'is it us or them?'
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with
