Delay in Kafka cluster provisioning
This incident has been resolved.
The latest update from Confluent Cloud.
State
Resolved
Started
16 d ago
2026-10-16 04:34 UTC
Lasted
3 h 49 min
until 2026-10-16 08:23 UTC
Worst impact
Degraded
Timeline
9 updatesIdentified
2 h 13 min 58%
Monitoring
1 h 36 min 42%
Updates
Times in UTCAs posted by Confluent Cloud
This incident has been resolved.
We are continuing to monitor for any further issues.
We have mitigated the issue that was causing delays in Kafka cluster provisioning and we are now monitoring the health of new cluster provisioning. Existing clusters were not affected. We will post our next update by 07:30 UTC, or sooner if there is new information
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Clusters provisioned during this window may take longer than usual to become available. Our next update will be posted by 6:30 UTC or as more information becomes available
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Our next update will be posted by 5:30 UTC or as more information becomes available
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Our next update will be posted by 5:30 UTC or as more information becomes available
We have identified the cause of the delays in Kafka cluster provisioning in all regions and are working on mitigation. Existing clusters continue to operate normally. Our next update will be posted by 4:30 UTC or as more information becomes available.
We are still investigating the delays in Kafka cluster provisioning in all regions and are actively working on mitigation. Existing clusters continue to operate normally. Our next update will be posted by 3:30 UTC or as more information becomes available.
We are investigating an issue that is causing delays in Kafka cluster provisioning in all regions. Existing clusters are not affected and continue to operate normally. We will provide another update within 60 minutes.
Affected components
1Confluent Cloud in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
17
Median duration
3 h 45 min
This incident
About the median
Other Confluent Cloud incidents
All incidentsConfluent 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.
Confluent Cloud·Confluent Cloud Console (UI) degraded functionality
This incident has been resolved.
Confluent Cloud·Possible outage in AWS us-east-1
This incident has been resolved. All affected services have fully recovered.
Confluent Cloud·Experiencing high error rate in AZURE in West Europe region
This incident has been resolved.
Confluent Cloud·Experiencing high error rate in AZURE in Germany West Central region
This incident has been resolved.
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.
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.
https://outages.cc/feed.xml?providers=confluent/feed subscribe https://outages.cc/feed.xml?providers=confluentFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane