AS53356 · Open Peering Policy

Peering with Free Range Cloud

Free Range Cloud maintains an open peering policy. If your network shares a common POP with Free Range Cloud through an Internet Exchange or dedicated cross-connect, we are generally happy to peer in that location. Peering in multiple common POPs is encouraged, but not required.

AS53356 Free Range Cloud network
Open policy Common POP peering is welcome
Gigabit+ Connectivity across all sites

Peering policy

In general, Free Range Cloud maintains an open peering policy. If a network shares a common POP with Free Range Cloud, either via IX or dedicated cross-connect, then Free Range Cloud will peer in that location.

Peering in multiple common POPs, while not required, is encouraged. Free Range Cloud requires that all peers adhere to the requirements listed on this page.

Useful network links

Review our public network profile, BGP community documentation, or test connectivity from individual Free Range Cloud locations.

Peer requirements

To keep routing clean and operational contacts reliable, Free Range Cloud asks all peers to follow these basic requirements.

Advertise your own networks Only advertise prefixes for the networks for which you operate.
No unauthorized default routes Do not point static or default routes towards 10VPN unless explicitly granted permission.
Use route validation Use IRR or RPKI filtering whenever possible.
Maintain reachable NOC contact Maintain a NOC reachable by email or phone.

Network footprint

Free Range Cloud operates infrastructure across North America and Europe. If we share a common location or exchange, reach out with your peering details.

Vancouver Calgary Winnipeg Toronto Halifax Fremont Ashburn Kansas City Amsterdam Oslo
Interested in peering? Please include your ASN, preferred peering location, contact details, and any relevant routing policy information when reaching out. Public peering information is available through our PeeringDB profile.