outages.live
Live
Confluent CloudIncident · 2026-09-23 11:47 UTC

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

ResolvedOfficial update

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

The latest update from Confluent Cloud.

State

Resolved

Started

39 d ago

2026-09-23 11:47 UTC

Lasted

11 h 30 min

until 2026-09-23 23:17 UTC

Worst impact

Partial outage

Timeline

4 updates
11:4714:3917:3220:2423:17
Partial outageUpdate postedTimes in UTC

Identified

4 h 10 min 36%

Monitoring

7 h 19 min 64%

Updates

Times in UTC

As posted by Confluent Cloud

Resolved2026-09-23 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.

Monitoring2026-09-23 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.

Identified2026-09-23 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

Identified2026-09-23 11:47 UTC

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

Affected components

1
Confluent Cloud

Confluent Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

17

Median duration

3 h 45 min

This incident

3.1× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

29 h 39 min
median 3 h 45 min
90 days agoToday

Other Confluent Cloud incidents

All incidents

Confluent Cloud·Multiple Confluent Cloud services are in a degraded state - GCP EU-West2

This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.

Resolvedresolved 12 d ago

Confluent Cloud·Delay in Kafka cluster provisioning

This incident has been resolved.

Resolvedresolved 16 d ago

Confluent Cloud·Confluent Cloud Console (UI) degraded functionality

This incident has been resolved.

Resolvedresolved 17 d ago

Confluent Cloud·Possible outage in AWS us-east-1

This incident has been resolved. All affected services have fully recovered.

Resolvedresolved 22 d ago

Confluent Cloud·Experiencing high error rate in AZURE in West Europe region

This incident has been resolved.

Resolvedresolved 22 d ago

Follow Confluent Cloud

Your coding agent knows when Confluent Cloud is down, and tells you when a failure is theirs, not yours. You can also get Confluent Cloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "confluent" and tell me if Confluent Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=confluent
Slack
/feed subscribe https://outages.cc/feed.xml?providers=confluent

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane