Elevated Kafka Latency in GCP asia-southeast1

What to do

• Check whether you use Confluent Cloud Confluent Cloud in apac, asia-southeast1. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 11h 46m it lasted.

  Anything that failed between 2026-02-23 22:12 UTC and 2026-02-24 09:58 UTC may need a replay.

• Subscribe to Confluent Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=confluent works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Confluent Cloud 6

1. investigatingFeb 23, 2026, 10:12 PM UTC

   We are currently investigating this issue.

   provider

2. investigatingFeb 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.

   provider

3. investigatingFeb 23, 2026, 10:18 PM UTC

   We are continuing to investigate this issue.

   provider

4. investigatingFeb 24, 2026, 12:23 AM UTC

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

   provider

5. monitoringFeb 24, 2026, 7:27 AM UTC

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

   provider

6. resolvedFeb 24, 2026, 9:58 AM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.