bgpreport

Network · data from 2026-11-12

AS131976 JPNAP-WEST

Registry name: JPNAP-WEST - INTERNET MULTIFEED CO., JP · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.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 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS131976, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131976, 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.
218.100.45.0/24 Valid Other IRR onlyJPIRR, RADB 667 99% 67
2406:e240::/32 Valid Other IRR onlyJPIRR, RADB 636 100% 70
2406:e240:f000::/36 Valid Other IRR onlyJPIRR, RADB 4 1%low visibility 3
113.192.20.0/24 Valid Other IRR onlyJPIRR, RADB 3 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS131976: RADB::AS131976:AS-JPNAP-WEST. 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 (AS131976 isn't in the set, or no route object for AS131976 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 objectsAS131976 in itNot covered
RADB::AS131976:AS-JPNAP-WEST RADB3 member sets in no database: AS-AKAMAI, AS-CYBERHOME2, AS8220:AS-COLT-APAC 39912,108 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 8 are in fix.csv.

  • Route object: RIR4
  • AS-SET: missing member3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR218.100.45.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2406:e240::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2406:e240:f000::/36Route object only in JPIRR, RADB. Add it in the RIR database for the space.4 of 636
Route object: RIR113.192.20.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.3 of 673
AS-SET: missing memberRADB::AS131976:AS-JPNAP-WESTAS131976:AS-JPNAP-WEST (RADB) lists AS-AKAMAI; no IRR database read has it.
AS-SET: missing memberRADB::AS131976:AS-JPNAP-WESTAS131976:AS-JPNAP-WEST (RADB) lists AS-CYBERHOME2; no IRR database read has it.
AS-SET: missing memberRADB::AS131976:AS-JPNAP-WESTAS131976:AS-JPNAP-WEST (RADB) lists AS8220:AS-COLT-APAC; no IRR database read has it.

Route objects not announced

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

2406:e240::/48JPIRR, RADBValid

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.