What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Confluent Cloud now? Check the current statusAffected services
Confluent Cloud
Updates (5)
- Feb 25, 2026, 01:07 AMElevated Kafka REST API Errors in AWS us-west-2
This incident has been resolved.
Confluent Cloud ↗ - Feb 25, 2026, 12:33 AMElevated Kafka REST API Errors in AWS us-west-2
Issue has been identified and we are currently deploying the fix.
Confluent Cloud ↗ - Feb 24, 2026, 09:16 PMElevated Kafka REST API Errors in AWS us-west-2
We are continuing to investigate this issue.
Confluent Cloud ↗ - Feb 24, 2026, 09:16 PMElevated Kafka REST API Errors in AWS us-west-2
We are currently working on a mitigation.
Confluent Cloud ↗ - Feb 24, 2026, 09:15 PMElevated Kafka REST API Errors in AWS us-west-2
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.
Confluent Cloud ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Confluent Cloud's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.