bgpreport

Network · data from 2026-11-12

AS152202 NCHQ-AS-KR-KR - NCIDS

Registry name: NCHQ-AS-KR-KR - NCIDS, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152202, 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.
115.88.112.0/24 No ROA None 33 5%low visibility 26
210.94.136.0/24 No ROA None 33 5%low visibility 26
210.120.55.0/24 No ROA None 33 5%low visibility 26
210.182.89.0/24 No ROA None 33 5%low visibility 26
103.150.62.0/23 No ROA Other IRR onlyRADB 672 100% 67
160.250.154.0/23 No ROA Other IRR onlyRADB 672 100% 67
211.189.163.0/24 No ROA Other IRR onlyRADB 672 100% 67
211.189.165.0/24 No ROA Other IRR onlyRADB 672 100% 67
211.189.167.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS152202 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 18 are in fix.csv.

  • ROA: none9
  • Route object: none4
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none115.88.112.0/24No ROA covers it. Add a ROA for AS152202, maxLength 24.33 of 673
Route object: none115.88.112.0/24No route object for it. Add a route object with origin AS152202 in the RIR database for the space.33 of 673
ROA: none210.94.136.0/24No ROA covers it. Add a ROA for AS152202, maxLength 24.33 of 673
Route object: none210.94.136.0/24No route object for it. Add a route object with origin AS152202 in the RIR database for the space.33 of 673
ROA: none210.120.55.0/24No ROA covers it. Add a ROA for AS152202, maxLength 24.33 of 673
Route object: none210.120.55.0/24No route object for it. Add a route object with origin AS152202 in the RIR database for the space.33 of 673
ROA: none210.182.89.0/24No ROA covers it. Add a ROA for AS152202, maxLength 24.33 of 673
Route object: none210.182.89.0/24No route object for it. Add a route object with origin AS152202 in the RIR database for the space.33 of 673
ROA: none103.150.62.0/23No ROA covers it. Add a ROA for AS152202, maxLength 23.672 of 673
Route object: RIR103.150.62.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none160.250.154.0/23No ROA covers it. Add a ROA for AS152202, maxLength 23.672 of 673
Route object: RIR160.250.154.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.189.163.0/24No ROA covers it. Add a ROA for AS152202, maxLength 24.672 of 673
Route object: RIR211.189.163.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.189.165.0/24No ROA covers it. Add a ROA for AS152202, maxLength 24.672 of 673
Route object: RIR211.189.165.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.189.167.0/24No ROA covers it. Add a ROA for AS152202, maxLength 24.672 of 673
Route object: RIR211.189.167.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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