Live / Confluent Cloud / Incident
Confluent Cloud: Multiple Confluent Cloud services are in a degraded state - All regions
Confluent Cloud · confluent.cloudMajor incidentResolved2026-09-16 00:22 UTC
Public — what happened
Summary
Confluent Cloud reported a major incident in which several of its cloud services were running in a degraded state across all regions, beginning at 23:59 UTC on September 15, 2026. The company said it had rolled out a fix and that the affected services were coming back as of 00:20 UTC on September 16. Confluent Cloud did not state a cause, and said it would keep watching for lingering problems before closing the incident; it was marked resolved at 01:25.
Timeline
- Started — 2026-09-15 23:59 UTC
- Resolved — 2026-09-16 01:25 UTC · 1h 26m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Confluent Cloud report →
More from Confluent Cloud
Covered in The Squid’s Ink, Week 39, 2026, our weekly internet health report.