bgpreport

Network · data from 2026-11-12

AS9755 RPKINET1-KR - Korea Internet Security Agency

Registry name: RPKINET1-KR - Korea Internet Security Agency, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9755, 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.30.120.0/24 No ROA None 671 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none202.30.120.0/24No ROA covers it. Add a ROA for AS9755, maxLength 24.671 of 673
Route object: none202.30.120.0/24No route object for it. Add a route object with origin AS9755 in the RIR database for the space.671 of 673

Route objects not announced

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

168.126.29.128/28RADBNo ROA
210.108.16.0/24RADBNo ROA
210.121.176.192/26RADBNo ROA
211.40.68.64/27RADBNo ROA
211.47.64.0/22RADBNo ROA
211.47.64.0/23RADBNo ROA
211.47.64.0/24NTTCOM, RADBNo ROA
211.47.65.0/24NTTCOM, RADBNo ROA
211.47.66.0/24NTTCOM, RADBNo ROA
211.47.67.0/24RADBNo ROA
211.47.68.0/24NTTCOMNo ROA
211.47.69.0/24NTTCOMNo ROA
211.47.70.0/24NTTCOMNo ROA
211.47.71.0/24NTTCOMNo ROA
211.47.72.0/24NTTCOMNo 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.