Confluent: Transit Gateway Connections UI Shows Failed State
Timeline of updates
- resolved
AWS has confirmed that when an external principal is removed from a customer's resource share, Confluent cannot determine if the TGW attachment still exists. This results in the AWS Transit Gateway connection displaying in the Failed state from within the Confluent Cloud UI. Affected users should validate the TGW resource share is in place per our documentation (https://docs.confluent.io/cloud/current/networking/aws-transit-gateway.html#add-an-aws-transit-gateway-attachment-in-ccloud (opens in new tab)).
From Confluent’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.confluent.cloud (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Confluent, started 2025-09-24 22:46 UTC, resolved after 25 h, 1 update(s).
- Title
- Transit Gateway Connections UI Shows Failed State
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/z3mtt58h6x75
Confluent profileRecent Confluent incidentsAll outages on September 24, 2025Confluent in September 2025MarkdownJSON