Skip to main content
Confluent Cloud

Connectivity degradation - AWS us-east-1

Partial outage Lasted 17h · started · Confluent Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
Confluent Cloud
Regions
us, us-east-1
Down Index
53of 100

What to do

  • Check whether you use Confluent Cloud Confluent Cloud in us, us-east-1. 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 17h it lasted.

    Anything that failed between 2026-09-08 20:01 UTC and 2026-09-09 13:01 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 investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. identified

    A possible root cause has been identified and the Confluent Cloud team is implementing a fix

    provider

  4. monitoring

    A fix has been implemented and the team is monitoring recovery.

    provider

  5. resolved

    The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.

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

Is Confluent Cloud still down?

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

How long did it last?

17h, from 2026-09-08 20:01 UTC to 2026-09-09 13:01 UTC, by the times Confluent Cloud posted.

What was affected?

Confluent Cloud named Confluent Cloud in us, us-east-1.

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.