Policy type: Open Peering
Last updated: October 2025
RackGenius maintains an open, settlement-free peering policy. RackGenius typically peers with IX Route Servers. If we aren't connected to Route Servers, we welcome requests where there is a clear mutual benefit and improved performance for both parties. We reserve the right to refuse or terminate any peering at our sole discretion. See below for peering requests.
Requirements
-
Settlement-free only: We do not pay for or accept paid peering.
-
Public ASN & registry accuracy: Peers must operate a public ASN and maintain correct information in PeeringDB and IRR/RPKI.
-
Consistent routing: The same set of prefixes should be advertised across all sessions (IPv4 and IPv6) in a geographic region.
-
NOC contact: Peers must maintain a 24/7/365 reachable NOC contact with authority to resolve routing or security incidents.
-
Maintenance notification: We request that peers notify us in advance of any maintenance that could affect peering sessions.
-
BGP session hygiene: No default routes, no RFC1918 space, and only legitimate customer/backbone prefixes should be advertised.
Termination
We may filter, suspend, or terminate peering at any time for:
-
Non-compliance with the above requirements.
-
Operational instability or security concerns.
-
Strategic, technical, or business reasons.
Requesting Peering
Peering requests should include:
-
ASN and PeeringDB entry
-
Contact information (NOC + abuse/security)
-
Proposed location(s), capacity, and IPs for sessions
-
Current and projected traffic estimates (optional)
Contact: please use our peering contact listed on PeeringDB (must be logged in)
PeeringDB: https://www.peeringdb.com/net/35471
