Network · data from 2026-11-12
AS6507 Riot Games
Registry name: RIOT-NA1 - Riot Games, Inc, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS6507, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 45.7.36.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 45.7.36.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 668 99% |
| 45.7.37.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 667 99% |
| 45.7.38.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 667 99% |
| 45.7.39.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 667 99% |
| 43.229.64.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.229.65.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.240.224.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 138.0.12.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 151.106.246.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 151.106.247.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 151.106.248.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 162.249.72.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 162.249.72.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 162.249.76.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 185.40.64.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 192.64.170.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 192.64.171.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 162.249.75.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 192.64.173.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 192.207.0.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 162.249.72.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 185.40.64.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 192.64.168.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 669 99% |
| 151.106.253.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 104.160.156.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 667 99% |
| 138.0.14.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 138.0.15.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 151.106.250.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 667 99% |
| 151.106.252.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 667 99% |
| 151.106.254.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 667 99% |
| 104.160.128.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 665 99% |
| 138.0.12.0/24 | Valid | Other IRR onlyRADB | 664 99% |
| 151.106.249.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 664 99% |
| 2a04:82c0::/29 | Valid | Other IRR onlyRADB | 635 100% |
| 45.250.208.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.219.128.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS6507: AS-RIOT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS6507 isn't in the set, or no route object for AS6507 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS6507 in it | Not covered |
|---|---|---|---|---|---|
| AS-RIOT | RADB | 2 | 1 | Yes | 0 |
| ARIN (also) | 2 | 1 | Yes | 0 | |
| RIPE (also) | 2 | 1 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 119 are in fix.csv.
- ROA: none5
- Route object: RIR35
- Route object: not announced79
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.7.36.0/24 | No ROA covers it. Add a ROA for AS6507, maxLength 24. |
| Route object: RIR | 45.7.36.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 45.7.36.0/22 | No ROA covers it. Add a ROA for AS6507, maxLength 22. |
| Route object: RIR | 45.7.36.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 45.7.37.0/24 | No ROA covers it. Add a ROA for AS6507, maxLength 24. |
| Route object: RIR | 45.7.37.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 45.7.38.0/24 | No ROA covers it. Add a ROA for AS6507, maxLength 24. |
| Route object: RIR | 45.7.38.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 45.7.39.0/24 | No ROA covers it. Add a ROA for AS6507, maxLength 24. |
| Route object: RIR | 45.7.39.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.229.64.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.229.65.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.240.224.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.0.12.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 151.106.246.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 151.106.247.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 151.106.248.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.249.72.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.249.72.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.249.76.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 185.40.64.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.64.170.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.64.171.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.249.75.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.64.173.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.207.0.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.249.72.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 185.40.64.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.64.168.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 151.106.253.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 104.160.156.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.0.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.0.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 151.106.250.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 151.106.252.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 151.106.254.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 104.160.128.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.0.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 151.106.249.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a04:82c0::/29 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS6507 whose prefix no peer sees AS6507 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.229.64.0/23 | APNIC, NTTCOM, RADB | Valid |
| 43.229.64.0/24 | NTTCOM, RADB | Valid |
| 43.229.66.0/23 | APNIC, NTTCOM, RADB | Valid |
| 43.229.66.0/24 | NTTCOM, RADB | Valid |
| 43.229.67.0/24 | NTTCOM, RADB | Valid |
| 45.7.36.0/23 | NTTCOM, RADB | No ROA |
| 45.7.38.0/23 | NTTCOM, RADB | No ROA |
| 45.250.208.0/23 | APNIC, NTTCOM, RADB | Valid |
| 45.250.208.0/24 | APNIC, NTTCOM, RADB | Valid |
| 45.250.209.0/24 | APNIC, NTTCOM, RADB | Valid |
| 45.250.210.0/23 | APNIC, NTTCOM, RADB | Valid |
| 45.250.210.0/24 | APNIC, NTTCOM, RADB | Valid |
| 45.250.211.0/24 | APNIC, NTTCOM, RADB | Valid |
| 59.100.79.128/25 | RADB | No ROA |
| 59.100.95.128/25 | RADB | No ROA |
| 103.219.128.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.219.128.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.219.129.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.219.130.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.219.130.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.219.131.0/24 | APNIC, NTTCOM, RADB | Valid |
| 110.45.191.0/24 | NTTCOM | No ROA |
| 117.52.75.0/24 | NTTCOM | No ROA |
| 117.52.76.0/22 | NTTCOM | No ROA |
| 117.52.76.0/23 | NTTCOM, RADB | No ROA |
| 117.52.76.0/24 | NTTCOM, RADB | No ROA |
| 117.52.77.0/24 | NTTCOM, RADB | No ROA |
| 117.52.78.0/23 | NTTCOM, RADB | No ROA |
| 117.52.78.0/24 | NTTCOM, RADB | No ROA |
| 117.52.79.0/24 | NTTCOM, RADB | No ROA |
| 117.52.101.0/24 | NTTCOM | No ROA |
| 138.0.12.0/22 | LACNIC, NTTCOM, RADB | Valid |
| 138.0.13.0/24 | RADB | Valid |
| 138.0.14.0/23 | RADB | Valid |
| 151.106.240.0/21 | RADB | No ROA |
| 151.106.248.0/22 | NTTCOM, RADB | No ROA |
| 151.106.248.0/23 | NTTCOM, RADB | No ROA |
| 151.106.255.0/24 | RADB | Valid |
| 162.249.72.0/23 | NTTCOM, RADB | Valid |
| 162.249.73.0/24 | NTTCOM, RADB | Valid |
| 162.249.74.0/23 | NTTCOM, RADB | Valid |
| 162.249.74.0/24 | NTTCOM, RADB | Valid |
| 162.249.76.0/23 | NTTCOM, RADB | Valid |
| 162.249.76.0/24 | NTTCOM, RADB | Valid |
| 162.249.77.0/24 | NTTCOM, RADB | Valid |
| 162.249.78.0/23 | NTTCOM, RADB | Valid |
| 162.249.78.0/24 | NTTCOM, RADB | Valid |
| 162.249.79.0/24 | NTTCOM, RADB | Valid |
| 182.162.120.0/21 | NTTCOM | No ROA |
| 182.162.120.0/22 | NTTCOM, RADB | No ROA |
| 182.162.120.0/23 | NTTCOM, RADB | No ROA |
| 182.162.120.0/24 | NTTCOM, RADB | No ROA |
| 182.162.121.0/24 | NTTCOM, RADB | No ROA |
| 182.162.122.0/23 | NTTCOM, RADB | No ROA |
| 182.162.122.0/24 | NTTCOM, RADB | No ROA |
| 182.162.123.0/24 | NTTCOM, RADB | No ROA |
| 182.162.124.0/22 | NTTCOM, RADB | No ROA |
| 182.162.124.0/23 | NTTCOM, RADB | No ROA |
| 182.162.124.0/24 | NTTCOM, RADB | No ROA |
| 182.162.125.0/24 | NTTCOM, RADB | No ROA |
| 182.162.126.0/23 | NTTCOM, RADB | No ROA |
| 182.162.126.0/24 | NTTCOM, RADB | No ROA |
| 182.162.127.0/24 | NTTCOM, RADB | No ROA |
| 189.125.80.0/24 | NTTCOM, RADB | No ROA |
| 189.125.169.0/24 | RADB | No ROA |
| 192.64.168.0/22 | NTTCOM, RADB | Valid |
| 192.64.168.0/23 | NTTCOM, RADB | Valid |
| 192.64.168.0/24 | NTTCOM, RADB | Valid |
| 192.64.169.0/24 | NTTCOM, RADB | Valid |
| 192.64.170.0/23 | NTTCOM, RADB | Valid |
| 192.64.172.0/22 | NTTCOM, RADB | Valid |
| 192.64.172.0/23 | NTTCOM, RADB | Valid |
| 192.64.172.0/24 | NTTCOM, RADB | Valid |
| 192.64.174.0/23 | NTTCOM, RADB | Valid |
| 192.64.174.0/24 | NTTCOM, RADB | Valid |
| 192.64.175.0/24 | NTTCOM, RADB | Valid |
| 192.91.144.0/24 | RADB | No ROA |
| 2801:1b:6000::/48 | RADB | No ROA |
| 2804:3ec0::/32 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.