### Peering Policy Exascale has a selective but generally open peering policy - peers are selected based upon performance, capability, and evidenced traffic flows over the 95th percentile. Peers are subject to certain operational, technical, and legal requirements. - less than 500 Mbps: route over exchange route-servers on common public IXP - more than 500 Mbps: direct BGP session on common public IXP - more than 1 Gbps: possible PNI in one of common POPs - more than 10 Gbps: if we have no POP in common, contact us to discuss possible solutions - We only support 10GE or 100GE interfaces or multiples thereof ### Technical Requirements The following technical requirements apply when peering with Exascale (AS61049), peers must: - Have a publicly routed ASN. - Not advertise prefixes with a mask longer than /24 for IPv4. - Announce a consistent set of prefixes to Exascale at all points of interconnection, unless otherwise agreed. - Only send traffic destined for prefixes announced by Exascale. - Never point a default route towards Exascale or use static routes to send traffic to AS61049. - Register their prefixes with appropriate route/route6 objects at an appropriate IRRDB. - Maintain a full and accurate PeeringDB listing. ### MEDs Not accepted by default, but if you advertise meaningful values then let us know and we'll happily use them.

ok

2024-06-26T04:47:55Z