Who is down right now

20 down now · 248 this week

Confluent · Data and observabilityFeb 3, 2026, 21:33 UTC 9 months ago

Confluent Cloud Service Outage

MajorConfig changeUpdated 46d ago
Feb 3, 21:33 UTCFeb 4, 00:48 UTC
Duration
3h 15m
Impact
Major
Root cause
Config change
Confluent, 90 days
20 incidents
Affected
Confluent Cloud
Status page

Final update

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.

Timeline

  1. Resolved · Feb 4, 00:48 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.
  2. Monitoring · Feb 4, 00:08 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.
  3. Identified · Feb 3, 23:25 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.
  4. Investigating · Feb 3, 21:33 UTC
    We are currently investigating this issue.

More from Confluent

Full history

Also caused by configuration change

All