Skip to main content
Confluent Cloud

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

Partial outage Lasted 1h 22m · started · Confluent Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
Confluent Cloud
Down Index
48of 100

What to do

  • Check whether you use Confluent Cloud Confluent Cloud. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 22m it lasted.

    Anything that failed between 2026-09-15 23:59 UTC and 2026-09-16 01:21 UTC may need a replay.
  • Subscribe to Confluent Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=confluent works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Confluent Cloud 4

  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.

    provider

  2. identified

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

    provider

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

    provider

  4. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-46f9eec7b0

Is Confluent Cloud still down?

No, this incident was resolved 2026-09-16 01:21 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.

How long did it last?

1h 22m, from 2026-09-15 23:59 UTC to 2026-09-16 01:21 UTC, by the times Confluent Cloud posted.

What was affected?

Confluent Cloud named Confluent Cloud.

What caused it?

Confluent Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Confluent Cloud's official status page, https://status.confluent.cloud, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.