Confluent Cloud incident: Delay in Kafka cluster provisioning

Affected components

• Confluent Cloud

1. resolvedOct 16, 2026, 08:23 UTC

   This incident has been resolved.

2. monitoringOct 16, 2026, 07:02 UTC

   We are continuing to monitor for any further issues.

3. monitoringOct 16, 2026, 06:47 UTC

   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

4. identifiedOct 16, 2026, 05:30 UTC

   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

5. identifiedOct 16, 2026, 04:35 UTC

   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

6. identifiedOct 16, 2026, 04:34 UTC

   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

7. identifiedOct 16, 2026, 03:34 UTC

   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.

8. investigatingOct 16, 2026, 02:26 UTC

   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.

9. investigatingOct 16, 2026, 01:04 UTC

   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.

What APIStatus.watch saw

• Oct 16, 2026, 07:04 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• OVHcloud: [AP-SOUTH-MUM-1][Storage] - S3 Object Storage incident notificationMajor · Oct 15, 2026, 12:24 UTC
• Shippo: USPS Service DegradationMajor · Oct 16, 2026, 04:06 UTC
• Grafana Cloud: IRM Unable to Send SMS to Thailand NumbersMinor · Oct 5, 2026, 16:17 UTC
• LiveKit: Investigating reports of elevated RoomService API errorsMinor · Oct 6, 2026, 00:10 UTC
• Shopify: Some merchants encountering error messages when trying to login to their adminsMinor · Oct 8, 2026, 14:49 UTC
• Twilio: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile ChinaMinor · Oct 9, 2026, 06:42 UTC
• Twilio: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to ThailandMinor · Oct 12, 2026, 11:53 UTC
• Grafana Cloud: Phone call notifications to numbers in Russia and Kazakhstan are blockedMinor · Oct 13, 2026, 09:23 UTC
• OpenAI: Delayed Costs data in the Compliance APIMinor · Oct 14, 2026, 17:00 UTC
• Twilio: SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Brisanet BrazilMinor · Oct 15, 2026, 15:24 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 16 incidents in the last 90 days, 12 of them major or critical. A typical incident lasted 3h 49m. See Confluent Cloud's uptime and incident history