← Live dashboard

Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2

ResolvedmajorOfficial source confirmedSingle region affectedFirst recorded update Jun 12, 2026, 07:42 AM · Resolved Jun 12, 2026, 11:55 AM

This incident has been resolved.

Confluent Cloud live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

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)

  1. Jun 12, 2026, 11:55 AM
    Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2

    This incident has been resolved.

    Confluent Cloud ↗
  2. Jun 12, 2026, 09:53 AM
    Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2

    We have deployed a mitigation for the intermittent inter-region connectivity issues affecting AWS us-west-2, which began at approximately 04:00 UTC. Customers with clusters in or communicating with this region may have experienced delays or errors with Cluster Linking, Flink processing, and accessing logs in the Confluent Cloud UI. We are monitoring to confirm full restoration.

    Confluent Cloud ↗
  3. Jun 12, 2026, 09:11 AM
    Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2

    We continue to investigate intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking, Flink processing and logs for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.

    Confluent Cloud ↗
  4. Jun 12, 2026, 07:42 AM
    Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2

    We are investigating intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking and Apache Flink processing for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.

    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.