Companies / Confluent / incidents
Confluent: Multiple Confluent Cloud services are in a degraded state - All regions
Multiple Confluent Cloud services degraded across all regions, with major impact; the vendor reported onset at 21:25 UTC on September 15th 2026. The recorded incident ran from 2026-09-15 23:59 UTC to resolution at 2026-09-16 01:21 UTC (1 h 22 min); mitigation was deployed and services were recovering by 00:20 UTC on September 16th, 2026.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Confluent Cloud
Timeline of updates
- investigating
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.
- identified
The issue has been identified and a fix is being implemented.
- monitoring
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).
- resolved
This incident has been resolved.
Rewindex changes for this incident
- Major incident: Multiple Confluent Cloud services are in a degraded state - All regions 2026-09-15 23:59 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON