bgpreport

Network · data from 2026-11-12

AS23791 LCV - LCV Corporation

Registry name: LCV - LCV Corporation, JP · not in PeeringDB

6IPv4 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 AS23791, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23791, 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.
110.5.120.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
118.102.40.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
118.102.48.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
124.246.128.0/17 Valid Other IRR onlyJPIRR, RADB 672 100% 67
202.122.192.0/19 Valid Other IRR onlyJPIRR, RADB 672 100% 67
202.170.208.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
2402:3880::/32 Valid Other IRR onlyJPIRR, RADB 635 100% 69

AS-SET

AS23791 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 7 are in fix.csv.

  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: RIR110.5.120.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR118.102.40.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR118.102.48.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.246.128.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.122.192.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.170.208.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2402:3880::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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