AMS-IX offers networks connected to the Peering LAN the opportunity to peer via its route servers. Our route servers offer the peers the possibility of filtering based on IRRdb objects, as well as on predefined BGP communities. Therefore, peering with the route servers does not preclude peers of maintaining their peering policy.
Normally, you need to maintain separate BGP sessions to each of your peers' routers. With a route server you can replace all or a subset of these sessions with one session towards each route server.
The goal of the route server project is to facilitate the implementation of peering arrangements, and to lower the barrier of entry for new participants on the peering platform.
The route servers do not partake in the forwarding path, so they do not forward any traffic. Also, peering with a route server does not mean that you must accept routes from all other route server participants.
Let's make it easy
Simplify the setup to as many peers as possible on the AMS-IX network. With the large amount of connected parties on the AMS-IX platform, it can be a full-time task to manage all the BGP sessions. The goal of the route servers is to simplify this task. With just two BGP sessions, you can connect to all the networks on the route servers. When a new party connects to the route servers, you can automatically exchange prefixes (depending on your filters).
Manage only your most important peers, let the route server do the rest
You probably want to exchange as much traffic as possible through the exchange, but setting up a peering takes time and effort. So only set up peering sessions with your most important peers. Let the route server do the rest.
Send and receive routes from day one
Once you connect to the route servers you will start exchanging routes immediately. The route servers are a good way to get started on the exchange.
Use it as a backup
When your BGP session to a party becomes inactive, there is a possibility that you can still connect to them via the route servers. So the use of the route servers can lead to a more stable platform.
Maintain your peering policy
The route server has built in filters that allow you to maintain your peering policies. For more information, please read the filtering topic.
|ASN: 6777||ASN: 6777|
|IPv4: 220.127.116.11||IPv4: 18.104.22.168|
|IPv6: 2001:7f8:1::a500:6777:1||IPv6: 2001:7f8:1::a500:6777:2|
|Platform: BIRD||Platform: BIRD|
The route servers are announcing around 180000 IPv4 prefixes and 28000 for IPv6. AMS-IX expects future prefix growth and therefore generally advises a max-prefix of 230000 for IPv4 and 40000 for IPv6. We recommend using the AMS-IX Looking Glass (members only) for more up-to-date information regarding announced prefixes.
Many unique ASNs participate in the route server project, representing tens of thousands of prefixes. For more information about who is participating, see the Connected Parties page.
If you would like to peer with the AMS-IX route servers, please login to our customer portal My.AMS-IX, and enable it in the configuration page of your respective connection (Connections -> Show -> Disable/Enable Peering with route-server). If you have any issues with that, please contact the AMS-IX NOC.
AMS-IX Route Servers are MANRS (Mutually Agreed Norms for Routing Security) compliant.