Major impactResolvedDatabases

Confluent Cloud outage: Connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2

Confluent Cloud reported this major-impact incident on its official status page on May 22, 2026, 00:21 UTC. It was resolved after 1 min.

Right now Confluent Cloud is operational. Live Confluent Cloud status →

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
May 22, 2026, 00:21 UTC
started
May 22, 2026, 00:22 UTC
resolved
1 min
duration
Major
impact

Affected components

  • Confluent Cloud

Timeline

updates from Confluent Cloud's status page ↗
  1. resolvedMay 22, 2026, 00:22 UTC

    The incident has been resolved.

  2. investigatingMay 22, 2026, 00:21 UTC

    Starting 20:26 UTC May 21, 2026, Confluent Cloud experienced connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2. We have fully mitigated the issue as of 23:56 UTC May 21, 2026 and service is operating normally.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history

← Previous: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4 (May 8, 2026)Next: Elevated error rates and latencies in Azure westus2 region (May 29, 2026) →
Confluent Cloud outage on May 22, 2026: Connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2 · APIStatus.watch