bgpreport

Network · data from 2026-11-12

AS151388 SE-JIKKEN-AS - SoftEther Corporation (SE-JIKKEN-AS)

Registry name: SE-JIKKEN-AS - SoftEther Corporation (SE-JIKKEN-AS), JP · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object
4IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS151388, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS151388, 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.
202.222.7.0/24 No ROA Other IRR onlyJPIRR 670 100% 69
219.100.39.0/24 No ROA Other IRR onlyJPIRR 670 100% 69
210.171.66.0/24 No ROA Other IRR onlyJPIRR 669 99% 69
210.171.67.0/24 No ROA Other IRR onlyJPIRR 669 99% 69
2401:af80:c401::/48 No ROA Other IRR onlyJPIRR 635 100% 67
2401:af80:c402::/48 No ROA Other IRR onlyJPIRR 635 100% 67
2401:af80:c200::/40 No ROA Other IRR onlyJPIRR 634 100% 69
2401:af80:c300::/40 No ROA Other IRR onlyJPIRR 634 100% 69

AS-SET

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

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none202.222.7.0/24No ROA covers it. Add a ROA for AS151388, maxLength 24.670 of 673
Route object: RIR202.222.7.0/24Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none219.100.39.0/24No ROA covers it. Add a ROA for AS151388, maxLength 24.670 of 673
Route object: RIR219.100.39.0/24Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none210.171.66.0/24No ROA covers it. Add a ROA for AS151388, maxLength 24.669 of 673
Route object: RIR210.171.66.0/24Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
ROA: none210.171.67.0/24No ROA covers it. Add a ROA for AS151388, maxLength 24.669 of 673
Route object: RIR210.171.67.0/24Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
ROA: none2401:af80:c401::/48No ROA covers it. Add a ROA for AS151388, maxLength 48.635 of 636
Route object: RIR2401:af80:c401::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
ROA: none2401:af80:c402::/48No ROA covers it. Add a ROA for AS151388, maxLength 48.635 of 636
Route object: RIR2401:af80:c402::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
ROA: none2401:af80:c200::/40No ROA covers it. Add a ROA for AS151388, maxLength 40.634 of 636
Route object: RIR2401:af80:c200::/40Route object only in JPIRR. Add it in the RIR database for the space.634 of 636
ROA: none2401:af80:c300::/40No ROA covers it. Add a ROA for AS151388, maxLength 40.634 of 636
Route object: RIR2401:af80:c300::/40Route object only in JPIRR. Add it in the RIR database for the space.634 of 636

Route objects not announced

Route objects with origin AS151388 whose prefix no peer sees AS151388 announce. Many are kept on purpose (backup routes, space announced only in some places).

210.171.66.0/23JPIRRNo ROA
2401:af80:c200::/39JPIRRNo ROA
2401:af80:c400::/40JPIRRNo ROA

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.