Route Servers

Route-server service for simplified multilateral peering at MBIX.

MBIX route servers let members exchange routes through multilateral peering, without configuring a separate BGP session with every participant.

How route servers help

MBIX operates two dual-stack route servers. By peering with both servers, a member can exchange routes with other route-server participants through a single pair of redundant BGP sessions. The route servers do not insert their own ASN into the AS path, so routes appear as though they were learned from the originating network.

The route servers use AS16395, the MBIX peering ASN. They provide routes over both IPv4 and IPv6 and are connected to the MBIX peering fabric with 10-gigabit links. The Peers page shows which members are currently peering with the route servers.

Routing policy and filtering

Members should advertise prefixes originated by their own AS and the ASes to which they provide transit. Do not advertise routes learned from private peers, as that can unintentionally provide transit.

MBIX applies automated filtering using IRR and RPKI data. Prefixes must be covered by valid routing objects, and the permitted AS path must include the member and its customers. Members should keep their IRR and RPKI records current so their routes pass the filters.

For operators, the Looking Glass can be used to inspect routes and BGP paths visible through the route servers. The complete Route Servers guide contains current session addresses, configuration examples, and operational details.