bgpreport

Network · data from 2026-11-12

AS9378 CABLENET - JCOM Co., Ltd.

Registry name: CABLENET - JCOM Co., Ltd., JP · not in PeeringDB

36IPv4 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 AS9378, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9378, 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.
27.116.0.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
27.116.8.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
61.215.128.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
61.215.144.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
61.215.160.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
61.215.168.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
110.93.96.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
110.93.104.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
124.195.144.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
124.195.152.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
180.131.192.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
180.131.200.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
202.179.224.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
202.179.232.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
219.124.16.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
219.124.24.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
27.116.0.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
61.215.128.0/19 Valid Other IRR onlyJPIRR, RADB 671 100% 67
61.215.160.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
110.93.96.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
124.195.144.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
180.131.152.0/21 Valid Other IRR onlyJPIRR, RADB 671 100% 67
180.131.192.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
202.179.224.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
218.45.112.0/21 Valid Other IRR onlyJPIRR, RADB 671 100% 67
218.45.120.0/21 Valid Other IRR onlyJPIRR, RADB 671 100% 67
219.124.16.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
27.113.248.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
27.113.250.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
103.3.4.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
103.3.6.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
180.131.152.0/22 Valid Other IRR onlyJPIRR, RADB 670 100% 67
180.131.156.0/22 Valid Other IRR onlyJPIRR, RADB 670 100% 67
218.45.112.0/20 Valid Other IRR onlyJPIRR, RADB 670 100% 67
27.113.248.0/22 Valid Other IRR onlyJPIRR, RADB 669 99% 67
103.3.4.0/22 Valid Other IRR onlyJPIRR, RADB 669 99% 67

AS-SET

AS9378 isn't in PeeringDB, where networks name their 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 36 are in fix.csv.

  • Route object: RIR36
ChangePrefix or setDetailFull-table peers
Route object: RIR27.116.0.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR27.116.8.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.215.128.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.215.144.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.215.160.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.215.168.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR110.93.96.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR110.93.104.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.195.144.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.195.152.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.131.192.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.131.200.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.179.224.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.179.232.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.124.16.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.124.24.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR27.116.0.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR61.215.128.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR61.215.160.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR110.93.96.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR124.195.144.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR180.131.152.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR180.131.192.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.179.224.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.45.112.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.45.120.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR219.124.16.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR27.113.248.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR27.113.250.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.3.4.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.3.6.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR180.131.152.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR180.131.156.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR218.45.112.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR27.113.248.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.3.4.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 AS9378 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.