Confluent incident
Performance degradation for resources in GCP us-central1-a
Confluent experienced a critical incident on August 6, 2025 affecting Confluent Cloud, lasting 1h 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 06, 2025, 03:11 AM UTC
This manifests itself as networking errors on affected clusters. We are currently investigating and attempting to mitigate or provide a work-around.
- investigating Aug 06, 2025, 03:24 AM UTC
Affected resources are limited to a single zone in GCP, us-central1-a. We are continuing to investigate.
- investigating Aug 06, 2025, 03:47 AM UTC
GCP has confirmed that starting, August 6th 12:46 PM UTC, us-central1 is experiencing packet loss causing elevated latency and errors. GCP have communicated that they will provide an update shortly
- investigating Aug 06, 2025, 04:00 AM UTC
Resources in multiple zones in GCP us-central1 are affected. We are continuing to investigate
- monitoring Aug 06, 2025, 04:28 AM UTC
Many clusters in the affected region are recovering. We are continuing to monitor.
- monitoring Aug 06, 2025, 04:53 AM UTC
We are seeing mitigation for all impacted Kafka clusters in GCP us-central1 and are continuing to monitor.
- resolved Aug 06, 2025, 05:05 AM UTC
This incident has been resolved.