bgpreport

Network · data from 2026-11-12

AS6507 Riot Games

Registry name: RIOT-NA1 - Riot Games, Inc, US · PeeringDB

36IPv4 routes 86.1% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
79Route objects not announced registered with origin AS6507, seen from no peer

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% 70
45.7.36.0/22 No ROA Other IRR onlyNTTCOM, RADB 668 99% 67
45.7.37.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 66
45.7.38.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
45.7.39.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
43.229.64.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
43.229.65.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 66
103.240.224.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
138.0.12.0/23 Valid Other IRR onlyRADB 673 100% 67
151.106.246.0/24 Valid Other IRR onlyRADB 673 100% 66
151.106.247.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 66
151.106.248.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
162.249.72.0/21 Valid Other IRR onlyNTTCOM, RADB 672 100% 66
162.249.72.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 66
162.249.76.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 66
185.40.64.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 66
192.64.170.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
192.64.171.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
162.249.75.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
192.64.173.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 66
192.207.0.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 66
162.249.72.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 66
185.40.64.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 66
192.64.168.0/21 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
151.106.253.0/24 Valid Other IRR onlyRADB 668 99% 67
104.160.156.0/24 Valid Other IRR onlyNTTCOM, RADB 667 99% 67
138.0.14.0/24 Valid Other IRR onlyRADB 667 99% 67
138.0.15.0/24 Valid Other IRR onlyRADB 667 99% 67
151.106.250.0/23 Valid Other IRR onlyNTTCOM, RADB 667 99% 67
151.106.252.0/24 Valid Other IRR onlyNTTCOM, RADB 667 99% 67
151.106.254.0/24 Valid Other IRR onlyNTTCOM, RADB 667 99% 67
104.160.128.0/19 Valid Other IRR onlyNTTCOM, RADB 665 99% 66
138.0.12.0/24 Valid Other IRR onlyRADB 664 99% 67
151.106.249.0/24 Valid Other IRR onlyNTTCOM, RADB 664 99% 67
2a04:82c0::/29 Valid Other IRR onlyRADB 635 100% 69
45.250.208.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.219.128.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67

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.

