Live  /  Confluent Cloud  /  Incident

Confluent Cloud: Delay in Kafka cluster provisioning

Confluent Cloud · confluent.cloudMinor incidentResolved2026-10-16 08:23 UTC
Public — what happened

Summary

Confluent Cloud said that starting at 01:04 UTC on 2026-10-16, setting up new Kafka clusters was taking longer than normal in all regions, while clusters already running were not affected. The company said it identified the cause at 03:34 UTC and kept working on a fix, noting that clusters created during the window might take extra time to become available. Confluent Cloud reported at 06:47 UTC that it had mitigated the problem and was monitoring new cluster setup, and the incident was marked resolved at 08:23 UTC.

Affected

Confluent Cloud

As listed on Confluent Cloud’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Confluent Cloud report →

More from Confluent Cloud

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Confluent Cloud status & history page.

Related: Confluent Cloud status & history. SquidGrid is not affiliated with Confluent Cloud.