Companies / Confluent / incidents
Confluent: Delay in Kafka cluster provisioning
Affected components: Confluent Cloud
Timeline of updates
- investigating
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.
- investigating
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.
- identified
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.
- identified
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
- identified
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
- identified
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
- monitoring
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
- monitoring
We are continuing to monitor for any further issues.
- resolved
This incident has been resolved.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON