Confluent Cloud: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2

Confluent Cloud · confluent.cloudImpact: majorResolved2026-09-22 01:31 UTC

Public — what happened

Summary

This incident has been resolved. All affected services, including Flink in AWS us-west-2, have fully recovered, and no further customer impact is expected. No action is required from customers.

Timeline

Started — 2026-09-21 16:04 UTC
Last update — 2026-09-22 01:31 UTC
Resolved — 2026-09-22 01:31 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

With SquidGrid — where it starts on the route

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see

Customers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Confluent Cloud report →

Related: Confluent Cloud status & history. SquidGrid is not affiliated with Confluent Cloud.