Service information

DE-CIX route server guides

DE-CIX operates so-called route server systems (s. RFC7947 for a detailed description) to facilitate the exchange of BGP announcements between peers at DE-CIX. Each peer needs only to set up a BGP connection to the route server in order to receive the BGP announcements of all other peers with a BGP connection to the route server.

DE-CIX operates two route servers at each of its Internet Exchanges that are redundant to each other. 

Route servers keep the number of necessary BGP sessions low for DE-CIX customers because you need only one BGP session to each of the route servers to receive the prefixes of all other route server users.

You can use BGP communities to tell the DE-CIX route servers to whom to announce (or not announce) your prefixes.

Incoming: you can use filter lists on your own routers to decide what to accept (or not accept) from the prefixes the route servers announce to you.

The route servers give newly-connected networks a kickstart into peering as they receive all prefixes of all route server users without having to setup individual BGP peering sessions; one session to each of the two route servers is enough.

Route server guides for our exchanges

The detailed route server guides for our locations are linked below:

BGP communities graph

Informational BGP communities

The DE-CIX route servers tag all prefixes with certain BGP communities to indicate their origin. You can use this information to determine where a certain prefix has been injected into the DE-CIX switching platform.

Find out more
AS6695 change

Operational BGP communities

Operational BGP communities can be used to control various functions of the route server.

Find out more


RPKI at the DE-CIX route servers increase the security of the Internet routing system and support the adoption of RPKI. The adoption is essential to Internet security, and beneficial for all peers and their customers.

Find out more