Skip to main content
Confluent Cloud

Elevated Kafka REST API Errors in AWS us-west-2

Degraded Lasted 3h 52m · started · Confluent Cloud's page

Level
confirmed
Worst impact
Degraded
Components
Confluent Cloud
Regions
us, us-west-2
Down Index
40of 100

What to do

  • Check whether you use Confluent Cloud Confluent Cloud in us, us-west-2. 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 3h 52m it lasted.

    Anything that failed between 2026-02-24 21:15 UTC and 2026-02-25 01:07 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 experiencing an elevated level of Kafka REST API Errors with error code 429 in AWS us-west-2 and are currently looking into the issue. This issue impacts Kafka eSKU clusters in this regions.

    provider

  2. investigating

    We are currently working on a mitigation.

    provider

  3. investigating

    We are continuing to investigate this issue.

    provider

  4. identified

    Issue has been identified and we are currently deploying the fix.

    provider

  5. 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-848f48544e

Is Confluent Cloud still down?

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

How long did it last?

3h 52m, from 2026-02-24 21:15 UTC to 2026-02-25 01:07 UTC, by the times Confluent Cloud posted.

What was affected?

Confluent Cloud named Confluent Cloud in us, us-west-2.

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.