Confluent incident

Potential delays in new or updated authentication rule enforcement and potential authentication failures for some OAUTH Kafka customers - All clusters - All regions

Minor Resolved View vendor source →

Confluent experienced a minor incident on August 18, 2025 affecting Confluent Cloud, lasting 1h 26m. The incident has been resolved; the full update timeline is below.

Started
Aug 18, 2025, 06:18 PM UTC
Resolved
Aug 18, 2025, 07:45 PM UTC
Duration
1h 26m
Detected by Pingoru
Aug 18, 2025, 06:18 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Aug 18, 2025, 06:18 PM UTC

    Starting at 08:00 UTC on August 18, 2025, some customers who have created or updated role based access control policies during this incident may see a delay in those new rules getting applied. Additionally, customers who have configured OAUTH where their public key is set to be refreshed during this incident may see additional authentication failures. This can impact clusters in any cluster regardless of region or cloud provider. We are currently investigating the issue. We will post an update in 30 minutes.

  2. investigating Aug 18, 2025, 06:52 PM UTC

    We are continuing to investigate. The potential impact also includes customer who have configured OAUTH and have changed their public key in any way, including refreshing it or creating a new public key during this incident. We will post an update in 60 minutes, or sooner if mitigation has been achieved.

  3. monitoring Aug 18, 2025, 07:39 PM UTC

    As of 19:38 UTC on August 18, 2025, this incident has been mitigated. We'll continue monitoring but no longer expect any customer impact.

  4. resolved Aug 18, 2025, 07:45 PM UTC

    This incident has been resolved.