AWS Direct Connect Adds BGP Route Visibility for Virtual Interfaces
AWS Direct Connect now offers Border Gateway Protocol (BGP) route visibility, enabling users to inspect routes exchanged with their on-premises routers across various virtual interfaces. This enhancement allows network administrators to better troubleshoot routing issues and monitor hybrid network connectivity by viewing accepted and advertised routes. The feature is available in all AWS commercial and China Regions via the Direct Connect console or API.
- →BGP Route Visibility Added to AWS Direct Connect
- →Detailed Route Information and Filtering
- →Availability and Documentation
Features (1) ›
- BGP Route Visibility Added to AWS Direct Connect
AWS Direct Connect now allows viewing BGP route exchanges with on-premises routers for private, transit, and public virtual interfaces. Users can see accepted and advertised routes, including AS path and BGP community values, directly in the console or via the ListVirtualInterfaceRoutes API.
Enhancements (1) ›
- Detailed Route Information and Filtering
Each route displayed includes its prefix, address family, AS path, community values, and installation timestamp, providing comprehensive routing topology insights. Users can filter routes by prefix, AS path, community, or address family for precise analysis.
Notes (1) ›
- Availability and Documentation
This new BGP route visibility feature is available in all AWS commercial Regions and AWS China Regions. Further details can be found in the AWS Direct Connect documentation.
https://aws.amazon.com/about-aws/whats-new/2026/07/aws-direct-connect-bgp-visibility/
Related releases
- Amazon Aurora DSQL adds multi-Region cluster support in four more Regions AWS What's New ·
- CloudWatch adds managed Prometheus collectors AWS What's New ·
- Amazon EC2 C7i Instances Expand to New Regions AWS What's New ·
- EC2 C7i-flex instances now available in Europe (Milan) region AWS What's New ·
- AWS CodeDeploy Expands to Five New Regions AWS What's New ·
- Redis 8.0 end-of-life date moved to 2026-12-01 endoflife.date ·