Confluent Cloud: Multiple Confluent Cloud services are in a degraded state - All regions

Confluent Cloud · confluent.cloudImpact: majorResolved2026-09-16 00:22 UTC

Public — what happened

Summary

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).

Timeline

Started — 2026-09-15 23:59 UTC
Last update — 2026-09-16 00:22 UTC
Resolved — 2026-09-16 01:25 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

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 see

Customers 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 →

Related: Confluent Cloud status & history. SquidGrid is not affiliated with Confluent Cloud.