Major incident
Confluent Cloud: Multiple Confluent Cloud services are in a degraded state - All regions
Sep 15, 2026, 23:59 UTC
started
01:21 UTC
resolved September 16, 2026
1 h 22 min
duration
Affected: Confluent Cloud
Current status of Confluent Cloud: Operational — live Confluent Cloud status
Timeline
- Sep 15, 2026, 23:59 UTCinvestigatingStarting 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.
- Sep 16, 2026, 00:00 UTCidentifiedThe issue has been identified and a fix is being implemented.
- Sep 16, 2026, 00:22 UTCmonitoringThe 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).
- Sep 16, 2026, 01:21 UTCresolvedThis incident has been resolved.
Updates as published by Confluent Cloud (original).
Other services with incidents at the same time
This was part of a wider event: 74 services reported incidents within the hour.
- Flexera System Status Dashboard 23:05 UTC · Flexera - EU - Policies/Automation Unavailable
More Confluent Cloud incidents
- October 20, 2026 Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
- October 16, 2026 Delay in Kafka cluster provisioning
- October 15, 2026 Confluent Cloud Console (UI) degraded functionality
- October 9, 2026 Possible outage in AWS us-east-1
- October 9, 2026 Experiencing high error rate in AZURE in West Europe region
- October 8, 2026 Experiencing high error rate in AZURE in Germany West Central region