BGP Route Aggregation and Filtering Policy
Sprint installs inbound and outbound route filters for all customer Border Gateway Protocol (BGP) sessions. Inbound filters provide additional security, and stability on the network, guaranteeing greater reliability, and reduce the odds of a customer created network event.

Filter Policy

Please familiarize yourself with the Sprint Route Aggregation and Filter guidelines outlined below: 

  • Customers should perform their own route filtering before announcing to Sprint. 
  • Route filter requests sent to Sprint to be placed on the Sprint side of the BGP session should be written as inclusive lists (i.e.. stating what should be permitted). 
  • Customers desiring changes to their route filters must complete the BGP request form within Compass
  • Customers must inform Sprint on all changes in IP block announcements if an IP filter was requested at the time of installation of the BGP session. 
  • Customer filters will be aggregated if not submitted as so already. This does not materially affect your announcements, it simply reduces the complexity of the route filter. 
  • Customers may announce routes as small as /26 for ARIN IP address blocks obtained through Sprint. Customers may announce routes as small as /28 for RIPE and APNIC address blocks obtained through Sprint. However, note that IPV4 prefixes longer than /24 will be suppressed externally and will only be visible within Sprintlink. 
  • IPv4 peer block announcements and customer announcements for blocks obtained from other providers are limited to a /24 or shorter (/23, /22 etc.).
  • Customers may announce IPv6 routes as long as /64 for address space obtained through Sprint, but these routes will be suppressed externally and will only be visible within Sprintlink. Externally these routes will be covered by the Sprint aggregate prefix.
  • IPv6 peer block announcements and customer announcements for blocks obtained from other providers are limited to a /48 or shorter (/32, /40 etc.).
  • Sprint can and will take action if a BGP session is causing routing problems. This may include, but is not limited to, imposing a filter change or temporary shutdown of the offending BGP session until the problem is corrected. 
  • Sprint will filter customer block announcements if the owner of the aggregate block requests in writing that we do so. 
  • While Sprint provides its best effort to check the validity of a customer's route announcements, it is the responsibility of the customer to maintain correct information. 
  • Sprint reserves the right to set or convert any and all route filters and filter types at their own discretion to preserve network stability and route sanity.