Confluent Cloud outage: Connectivity degradation - AWS us-east-1

Affected components

• Confluent Cloud

1. resolvedSep 9, 2026, 13:01 UTC

   The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.

2. monitoringSep 8, 2026, 20:30 UTC

   A fix has been implemented and the team is monitoring recovery.

3. identifiedSep 8, 2026, 20:20 UTC

   A possible root cause has been identified and the Confluent Cloud team is implementing a fix

4. investigatingSep 8, 2026, 20:13 UTC

   We are continuing to investigate this issue.

5. investigatingSep 8, 2026, 20:01 UTC

   We are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.

What APIStatus.watch saw

• Sep 9, 2026, 06:45 UTCpartial outage → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• dbt Cloud: User Login Sessions TerminatedMajor · Sep 8, 2026, 18:44 UTC
• Miro: Sign-in with username and password is unavailableMajor · Sep 8, 2026, 19:21 UTC
• Shippo: Elevated error rates for the Lasership Transaction servicesMajor · Sep 8, 2026, 19:22 UTC
• Telnyx: Edge Compute StatefulActor Deploys Partial OutageMajor · Sep 8, 2026, 21:29 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Telnyx: Intermittent delays for some outbound messagesMinor · Sep 2, 2026, 21:33 UTC
• Grafana Cloud: High Latency in prod-us-east-2Minor · Sep 8, 2026, 16:14 UTC

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