Confluent experienced a major incident on February 3, 2026 affecting Confluent Cloud, lasting 3h 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 03, 2026, 11:10 PM UTC
We are currently investigating this issue.
- identified Feb 03, 2026, 11:25 PM UTC
We’ve identified the cause of the connection issues and are reverting a recent configuration change. Service stability is improving as the rollback progresses. We’ll continue monitoring and provide an update once all services are confirmed restored.
- monitoring Feb 04, 2026, 12:08 AM UTC
Confluent has identified the cause of the issue and reverted the related configuration change. During the incident, some Kafka clusters experienced intermittent connectivity issues, and some control plane services, including metrics, logging, authentication, and new cluster provisioning, were briefly impacted. The issue has been mitigated, services are stable, and we continue to monitor.
- resolved Feb 04, 2026, 12:48 AM UTC
The issue has been resolved and services are operating normally. The root cause was a networking configuration change in the us-west-2 region that caused client connection issues starting at approximately 21:33 UTC, resulting in intermittent service disruption across several Confluent Cloud services, including Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication. The change was reverted, and as of 00:20 UTC, services have been fully restored.