Confluent incident
Elevated Kafka Latency in GCP asia-southeast1
Affected components
Update timeline
- investigating Feb 23, 2026, 10:12 PM UTC
We are currently investigating this issue.
- 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.
- investigating Feb 23, 2026, 10:18 PM UTC
We are continuing to investigate this issue.
- investigating Feb 24, 2026, 12:23 AM UTC
We are continuing to investigate this issue with GCP. GCP is actively working on applying mitigation.
- monitoring Feb 24, 2026, 07:27 AM UTC
GCP has identified the root cause and has fixed the same. Currently monitoring.
- resolved Feb 24, 2026, 09:58 AM UTC
The issue was resolved successfully. All systems working as expected.
Looking to track Confluent downtime and outages?
Pingoru polls Confluent's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Confluent reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Confluent alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required