Confluent incident

Delays in Provisioning affecting Schema Registry, KSQL and Stream Governance resources

Minor Resolved View vendor source →

Confluent experienced a minor incident on October 3, 2025 affecting Confluent Cloud, lasting 1d 11h. The incident has been resolved; the full update timeline is below.

Started
Oct 03, 2025, 04:43 AM UTC
Resolved
Oct 04, 2025, 03:46 PM UTC
Duration
1d 11h
Detected by Pingoru
Oct 03, 2025, 04:43 AM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Oct 03, 2025, 04:43 AM UTC

    We are currently experiencing degraded performance in the provisioning flow for Schema Registry, KSQL, and Stream Governance resources. Impact: Newly created clusters and API keys for these services may be delayed. You may also encounter authentication/authorization errors when using newly created keys. Unaffected: Existing clusters, keys, and resources continue to function as expected. Our engineering team is actively investigating and working to restore normal provisioning times. We will provide updates as more information becomes available.

  2. investigating Oct 03, 2025, 08:27 AM UTC

    Provisioning Performance Restored Provisioning times for Schema Registry, KSQL, and Stream Governance resources have returned to normal. Our engineering team is continuing to investigate the root cause to ensure long-term stability.

  3. monitoring Oct 03, 2025, 06:26 PM UTC

    Provisioning times have returned to normal since the last update and a mitigation has been put in place to prevent further regressions. Confluent will continue to monitoring to ensure that the issues have been resolved.

  4. resolved Oct 04, 2025, 03:46 PM UTC

    This incident has been fully resolved.