bgpreport

Network · data from 2026-11-12

AS18018 GAMEBUILDERS-AS-PH - Gamebuilders Inc.

Registry name: GAMEBUILDERS-AS-PH - Gamebuilders Inc., PH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18018, 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.

61.58.34.0/25 Valid Other IRR onlyNTTCOM 31 5%low visibility 24
122.255.93.112/28 Valid Other IRR onlyNTTCOM 28 4%low visibility 22
122.255.94.64/26 Valid Other IRR onlyNTTCOM 28 4%low visibility 22
114.141.217.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
114.141.219.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
114.141.220.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.129.220.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
202.165.60.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
114.141.221.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.129.222.0/24 Valid RIR databaseAPNIC 672 100% 67
110.50.224.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
110.50.225.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
110.50.227.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
110.50.228.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
110.50.229.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
110.50.230.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
110.50.231.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
110.50.233.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
110.50.234.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 68
114.141.216.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
114.141.222.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
114.141.223.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.221.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.165.61.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68

AS-SET

AS18018 isn't in PeeringDB, where networks name their AS-SET.

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 30 are in fix.csv.

  • Route object: RIR3
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
Route object: RIR61.58.34.0/25Route object only in NTTCOM. Add it in the RIR database for the space.31 of 673
Route object: RIR122.255.93.112/28Route object only in NTTCOM. Add it in the RIR database for the space.28 of 673
Route object: RIR122.255.94.64/26Route object only in NTTCOM. Add it in the RIR database for the space.28 of 673

Route objects not announced

Route objects with origin AS18018 whose prefix no peer sees AS18018 announce. Many are kept on purpose (backup routes, space announced only in some places).

110.50.224.0/20NTTCOM, RADBNo ROA
110.50.224.0/21RADBNo ROA
110.50.224.0/22RADBNo ROA
110.50.224.0/23APNIC, NTTCOM, RADBValid
110.50.226.0/23APNIC, RADBValid
110.50.226.0/24APNIC, NTTCOM, RADBValid
110.50.228.0/23APNIC, NTTCOM, RADBValid
110.50.230.0/23APNICValid
110.50.232.0/24APNIC, NTTCOM, RADBValid
110.50.235.0/24APNIC, NTTCOMValid
110.50.236.0/23NTTCOM, RADBNo ROA
110.50.236.0/24APNIC, NTTCOMValid
110.50.237.0/24APNIC, NTTCOM, RADBValid
110.50.238.0/23RADBNo ROA
110.50.238.0/24APNIC, NTTCOM, RADBValid
110.50.239.0/24APNIC, NTTCOM, RADBValid
114.141.216.0/21APNIC, NTTCOM, RADBValid
114.141.218.0/24APNIC, RADBValid
122.255.94.0/28NTTCOMValid
122.255.95.128/25NTTCOMValid
202.129.220.0/22NTTCOM, RADBNo ROA
202.129.222.0/23APNICValid
202.129.223.0/24APNIC, NTTCOM, RADBValid
202.151.34.0/23APNIC, NTTCOM, RADBValid
202.151.34.0/24APNIC, NTTCOM, RADBValid
202.151.35.0/24APNIC, NTTCOM, RADBValid
202.165.60.0/23NTTCOM, RADBNo 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.