bgpreport

Network · data from 2026-11-12

AS24271 Iruma CableTV

Registry name: iCTV - Iruma CATV co., JP · PeeringDB

8IPv4 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 AS24271, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24271, 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.177.64.0/18 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.177.64.0/19 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.177.64.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.177.80.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.177.96.0/19 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.177.96.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.177.112.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
218.231.216.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
2400:99a0::/32 Valid Other IRR onlyJPIRR 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS24271: AS-ICTVNET. 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 (AS24271 isn't in the set, or no route object for AS24271 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 objectsAS24271 in itNot covered
AS-ICTVNET JPIRR 119 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 9 are in fix.csv.

  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
Route object: RIR202.177.64.0/18Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.177.64.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.177.64.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.177.80.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.177.96.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.177.96.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.177.112.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR218.231.216.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2400:99a0::/32Route object only in JPIRR. Add it in the RIR database for the space.634 of 636

Route objects not announced

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