Riot Games: PeeringDB fix list

AS6507 · peeringdb.com/net/5918

PeeringDB

5 things to fix in Riot Games's PeeringDB record, from what its exchanges publish: 3 to add, 2 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Riot Games's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (3)

On the exchange's own member list, but not in Riot Games's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Chennai Chennai, India · PeeringDB 2588From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. India DE-CIX Kolkata Kolkata, India · PeeringDB 2589From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Riot Games has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.13
    IPv62001:7f8:d:fe::13
    Speed10000 Mbps (10G)
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.13
    IPv62001:7f8:d:ff::13
    Speed10000 Mbps (10G)

From ixreport.com/net/6507/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.