Confluent incident

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

Major Resolved View vendor source →

Confluent experienced a major incident on September 15, 2026 affecting Confluent Cloud, lasting 1h 22m. The incident has been resolved; the full update timeline is below.

Started
Sep 15, 2026, 11:59 PM UTC
Resolved
Sep 16, 2026, 01:21 AM UTC
Duration
1h 22m
Detected by Pingoru
Sep 15, 2026, 11:59 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Sep 15, 2026, 11:59 PM 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.

  2. identified Sep 16, 2026, 12:00 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Sep 16, 2026, 12:22 AM 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).

  4. resolved Sep 16, 2026, 01:21 AM UTC

    This incident has been resolved.