Skip to main content
Confluent Cloud

Elevated error rates in Azure East US

Degraded Lasted 13h 4m · started · Confluent Cloud's page

Level
confirmed
Worst impact
Degraded
Components
Confluent Cloud
Regions
us

What to do

  • Check whether you use Confluent Cloud Confluent Cloud in us. 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 13h 4m it lasted.

    Anything that failed between 2026-09-26 06:40 UTC and 2026-09-26 19:43 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 5

  1. investigating

    We are currently investigating an issue related to elevated error rates in Azure East US

    provider

  2. identified

    Microsoft Azure has confirmed an outage impacting their Azure East US region, which is the root cause of the elevated error rates affecting Confluent services. Confluent will provide another update as soon as we receive further details.

    provider

  3. identified

    Systems are continuing to recover and are being monitored

    provider

  4. identified

    We are continuing to work on a fix for this issue.

    provider

  5. resolved

    This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.

    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-85aa0762e5

Is Confluent Cloud still down?

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

How long did it last?

13h 4m, from 2026-09-26 06:40 UTC to 2026-09-26 19:43 UTC, by the times Confluent Cloud posted.

What was affected?

Confluent Cloud named Confluent Cloud in us.

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.