What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Confluent Cloud now? Check the current statusAffected services
Updates (6)
- Feb 24, 2026, 09:58 AMElevated Kafka Latency in GCP asia-southeast1
The issue was resolved successfully. All systems working as expected.
Confluent Cloud ↗ - Feb 24, 2026, 07:27 AMElevated Kafka Latency in GCP asia-southeast1
GCP has identified the root cause and has fixed the same. Currently monitoring.
Confluent Cloud ↗ - Feb 24, 2026, 12:23 AMElevated Kafka Latency in GCP asia-southeast1
We are continuing to investigate this issue with GCP. GCP is actively working on applying mitigation.
Confluent Cloud ↗ - Feb 23, 2026, 10:18 PMElevated Kafka Latency in GCP asia-southeast1
We are continuing to investigate this issue.
Confluent Cloud ↗ - Feb 23, 2026, 10:17 PMElevated Kafka Latency in GCP asia-southeast1
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.
Confluent Cloud ↗ - Feb 23, 2026, 10:12 PMElevated Kafka Latency in GCP asia-southeast1
We are currently investigating this issue.
Confluent Cloud ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Confluent Cloud's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.