Confluent incident

Elevated Kafka Latency in GCP asia-southeast1

Minor Resolved View vendor source →

Confluent experienced a minor incident on February 23, 2026 affecting Confluent Cloud, lasting 11h 45m. The incident has been resolved; the full update timeline is below.

Started
Feb 23, 2026, 10:12 PM UTC
Resolved
Feb 24, 2026, 09:58 AM UTC
Duration
11h 45m
Detected by Pingoru
Feb 23, 2026, 10:12 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Feb 23, 2026, 10:12 PM UTC

    We are currently investigating this issue.

  2. investigating Feb 23, 2026, 10:17 PM UTC

    Starting 2/21/2026, 21:00 UTC We are observing Elevated Kafka Latency in GCP asia-southeast1 region for less than 0.1% of produce and fetch requests for some customers. Median latencies for both produce and fetch requests are not impacted. We are actively working with GCP to identify the root cause of the issue. We will provide next update in 2 hours or earlier.

  3. investigating Feb 23, 2026, 10:18 PM UTC

    We are continuing to investigate this issue.

  4. investigating Feb 24, 2026, 12:23 AM UTC

    We are continuing to investigate this issue with GCP. GCP is actively working on applying mitigation.

  5. monitoring Feb 24, 2026, 07:27 AM UTC

    GCP has identified the root cause and has fixed the same. Currently monitoring.

  6. resolved Feb 24, 2026, 09:58 AM UTC

    The issue was resolved successfully. All systems working as expected.