All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing
Feb 26, 19:56 UTCFeb 27, 01:57 UTC
Duration
6h 1m
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
16 incidents
Affected
Confluent Cloud
Final update
This incident has been resolved.
Timeline
- Resolved · Feb 27, 01:57 UTC
This incident has been resolved.
- Identified · Feb 26, 23:07 UTC
The issue has been identified and a fix is being implemented.
- Investigating · Feb 26, 19:56 UTC
Azure is investigating the issue and we will post an update soon.
More from Confluent
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2311:47 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 11h 30m |
| Sep 2215:09 UTC | Elevated error rates in Azure Germany West Central region | major | 4h 50m |
| Sep 2116:15 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 9h 16m |
| Sep 1717:49 UTC | Confluent Cloud Metrics API experienced elevated latency and error rates | none | 0m |
| Sep 1523:59 UTC | Multiple Confluent Cloud services are in a degraded state - All regions | major | 1h 22m |
| Sep 820:01 UTC | Connectivity degradation - AWS us-east-1 | major | 17h |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.