Help Center/ Direct Connect/ Troubleshooting/ Routing Issues
Updated on 2025-08-13 GMT+08:00
View PDF

Routing Issues

If static routes have been delivered for the virtual interface or a BGP peer relationship has been established, perform the following steps to locate the fault:

Accessing a VPC through Direct Connect

  1. Verify that the routes between your gateway and your on-premises network are reachable.
  2. Verify that the routes to your on-premises network are propagated and correctly configured in the remote subnet of the virtual interface if static routing is configured for the virtual interface, or BGP is used to route traffic to your on-premises network if you have selected BGP routing.
  3. Verify that the VPC CIDR block is correctly configured on the virtual gateway.
  4. Verify that the security group and network ACL rules allow inbound and outbound traffic.

Accessing a VPC Through Direct Connect and Enterprise Router

  1. Verify that the routes between your gateway and your on-premises network are reachable.
  2. Verify that the routes to your on-premises network are propagated and correctly configured in the remote subnet of the virtual interface if static routing is configured for the virtual interface, or BGP is used to route traffic to your on-premises network if you have selected BGP routing.
  3. Verify that the enterprise router route table contains the association and propagation of the global DC gateway attachment, the routes destined for your on-premises network (with the next hop set to the global DC gateway), and the routes destined for the VPC you want to access (with the next hop set to the VPC).
  4. Verify that routes whose destination is your on-premises network and next hop is the enterprise router are added to your VPC route table.
  5. Verify that the security group and network ACL rules allow inbound and outbound traffic.