Transit Gateway Connections UI Shows Failed State

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).

As of September 25, 2025, customers may observe that their AWS Transit Gateway connection is in a Failed state from within the Confluent Cloud UI. However this shouldn't impact any of your services or connectivity.
From our assessment this is likely a problem from AWS and we have escalated to AWS for resolution.

As of September 24, 2025, some customers may see their AWS Transit Gateway connection displayed as Failed in the Confluent Cloud UI. Connectivity is not impacted, and traffic is flowing normally. Our engineering team is actively investigating.

As of September 24, 2025 customers may observe that their AWS Transit Gateway connection is in a Failed state from within the Confluent Cloud UI. But connectivity is unaffected. Engineering has been engaged and are investigating the issue.