Confluent Cloud incident: Elevated Kafka REST API Errors in AWS us-west-2

Affected components

• Confluent Cloud

1. resolvedFeb 25, 2026, 01:07 UTC

   This incident has been resolved.

2. identifiedFeb 25, 2026, 00:33 UTC

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

3. investigatingFeb 24, 2026, 21:16 UTC

   We are continuing to investigate this issue.

4. investigatingFeb 24, 2026, 21:16 UTC

   We are currently working on a mitigation.

5. investigatingFeb 24, 2026, 21:15 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mux: Delayed video ingest and webhook delivery for some customersMinor · Feb 24, 2026, 20:06 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history