bgpreport

Network · data from 2026-11-12

AS2518 BIGLOBE (AS2518)

Registry name: BIGLOBE - BIGLOBE Inc., JP · PeeringDB

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

Announced routes

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

202.247.78.0/24 Valid Nonecovered by 202.247.0.0/17 671 100% 67
49.129.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
60.236.0.0/14 Valid Other IRR onlyJPIRR, RADB 673 100% 67
61.193.0.0/17 Valid Other IRR onlyJPIRR, RADB 673 100% 67
61.203.0.0/17 Valid Other IRR onlyJPIRR, RADB 673 100% 67
110.233.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
111.168.0.0/15 Valid Other IRR onlyJPIRR, RADB 673 100% 67
118.108.0.0/14 Valid Other IRR onlyJPIRR, RADB 673 100% 67
119.238.0.0/15 Valid Other IRR onlyJPIRR, RADB 673 100% 67
119.244.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
122.130.0.0/15 Valid Other IRR onlyJPIRR, RADB 673 100% 67
122.132.0.0/14 Valid Other IRR onlyJPIRR, RADB 673 100% 67
133.200.0.0/14 Valid Other IRR onlyJPIRR, RADB 673 100% 67
133.204.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
133.205.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
133.206.0.0/15 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.225.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.247.0.0/17 Valid Other IRR onlyJPIRR, RADB 673 100% 67
203.136.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
211.13.0.0/17 Valid Other IRR onlyJPIRR, RADB 673 100% 67
211.135.128.0/17 Valid Other IRR onlyJPIRR, RADB 673 100% 67
219.107.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
220.102.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
220.144.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
221.170.0.0/15 Valid Other IRR onlyJPIRR, RADB 673 100% 67
210.147.0.0/16 Valid Other IRR onlyJPIRR, RADB 672 100% 67
210.151.128.0/17 Valid Other IRR onlyJPIRR, RADB 672 100% 67
218.42.0.0/17 Valid Other IRR onlyJPIRR, RADB 672 100% 67
218.227.0.0/16 Valid Other IRR onlyJPIRR, RADB 672 100% 67
27.127.0.0/17 Valid Other IRR onlyJPIRR, RADB 670 100% 67
119.240.0.0/14 Valid Other IRR onlyJPIRR, RADB 670 100% 67
133.208.0.0/15 Valid Other IRR onlyJPIRR, RADB 670 100% 67
125.192.0.0/13 Valid Other IRR onlyJPIRR, RADB 669 99% 67
2001:260::/32 Valid Other IRR onlyJPIRR, NTTCOM, RADB 635 100% 69
2404:7a80::/29 Valid Other IRR onlyJPIRR, RADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS2518: AS-MESH. 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 (AS2518 isn't in the set, or no route object for AS2518 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 objectsAS2518 in itNot covered
AS-MESH RADB1 member set in no database: AS-MESH-CUSTOMER:AS9326 2294019,272 Yes 0
ARIN (also) 2224 No 35
JPIRR (also)1 member set in no database: AS-MESH-CUSTOMER:AS9326 2284019,269 Yes 0
RIPE (also) 110 No 35

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

  • Route object: none1
  • Route object: RIR34
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
Route object: none202.247.78.0/24No route object for it. A route object for 202.247.0.0/17 with origin AS2518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2518 in the RIR database for the space.671 of 673
Route object: RIR49.129.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR60.236.0.0/14Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR61.193.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR61.203.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR110.233.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR111.168.0.0/15Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR118.108.0.0/14Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR119.238.0.0/15Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR119.244.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR122.130.0.0/15Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR122.132.0.0/14Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR133.200.0.0/14Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR133.204.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR133.205.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR133.206.0.0/15Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.225.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.247.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.136.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR211.13.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR211.135.128.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR219.107.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR220.102.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR220.144.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR221.170.0.0/15Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR210.147.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.151.128.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.42.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.227.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR27.127.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR119.240.0.0/14Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR133.208.0.0/15Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR125.192.0.0/13Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2001:260::/32Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2404:7a80::/29Route object only in JPIRR, RADB. Add it in the RIR database for the space.634 of 636
AS-SET: missing memberAS-MESHAS-MESH (RADB) lists AS-MESH-CUSTOMER:AS9326; no IRR database read has it.

Route objects not announced

Every route object with origin AS2518 is announced.

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.