bgpreport

Network · data from 2026-11-12

AS45677 ISAHAYA CABLE MEDIA co.,Ltd.

Registry name: ICV - Isahaya Cable Media Co.,Ltd, JP · PeeringDB

4IPv4 routes 100.0% 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
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS45677, seen from no peer

Announced routes

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

180.148.184.0/21 Valid Other IRR onlyJPIRR, NTTCOM 672 100% 67
180.148.192.0/20 Valid Other IRR onlyJPIRR, NTTCOM 672 100% 67
192.92.248.0/21 Valid Other IRR onlyJPIRR, NTTCOM 672 100% 67
103.251.116.0/22 Valid Other IRR onlyJPIRR, NTTCOM 670 100% 67
2407:8f00::/32 Valid Other IRR onlyJPIRR, NTTCOM 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS45677: AS-ICM. 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 (AS45677 isn't in the set, or no route object for AS45677 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 objectsAS45677 in itNot covered
AS-ICM RIPE 3118 No 5
JPIRR (also) 115 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 6 are in fix.csv.

  • Route object: RIR5
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: RIR180.148.184.0/21Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR180.148.192.0/20Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR192.92.248.0/21Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.251.116.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: RIR2407:8f00::/32Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.634 of 636
AS-SET: own ASNAS-ICMAS45677 isn't in AS-ICM (RIPE) once expanded. Add AS45677 to it.

Route objects not announced

Every route object with origin AS45677 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.