Serverius Peering Requirements
Serverius is willing to peer (IPv4 and IPv6) with networks which are connected to one or more exchange points which we have in common.
If you require a more formal agreement, contact us and we will make arrangements. We will announce to you via BGP4 any routes which we carry and will listen to any routes that you carry. Our peering policy is simple, if you peer with Serverius, we expect the following:
- Only send us traffic that is destined for the prefixes we announce to you. Do not point default at us or use static routes to send us traffic that does not match the routes we announce to you.
- Serverius will announce consistent routes at each exchange point and expects peers to do the same.
- Serverius expects you to peer at all exchange fabrics we have in common if we peer with you via public exchanges or all facilities we have in common if we peer via private interconnect with you. In other words, if you are peering in the US, Asia and Europe at the same locations as Serverius you must peer with Serverius at all those locations. This is to prevent problems for your and our US and European customers so that customer traffic does not cross the Pacific or Atlantic twice to return back to the same continent.
- Serverius sets up IPv6 peering (along with IPv4 peering) with all networks that run both protocols.
Network Information (Registered at PeeringDB)
Any network is welcome to contact Serverius via email at firstname.lastname@example.org to discuss peering. Please include your ASN and peering point locations. An up-to-date peeringDB entry is nearly always required.
|General Peering Information|
|Peering Policy||Open (for both IPv6 & IPv4)|
|Peering Contact Information|
|NOC Contactemail@example.com or +1 510 580 4100 (24 hours a day by 7 days by 365 days)|
|PeeringDB||http://AS50673.peeringdb.com (contains full contact information)|
|Postal Address||Serverius B.V.
Meppel, 7942KG, NL
Serverius Exchange Point Information
Serverius strives to provide uncongested bandwidth at all exchange points. All exchange port bandwidth is monitored and kept within acceptable levels. The network is upgraded constantly and in some case very large peers are moved onto private peering sessions.
When requesting peering with Serverius at multiple locations, we also request that backbone operators provide enough backhaul bandwidth to handle their peering bandwidth needs.
Check back regularly for additional peering exchangesAll physical peering locations are serviced by multiple 10GbE links and peering routers are capable of handling thousands of BGP sessions. Each location also provides facilities for private peering at GigE 10GigE or 40GigE levels.