Incidentsby GlyphMultiple 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
20 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 historyKafka - Increased latency and connectivity issues - Azure - brazilsouthlasted 2h 9mMultiple Confluent Cloud services are in a degraded state - GCP EU-West2lasted 10h 25mDelay in Kafka cluster provisioninglasted 7h 18mConfluent Cloud Console (UI) degraded functionalitylasted 2h 45mPossible outage in AWS us-east-1lasted 56mExperiencing high error rate in AZURE in West Europe regionlasted 20h 2m