bgpreport

Network · data from 2026-11-12

AS38100 INICIS-AS-KR-KR - INICIS Co., Ltd

Registry name: INICIS-AS-KR-KR - INICIS Co., Ltd, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38100, 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.
210.101.91.40/29 No ROA None 10 1%low visibility 10
39.115.212.0/24 No ROA Other IRR onlyRADB 673 100% 66
183.109.71.0/24 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

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

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none210.101.91.40/29No ROA covers it. Add a ROA for AS38100, maxLength 29.10 of 673
Route object: none210.101.91.40/29No route object for it. Add a route object with origin AS38100 in the RIR database for the space.10 of 673
ROA: none39.115.212.0/24No ROA covers it. Add a ROA for AS38100, maxLength 24.673 of 673
Route object: RIR39.115.212.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none183.109.71.0/24No ROA covers it. Add a ROA for AS38100, maxLength 24.673 of 673
Route object: RIR183.109.71.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

124.137.75.0/24NTTCOMNo ROA
124.137.76.0/24NTTCOMNo ROA
124.137.77.0/24NTTCOMNo ROA
124.137.78.0/24NTTCOMNo ROA
124.137.79.0/24NTTCOMNo ROA
124.137.80.0/24NTTCOMNo ROA
124.137.81.0/24NTTCOMNo ROA
124.137.82.0/24NTTCOMNo ROA
124.137.83.0/24NTTCOMNo ROA
211.175.38.0/24RADBNo ROA
220.230.152.0/22RADBNo ROA
220.230.156.0/24RADBNo ROA
220.230.249.0/24RADBNo ROA
220.230.250.0/23RADBNo ROA
220.230.250.0/24RADBNo ROA
220.230.251.0/24RADBNo ROA
220.230.252.0/22RADBNo ROA
220.230.252.0/23RADBNo ROA
220.230.254.0/23RADBNo 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.