Major impactResolvedDatabases

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

Confluent Cloud reported this major-impact incident on its official status page on Sep 23, 2026, 11:47 UTC. It was resolved after 11h 30m.

Right now Confluent Cloud is operational. Live Confluent Cloud status →

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Sep 23, 2026, 11:47 UTC
started
Sep 23, 2026, 23:17 UTC
resolved
11h 30m
duration
Major
impact

Affected components

  • Confluent Cloud
  1. resolvedSep 23, 2026, 23:17 UTC

    This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.

  2. monitoringSep 23, 2026, 15:57 UTC

    All affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident.

  3. identifiedSep 23, 2026, 14:18 UTC

    Flink in AWS us-west-2 is continues to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period. All other services including Connect, ConfluentCloud UI are mitigated and operational

  4. identifiedSep 23, 2026, 11:47 UTC

    The issue has been identified and a fix is being implemented.

What APIStatus.watch saw

  • Sep 23, 2026, 11:50 UTCoperational → degraded
  • Sep 23, 2026, 23:20 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

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

Confluent Cloud outage on Sep 23, 2026: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 · APIStatus.watch