Network · data from 2026-11-12

AS9634 SHNS-AS-KR - Shinhan Securities Co.,Ltd.

Registry name: SHNS-AS-KR - Shinhan Securities Co.,Ltd., KR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No 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 AS9634, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9634, 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.


128.134.154.0/24	No ROA	Other IRR onlyNTTCOM, RADB	673 100%	66
175.120.58.0/24	No ROA	Other IRR onlyRADB	673 100%	66
210.123.80.0/24	No ROA	Other IRR onlyNTTCOM, RADB	673 100%	66
210.183.214.0/24	No ROA	Other IRR onlyRADB	673 100%	66

AS-SET

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

ROA: none4
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
ROA: none	128.134.154.0/24	No ROA covers it. Add a ROA for AS9634, maxLength 24.	673 of 673
Route object: RIR	128.134.154.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	175.120.58.0/24	No ROA covers it. Add a ROA for AS9634, maxLength 24.	673 of 673
Route object: RIR	175.120.58.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	210.123.80.0/24	No ROA covers it. Add a ROA for AS9634, maxLength 24.	673 of 673
Route object: RIR	210.123.80.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	210.183.214.0/24	No ROA covers it. Add a ROA for AS9634, maxLength 24.	673 of 673
Route object: RIR	210.183.214.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

128.134.154.0/24

No ROA covers it. Add a ROA for AS9634, maxLength 24.

673 of 673

Route object: RIR

128.134.154.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

175.120.58.0/24

No ROA covers it. Add a ROA for AS9634, maxLength 24.

673 of 673

Route object: RIR

175.120.58.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

210.123.80.0/24

No ROA covers it. Add a ROA for AS9634, maxLength 24.

673 of 673

Route object: RIR

210.123.80.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

210.183.214.0/24

No ROA covers it. Add a ROA for AS9634, maxLength 24.

673 of 673

Route object: RIR

210.183.214.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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