bgpreport

Network · data from 2026-11-12

AS18272 BC-NET - Benesse Corporation

Registry name: BC-NET - Benesse Corporation, JP · not in PeeringDB

11IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
11No 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 AS18272, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18272, 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.
182.16.236.0/22 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
182.16.237.0/24 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
182.16.238.0/24 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
182.16.239.0/24 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
202.8.6.0/23 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
202.8.7.0/24 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
202.143.2.0/23 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
202.143.2.0/24 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
202.143.3.0/24 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
202.8.6.0/24 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
182.16.236.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 67

AS-SET

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

  • ROA: none11
  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
ROA: none182.16.236.0/22No ROA covers it. Add a ROA for AS18272, maxLength 22.673 of 673
Route object: RIR182.16.236.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none182.16.237.0/24No ROA covers it. Add a ROA for AS18272, maxLength 24.673 of 673
Route object: RIR182.16.237.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none182.16.238.0/24No ROA covers it. Add a ROA for AS18272, maxLength 24.673 of 673
Route object: RIR182.16.238.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none182.16.239.0/24No ROA covers it. Add a ROA for AS18272, maxLength 24.673 of 673
Route object: RIR182.16.239.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.8.6.0/23No ROA covers it. Add a ROA for AS18272, maxLength 23.673 of 673
Route object: RIR202.8.6.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.8.7.0/24No ROA covers it. Add a ROA for AS18272, maxLength 24.673 of 673
Route object: RIR202.8.7.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.143.2.0/23No ROA covers it. Add a ROA for AS18272, maxLength 23.673 of 673
Route object: RIR202.143.2.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.143.2.0/24No ROA covers it. Add a ROA for AS18272, maxLength 24.673 of 673
Route object: RIR202.143.2.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.143.3.0/24No ROA covers it. Add a ROA for AS18272, maxLength 24.673 of 673
Route object: RIR202.143.3.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.8.6.0/24No ROA covers it. Add a ROA for AS18272, maxLength 24.672 of 673
Route object: RIR202.8.6.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none182.16.236.0/24No ROA covers it. Add a ROA for AS18272, maxLength 24.670 of 673
Route object: RIR182.16.236.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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