Route Server

Introduction

Route servers are servers (not routers) which collect BGP announcements and send them to all their peers without any manipulation: next hops, AS-path, BGP attributes and communities are preserved.

1. Why choosing Route Servers

Keep it easy
Managing lot of BGP sessions requires time and effort. With Route Servers a moltitude of peers are reachable with only two sessions.
You can still manage direct BGP sessions with your most important peers and use Route Servers for the rest.

Use it as backup
Even if you have single BGP session with some peers, sessions with route server can grant you backup.

Mange your traffic policies
Our Route Servers support a large variety of communieties and funcionality that can be used to define your own route policies.

1.1. Our Route Servers

Type	Route Server 1	Route Server 2
AS	25309	25309
IPv4	194.116.96.254	194.116.96.253
IPv6	2001:7f8:23:ffff::ffff	2001:7f8:23:ffff::fffe
Platform	Bird	Bird

2. Supported features

Routes Filtering
We apply different filters on our Route Servers for inbound and outbound announcements. See the section below for more information

Large Communities
TOP-IX Route Servers support both standard communities and large communities

Manage your own policy
TOP-IX Route Servers support a large variety of communities that can be used to manage peers’ inbound traffics. For outbound traffic peers should configure peering policies on their routers. For a detailed list of our supported communities, please refer to this link.

Gracefull shutdown
TOP-IX Route Servers will set local preference to 0 for all the routes tagged with the community (65535,0). The community will be preserved and sent to all the peers.

2.1. Prefix filtering

Incoming prefixes
TOP-IX Route Servers perform filtering on incoming prefixes. We drop default route, bogon, Martians, RFC 1918 ranges and announcement with lenght </8 or >/24 for IPv4 and <16 or >70 for IPv6
We set a limit of 2000 routes imported for IPv4 and 200 routes for IPv6. If you need to advertise more routes, contact us.

Outgoing prefixes
From July 2019 TOP-IX Route Servers’ implement an outgoing filter based on RPKI + IRRdb checks. All prefixes which are not compliant will be dropped.

If you need to receive even not valid prefixes ( i.e research purpose ) please contact us and we will send all the routes tagged with the following schema:

ROA VALID (25309,65021) (25309,1000,1)
ROA UNKNOWN (25309,65022) (25309,1000,2)
ROA INVALID (25309,65023) (25309,1000,3)

If ROA is UNKNOWN then a check on IRRDB is performed

IRR VALID (25309,65031) (25309,1001,1)
IRR INVALID (25309,65034) (25309,1001,4)

MANRS
Yes, we are MANRS compliant. for more informations refer to www.manrs.org

3. Peering policy for IXPs

Due to interconnetcions with other IXPs, at TOP-IX Route Servers you can peer with networks from FranceIX, LyonIX and VSIX.
Routes incoming from different IXPs are tagged with special communities, see the link for more details
Due to commercial agreements, visibility of networks belonging to different IXPs is not always permitted: