Riot peers, directly interconnects with another network to exchange traffic, with internet service providers (ISPs) to provide better connectivity and service to League of Legends players.
We have a pretty open peering policy. It’s always evolving, so check back for updates.
- Riot’s willing to peer with any network connected to common exchange points.
- Private peers must have adequate capacity to support a minimum of 1Gbps peering connection and must also have a professionally managed 24/7 NOC.
- Peers must not point default route at Riot or use static routes to send us traffic that doesn’t match the routes we announce to you, and peers must not reset next hop.
- Riot will announce consistent routes at each exchange point and expects peers to do the same.
- Riot 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. In other words, if you’re peering in the US, Asia, and Europe at the same locations as Riot, you must peer with Riot s at all those locations to prevent continental tromboning.
- Peers must maintain adequate upstream bandwidth so that networks on either side may fully realize the aggregate peering bandwidth.
- Unless otherwise requested by Riot, peers must not advertise third party or transit routes to Riot Games. Only advertise routes that originate within the peer’s ASN.
- Peers must not point static routes at Riot that do not match the routes Riot has announced to you.
- Peers must use a single peering ASN at each interconnection point within the same country.
- Peers will not reset, resell, or give our next hop to others.
- Meeting the peering guidelines is not a guarantee that a peering relationship with Riot will be established. Riot will evaluate a number of factors and reserves the right not to enter into a peering agreement with an otherwise qualified applicant.
- Existing peers of AS6507 will have their peering status reviewed periodically to ensure joint capacity planning and to ensure that all criteria continue to be met. Riot reserves the right to terminate peering, upon a notice period as determined by the parties' agreement, with peers who do not meet the criteria described above.
- Periodic review of the policies contained here will be conducted to ensure that the criteria and eligibility requirements are consistent with Riots business needs. Riot may modify this settlement-free peering policy at any time.
- Both parties will monitor the health of the peering session and provide 24/7 support and contact information (including escalation points in the event of incidents).
- Riot reserves the right to filter any announced routes. As a best practice, however, Riot will generally only filter RFC6890 reserved addresses as well as its own netblocks.
- Riot will honor and expects the peer to honor the use of BGP communities as documented.
- Riot reserves the right to shut down the BGP peering session or physical link if the peering session is impacting Riot Games in a negative way, or (with notification) for planned maintenance.
- Riot expects the peering organization to provide advanced notification regarding any planned maintenance or outages with the peering transport or devices.
- Riot will protect its peering interfaces with ACLs.
- Both parties will exchange communities for RTBH (Remotely Triggered Blackholing) prefixes. Both parties will set forth a previously agreed policy on requirements and notification for blackholed prefixes.
- Peers will attempt to support BGP Flowspec (RFC 3882/5635) and provide clear definition of how and at what backbone points they will honour the flowspec ACL entries.
- If peers will not or cannot support BGP Flowspec, Riot may ask peers to manually implement ACLs on their behalf. These should be implemented at all ingress entry points of the peer's backbone to filter unwanted traffic. This will not only have security benefits in protecting Riot but it will also improve performance with less traffic hitting Riot.
- Bogon Filters will be used (per the operating policy above : see RFC6890)