Multiple Confluent Cloud services are in a degraded state - All regions
Sep 15, 23:59 UTCSep 16, 01:21 UTC
Duration
1h 22m
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
16 incidents
Affected
Confluent Cloud
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 16, 01:21 UTC
This incident has been resolved.
- Monitoring · Sep 16, 00:22 UTC
The mitigation has been deployed and the degraded services are recovering as of 00:20 UTC on September 16th, 2026. We'll continue to monitor for any residual issues before resolving this incident in 1 hour (01:20 UTC).
- Identified · Sep 16, 00:00 UTC
The issue has been identified and a fix is being implemented.
- Investigating · Sep 15, 23:59 UTC
Starting on Tuesday, September 15th 2026 at 21:25 UTC, multiple Confluent Cloud services began entering a degraded state. We have identified the cause of the degradation and are actively mitigating the issue. Updates will be posted here in the next 30 minutes or when the issue is fully mitigated, whichever happens first.
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 820:01 UTC | Connectivity degradation - AWS us-east-1 | major | 17h |
| Sep 809:17 UTC | Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1 | minor | 29h 39m |
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.