Major impactResolvedDatabases

Confluent Cloud outage: Possible outage in AWS us-east-1

Confluent Cloud reported this major-impact incident on its official status page on Oct 9, 2026, 23:27 UTC. It was resolved after 56 min.

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

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Oct 9, 2026, 23:27 UTC
started
Oct 10, 2026, 00:23 UTC
resolved
56 min
duration
Major
impact

Affected components

  • Confluent Cloud

Timeline

updates from Confluent Cloud's status page ↗
  1. resolvedOct 10, 2026, 00:23 UTC

    This incident has been resolved. All affected services have fully recovered.

  2. monitoringOct 9, 2026, 23:43 UTC

    The observed elevated error rates seen in AWS us-east-1 have subsided and all services have recovered. No action is required from customers at this point and we are monitoring and investigating further to understand the root cause with the provider.

  3. investigatingOct 9, 2026, 23:27 UTC

    We are investigating an incident affecting services in the AWS us-east-1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates.

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 17 incidents in the last 90 days, 12 of them major or critical. A typical incident lasted 3h 45m. See Confluent Cloud's uptime and incident history

← Previous: Experiencing high error rate in AZURE in West Europe region (Oct 9, 2026)Next: Delay in Kafka cluster provisioning (Oct 16, 2026) →