bgpreport

Network · data from 2026-11-12

AS18134 KITA Cable Network

Registry name: KITANET - JCOM Co., Ltd., JP · PeeringDB

24IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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 AS18134, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18134, 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.
113.197.16.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
113.197.24.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
122.50.32.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
122.50.48.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
202.57.224.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
202.57.232.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
219.112.128.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
219.112.144.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
111.125.144.0/21 Valid Other IRR onlyJPIRR, RADB 671 100% 67
113.197.16.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
122.50.32.0/19 Valid Other IRR onlyJPIRR, RADB 671 100% 67
202.57.224.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
219.112.128.0/19 Valid Other IRR onlyJPIRR, RADB 671 100% 67
103.55.196.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
103.55.198.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
111.125.144.0/22 Valid Other IRR onlyJPIRR, RADB 670 100% 67
111.125.148.0/22 Valid Other IRR onlyJPIRR, RADB 670 100% 67
203.217.180.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
203.217.182.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
219.100.24.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
219.100.26.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
103.55.196.0/22 Valid Other IRR onlyJPIRR, RADB 669 99% 67
203.217.180.0/22 Valid Other IRR onlyJPIRR, RADB 669 99% 67
219.100.24.0/22 Valid Other IRR onlyJPIRR, RADB 669 99% 67

AS-SET

AS18134'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 24 are in fix.csv.

  • Route object: RIR24
ChangePrefix or setDetailFull-table peers
Route object: RIR113.197.16.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.197.24.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR122.50.32.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR122.50.48.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.57.224.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.57.232.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.112.128.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.112.144.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.125.144.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR113.197.16.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.50.32.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.57.224.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR219.112.128.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.55.196.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.55.198.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR111.125.144.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR111.125.148.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR203.217.180.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR203.217.182.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR219.100.24.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR219.100.26.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.55.196.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR203.217.180.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR219.100.24.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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