outages.live
Live

Confluent Cloud

Confluent Cloud is operational

Checked 26 s ago Operational

History

90 days agoToday

Incidents in 90 days

16

Days with an incident

17

Median duration

3 h 45 min

Longest incident

29 h 39 min

Components

1
Confluent Cloud Operational
90 days ago17 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 20, 2026

Duration3 h 41 min14:46 to 18:27Multiple Confluent Cloud services are in a degraded state - GCP EU-West2Partial outage

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

Oct 16, 2026

Duration3 h 49 min04:34 to 08:23Delay in Kafka cluster provisioningDegraded

This incident has been resolved.

Oct 15, 2026

Duration2 h 45 min16:01 to 18:46Confluent Cloud Console (UI) degraded functionalityNotice

This incident has been resolved.

Oct 9, 2026

Duration56 min23:27 to 00:23Possible outage in AWS us-east-1Partial outage

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

Duration10 h 33 min23:03 to 09:36Experiencing high error rate in AZURE in West Europe regionPartial outage

This incident has been resolved.

Oct 8, 2026

Duration56 min11:00 to 11:56Experiencing high error rate in AZURE in Germany West Central regionPartial outage

This incident has been resolved.

Sep 26, 2026

Duration13 h 4 min06:40 to 19:43Elevated error rates in Azure East USDegraded

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

Sep 23, 2026

Duration11 h 30 min11:47 to 23:17Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2Partial outage

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

Sep 22, 2026

Duration4 h 50 min15:09 to 19:58Elevated error rates in Azure Germany West Central regionPartial outage

This incident has been resolved. Clusters in the Azure's Germany West Central region are now fully operational.

Sep 21, 2026

Duration9 h 16 min16:15 to 01:31Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2Partial outage

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.

Sep 15, 2026

Duration1 h 22 min23:59 to 01:21Multiple Confluent Cloud services are in a degraded state - All regionsPartial outage

This incident has been resolved.

Sep 8, 2026

Duration17 h20:01 to 13:01Connectivity degradation - AWS us-east-1Partial outage

The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.

Duration29 h 39 min09:17 to 14:56Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1Degraded

The systems have recovered and Confluent Cloud is fully operational.

Sep 1, 2026

Duration48 min16:27 to 17:14Investigating Elevated Errors in GCP us-central1Degraded

The GCP issue affecting the us-central1 region has been mitigated and all Confluent Cloud services in the region have returned to normal operation. Provisioning capability, error rates and latency have recovered to expected levels. Customers should no longer experience impact. If you continue to see any issues, please contact Confluent Support.

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.live/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.live/feed.xml?providers=confluent
Slack
/feed subscribe https://outages.live/feed.xml?providers=confluent

Go from tracking outages to fixing production issues with Polylane.

Try Polylane