Skip to content
OutageDeck

Incident detail

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

Resolved incidentMajor1 affected service

Timeline window

to

Get alerted the next time Confluent Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Confluent Cloud alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    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

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

  3. Monitoring

    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

    This incident has been resolved.

Keep exploring

More from Confluent Cloud

Neighboring incidents on Confluent Cloud's timeline and the rest of their record on OutageDeck.

← Older incident

Connectivity degradation - AWS us-east-1

Newer incident →

Confluent Cloud Metrics API experienced elevated latency and error rates

All Confluent Cloud incidentsConfluent Cloud live status