Live / Incidents / Confluent Cloud

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

Confluent Cloud · confluent.cloudImpact: majorResolved2026-09-08 20:30 UTC

Public — what happened

Summary

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

Timeline

Started — 2026-09-08 20:01 UTC
Last update — 2026-09-08 20:30 UTC
Resolved — 2026-09-09 13:09 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

With SquidGrid — where it starts on the route

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 →

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