rewindex

CompaniesConfluentIncidents

Confluent: Kafka cluster and network provisioning delays

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.confluent.cloud (opens in new tab)

Timeline of updates

  1. resolved

    On March 28, 2025, between 14:23 and 16:40 UTC, the provisioning of Kafka clusters and networks were delayed. The root cause has been resolved and Kafka clusters and networks are being deployed. There is no customer action required.

From Confluent’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.confluent.cloud (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Confluent, started 2025-03-28 14:23 UTC, resolved after 0 min, 1 update(s).

Title
Kafka cluster and network provisioning delays
Vendor
Confluent
Date
URL
https://rewindex.com/company/confluent/incidents/5y62ptkycdrn

Confluent profileRecent Confluent incidentsAll outages on March 28, 2025Confluent in March 2025MarkdownJSON