Live  /  Confluent Cloud  /  Incident

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

Confluent Cloud · confluent.cloudMajor incidentResolved2026-10-10 00:23 UTC
Public — what happened

Summary

Confluent Cloud said it was looking into a major problem with its services in the AWS us-east-1 region beginning at 23:27 UTC on October 9, 2026. The company said customers running Kafka clusters there could see slower responses, timed-out requests, or more errors than usual. By 23:43 UTC it reported that error levels had dropped back and services were working again, adding that customers did not need to take any steps while it worked with the provider to find the underlying cause. The incident was marked resolved at 00:23 on October 10.

Affected

Confluent Cloud

As listed on Confluent Cloud’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Confluent Cloud report →

More from Confluent Cloud

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Confluent Cloud status & history page.

Related: Confluent Cloud status & history. SquidGrid is not affiliated with Confluent Cloud.