Peering on STLIX is simple! These steps coupled with tools such as IRR and PeeringDB will prepare your network for peering on STLIX.
If you know that you want to join STLIX then completing our peering request is the best place to start. Don't worry too much if you're unable to answer every question. It's just important that we know that you want to peer!
Once everything looks good we will issue an LOA permitting your network to connect to STLIX. This LOA will be needed by you or your transport provider when requesting the cross connect from the chosen location.
It's important to keep an up to date PeeringDB page for your network. This enables other network operators to reference information needed when peering with you. Some networks deploy automation that relies on data from PeeringDB to be correct.
An AS-SET enables your peers to filter your BGP sessions automatically. The ARIN Internet Routing Registry is free and a good place to start for those new to IRR. Be sure to include your IRR AS-SET in your PeeringDB.
An AS-SET is required to keep STLIX route servers secure.
Decide where you're going to connect to STLIX. This is where the cross connect will be made between STLIX and your network / transport provider. STLIX is available in 900 Walnut and 210 N Tucker St. Louis Missouri.
What are your port requirements? We recommend that networks connect with a minimum of 10Gbps if possible. STLIX offers 10Gbps ports for free.
If you have a POP in 900 Walnut or 210 N Tucker then you don't need transport. Simply connect to us in the building Meet-Me Room.
However some networks will need to find a transport provider to carry their traffic the "last mile" to STLIX. There are plenty of transport providers available that can link your network to STLIX.
Provide your LOA and demarc details to your transport provider or peering location to complete the cross connect.
Once you're physically connected you're ready to turn up BGP sessions with the STLIX route servers or other peers over the public STLIX peering fabric.