What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Confluent Cloud now? Check the current status

Affected services

Confluent Cloud

Updates (4)

Feb 4, 2026, 12:48 AM
Confluent Cloud Service Outage
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.
Confluent Cloud ↗
Feb 4, 2026, 12:08 AM
Confluent Cloud Service Outage
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.
Confluent Cloud ↗
Feb 3, 2026, 11:25 PM
Confluent Cloud Service Outage
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.
Confluent Cloud ↗
Feb 3, 2026, 11:10 PM
Confluent Cloud Service Outage
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.