bgpreport

Network · data from 2026-11-12

AS24259 kanuma cable television Corporation

Registry name: BC9 - kanuma cable television Corporation, JP · PeeringDB

14IPv4 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 AS24259, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24259, 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.
123.255.232.0/21 Valid Other IRR onlyJPIRR 673 100% 67
124.110.192.0/21 Valid Other IRR onlyJPIRR 673 100% 67
202.80.96.0/21 Valid Other IRR onlyJPIRR 673 100% 67
202.89.240.0/21 Valid Other IRR onlyJPIRR 673 100% 67
202.127.176.0/20 Valid Other IRR onlyJPIRR 673 100% 67
203.188.208.0/21 Valid Other IRR onlyJPIRR 673 100% 67
103.2.32.0/22 Valid Other IRR onlyJPIRR 671 100% 67
103.246.68.0/22 Valid Other IRR onlyJPIRR 671 100% 67
126.52.16.0/21 Valid Other IRR onlyJPIRR 671 100% 67
133.88.79.0/24 Valid Other IRR onlyJPIRR 671 100% 67
133.88.80.0/22 Valid Other IRR onlyJPIRR 671 100% 67
133.88.84.0/23 Valid Other IRR onlyJPIRR 671 100% 67
133.88.86.0/24 Valid Other IRR onlyJPIRR 671 100% 67
157.120.120.0/22 Valid Other IRR onlyJPIRR 671 100% 67
2402:b9c0::/32 Valid Other IRR onlyJPIRR 635 100% 67

AS-SET

AS24259's PeeringDB record names no 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 15 are in fix.csv.

  • Route object: RIR15
ChangePrefix or setDetailFull-table peers
Route object: RIR123.255.232.0/21Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR124.110.192.0/21Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR202.80.96.0/21Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR202.89.240.0/21Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR202.127.176.0/20Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR203.188.208.0/21Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR103.2.32.0/22Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR103.246.68.0/22Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR126.52.16.0/21Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR133.88.79.0/24Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR133.88.80.0/22Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR133.88.84.0/23Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR133.88.86.0/24Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR157.120.120.0/22Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR2402:b9c0::/32Route object only in JPIRR. Add it in the RIR database for the space.635 of 636

Route objects not announced

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