Confluent Cloud incident: Elevated Kafka Latency in GCP asia-southeast1

Affected components

• Confluent Cloud

1. resolvedFeb 24, 2026, 09:58 UTC

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

2. monitoringFeb 24, 2026, 07:27 UTC

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

3. investigatingFeb 24, 2026, 00:23 UTC

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

4. investigatingFeb 23, 2026, 22:18 UTC

   We are continuing to investigate this issue.

5. investigatingFeb 23, 2026, 22:17 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.

6. investigatingFeb 23, 2026, 22:12 UTC

   We are currently investigating this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Pinecone: [GCP][us-central1][europe-west4] Errors on some read operationsMajor · Feb 23, 2026, 23:14 UTC
• Datadog: Delayed RUM dataMinor · Feb 24, 2026, 04:31 UTC
• Sanity: Elevated listener latency impacting Studio performanceMinor · Feb 24, 2026, 09:56 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history