NameDatabaseASNsSets Route objectsAS6507 in itNot covered
AS-RIOT RADB 21118 Yes 0
ARIN (also) 21118 Yes 0
RIPE (also) 21118 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
ChangePrefix or setDetailFull-table peers
ROA: none45.7.36.0/24No ROA covers it. Add a ROA for AS6507, maxLength 24.672 of 673
Route object: RIR45.7.36.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.7.36.0/22No ROA covers it. Add a ROA for AS6507, maxLength 22.668 of 673
Route object: RIR45.7.36.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.7.37.0/24No ROA covers it. Add a ROA for AS6507, maxLength 24.667 of 673
Route object: RIR45.7.37.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.7.38.0/24No ROA covers it. Add a ROA for AS6507, maxLength 24.667 of 673
Route object: RIR45.7.38.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.7.39.0/24No ROA covers it. Add a ROA for AS6507, maxLength 24.667 of 673
Route object: RIR45.7.39.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR43.229.64.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.229.65.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.240.224.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR138.0.12.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR151.106.246.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR151.106.247.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR151.106.248.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.249.72.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR162.249.72.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR162.249.76.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR185.40.64.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR192.64.170.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR192.64.171.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR162.249.75.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.64.173.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.207.0.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR162.249.72.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR185.40.64.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR192.64.168.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR151.106.253.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR104.160.156.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR138.0.14.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR138.0.15.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR151.106.250.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR151.106.252.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR151.106.254.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR104.160.128.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR138.0.12.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR151.106.249.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR2a04:82c0::/29Route object only in RADB. Add it in the RIR database for the space.635 of 636

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/23APNIC, NTTCOM, RADBValid
43.229.64.0/24NTTCOM, RADBValid
43.229.66.0/23APNIC, NTTCOM, RADBValid
43.229.66.0/24NTTCOM, RADBValid
43.229.67.0/24NTTCOM, RADBValid
45.7.36.0/23NTTCOM, RADBNo ROA
45.7.38.0/23NTTCOM, RADBNo ROA
45.250.208.0/23APNIC, NTTCOM, RADBValid
45.250.208.0/24APNIC, NTTCOM, RADBValid
45.250.209.0/24APNIC, NTTCOM, RADBValid
45.250.210.0/23APNIC, NTTCOM, RADBValid
45.250.210.0/24APNIC, NTTCOM, RADBValid
45.250.211.0/24APNIC, NTTCOM, RADBValid
59.100.79.128/25RADBNo ROA
59.100.95.128/25RADBNo ROA
103.219.128.0/23APNIC, NTTCOM, RADBValid
103.219.128.0/24APNIC, NTTCOM, RADBValid
103.219.129.0/24APNIC, NTTCOM, RADBValid
103.219.130.0/23APNIC, NTTCOM, RADBValid
103.219.130.0/24APNIC, NTTCOM, RADBValid
103.219.131.0/24APNIC, NTTCOM, RADBValid
110.45.191.0/24NTTCOMNo ROA
117.52.75.0/24NTTCOMNo ROA
117.52.76.0/22NTTCOMNo ROA
117.52.76.0/23NTTCOM, RADBNo ROA
117.52.76.0/24NTTCOM, RADBNo ROA
117.52.77.0/24NTTCOM, RADBNo ROA
117.52.78.0/23NTTCOM, RADBNo ROA
117.52.78.0/24NTTCOM, RADBNo ROA
117.52.79.0/24NTTCOM, RADBNo ROA
117.52.101.0/24NTTCOMNo ROA
138.0.12.0/22LACNIC, NTTCOM, RADBValid
138.0.13.0/24RADBValid
138.0.14.0/23RADBValid
151.106.240.0/21RADBNo ROA
151.106.248.0/22NTTCOM, RADBNo ROA
151.106.248.0/23NTTCOM, RADBNo ROA
151.106.255.0/24RADBValid
162.249.72.0/23NTTCOM, RADBValid
162.249.73.0/24NTTCOM, RADBValid
162.249.74.0/23NTTCOM, RADBValid
162.249.74.0/24NTTCOM, RADBValid
162.249.76.0/23NTTCOM, RADBValid
162.249.76.0/24NTTCOM, RADBValid
162.249.77.0/24NTTCOM, RADBValid
162.249.78.0/23NTTCOM, RADBValid
162.249.78.0/24NTTCOM, RADBValid
162.249.79.0/24NTTCOM, RADBValid
182.162.120.0/21NTTCOMNo ROA
182.162.120.0/22NTTCOM, RADBNo ROA
182.162.120.0/23NTTCOM, RADBNo ROA
182.162.120.0/24NTTCOM, RADBNo ROA
182.162.121.0/24NTTCOM, RADBNo ROA
182.162.122.0/23NTTCOM, RADBNo ROA
182.162.122.0/24NTTCOM, RADBNo ROA
182.162.123.0/24NTTCOM, RADBNo ROA
182.162.124.0/22NTTCOM, RADBNo ROA
182.162.124.0/23NTTCOM, RADBNo ROA
182.162.124.0/24NTTCOM, RADBNo ROA
182.162.125.0/24NTTCOM, RADBNo ROA
182.162.126.0/23NTTCOM, RADBNo ROA
182.162.126.0/24NTTCOM, RADBNo ROA
182.162.127.0/24NTTCOM, RADBNo ROA
189.125.80.0/24NTTCOM, RADBNo ROA
189.125.169.0/24RADBNo ROA
192.64.168.0/22NTTCOM, RADBValid
192.64.168.0/23NTTCOM, RADBValid
192.64.168.0/24NTTCOM, RADBValid
192.64.169.0/24NTTCOM, RADBValid
192.64.170.0/23NTTCOM, RADBValid
192.64.172.0/22NTTCOM, RADBValid
192.64.172.0/23NTTCOM, RADBValid
192.64.172.0/24NTTCOM, RADBValid
192.64.174.0/23NTTCOM, RADBValid
192.64.174.0/24NTTCOM, RADBValid
192.64.175.0/24NTTCOM, RADBValid
192.91.144.0/24RADBNo ROA
2801:1b:6000::/48RADBNo ROA
2804:3ec0::/32RADBNo 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.