Route server

VSIX offers to the networks connected to the Peering LAN the opportunity to peer via its route servers.

We operate two route servers based on BIRD.

Therefore peering with the route servers does not eliminate the possibility of maintaining your 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.

Why would you use the route servers?

Let's make it easy
Simplify the setup to as many peers as possible on the VSIX network. 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.

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.

RPKI Filters

Route Server support RPKI for prefix validation. It will not be necessary for you to activate RPKI in your router, but if you do not already have it done, to fully use the service you will have to create the ROA associated with your networks within the reserved area of your IRR

IRR Filters

There are also IRR filters, that accept only prefixes that match with the Route Objects defined at the IRR

Route Server details

AS Number: 35836
Network IPv4:
Network IPv6: 2001:7f8:5f:ffff::/64

Route Server 1 IPv4:
Route Server 1 IPv6: 2001:7f8:5f:ffff:fff1

Route Server 2 IPv4:
Route Server 2 IPv6: 2001:7f8:5f:ffff:fff2

We encourage networks to peer with both route servers for resilience.
Write to to enable your BGP session and for any other details.


BGP Communities

Route Servers support Satndard and Large BGP Communities

Communities that can be used in route servers to manage traffic::

Standard Community Large Community Action
0:PEERAS 35836:0:PEERAS Do not announce to PEERAS
0:35836 35836:0:0 Do not announce to any peer
35836:PEERAS 35836:1:PEERAS Explicity announce to PEERAS (if 35836:0:0 is set)
35836:35836 36836:1:0 Announce to all peers
0:64600 35836:1003:1 Do not announce to any peer from TOPIX

Table with communities applied by route servers and related actions::

Standard Community Large Community Action
35836:65501 35836:1000:1 RPKI Valid - Accepted
35836:65502 35836:1000:2 RPKI Unknown - Accepted
35836:65503 35836:1000:3 RPKI Not checked - Accepted
35836:65504 35836:1000:4 RPKI Invalid - Rejected
35836:65521 35836:1001:1 IRRdb Valid - Accepted
35836:65522 35836:1001:2 IRRdb Invalid - Rejected
35836:64600 35836:1002:1 PEERAS from TOPIX - Tag only

BGP Communities for 32-bit AS numbers

>To use BGP communities with 32-bit AS numbers, set MEMBER-AS values as listed in the following table:

Member AS BGP Community (MEMBER-AS)
Digisat 198240 65000
Siav 207042 65001
3P System 199837 65002
Nexus 199947 65003
ZG Elettronica 200794 65004 200043 65005
NETandWORK 201877 65006
Naquadria 201333 65007
Pasubio Tecnologia 200480 65008
Unica TLC 203223 65010
Progetto 8 198721 65011
Lepida2 205139 65012
Comune di Padova 204546 65013
Airgrid 201198 65014
Snapsystem 210224 65015
Hynet 199666 65016
DB Network 207054 65017
Asi srl 202308 65019
Wirelessgroup 203848 65020
Speedwifi 212686 65021