Skip to main content
Confluent Cloud

Intermittent Produce/Consume Unavailability in Azure Dedicated clusters

Degraded Lasted 1h 57m · started · Confluent Cloud's page

Level
confirmed
Worst impact
Degraded
Components
Confluent Cloud
Down Index
39of 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 57m it lasted.

    Anything that failed between 2026-06-16 16:02 UTC and 2026-06-16 17:58 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

    We are currently experiencing Intermittent Produce/Consume Unavailability in Azure Dedicated clusters. The problem started at 2026-06-16 13:20 UTC. We are currently investigating and will update as we know more.

    provider

  2. monitoring

    We have found the root cause and have mitigated the problem as of 2026-06-16 16:09 UTC. We will monitor for any residual issues before resolving this incident in 1 hour.

    provider

  3. monitoring

    No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.

    provider

  4. resolved

    No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.

    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-99ff66af32

Is Confluent Cloud still down?

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

How long did it last?

1h 57m, from 2026-06-16 16:02 UTC to 2026-06-16 17:58 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.