bgpreport

Network · data from 2026-11-12

AS38112 HUGC-AS-KR-KR - Korea Housing Urban Guarantee Corporation

Registry name: HUGC-AS-KR-KR - Korea Housing Urban Guarantee Corporation, KR · not in PeeringDB

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

Announced routes

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

221.151.172.0/24 No ROA None 673 100% 67
211.54.148.224/28 No ROA None 13 2%low visibility 13
211.210.99.0/29 No ROA Nonecovered by 211.210.99.0/24 10 1%low visibility 10
1.252.186.0/24 No ROA Other IRR onlyRADB 673 100% 66
39.113.249.32/27 No ROA Other IRR onlyRADB 14 2%low visibility 13

AS-SET

AS38112 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 37 are in fix.csv.

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: none221.151.172.0/24No ROA covers it. Add a ROA for AS38112, maxLength 24.673 of 673
Route object: none221.151.172.0/24No route object for it. Add a route object with origin AS38112 in the RIR database for the space.673 of 673
ROA: none211.54.148.224/28No ROA covers it. Add a ROA for AS38112, maxLength 28.13 of 673
Route object: none211.54.148.224/28No route object for it. Add a route object with origin AS38112 in the RIR database for the space.13 of 673
ROA: none211.210.99.0/29No ROA covers it. Add a ROA for AS38112, maxLength 29.10 of 673
Route object: none211.210.99.0/29No route object for it. A route object for 211.210.99.0/24 with origin AS38112 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38112 in the RIR database for the space.10 of 673
ROA: none1.252.186.0/24No ROA covers it. Add a ROA for AS38112, maxLength 24.673 of 673
Route object: RIR1.252.186.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none39.113.249.32/27No ROA covers it. Add a ROA for AS38112, maxLength 27.14 of 673
Route object: RIR39.113.249.32/27Route object only in RADB. Add it in the RIR database for the space.14 of 673

Route objects not announced

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

58.143.212.0/22RADBNo ROA
58.143.216.0/21RADBNo ROA
58.143.224.0/20RADBNo ROA
58.143.240.0/23RADBNo ROA
118.176.0.0/21RADBNo ROA
118.176.146.0/23RADBNo ROA
118.176.162.0/23RADBNo ROA
118.176.164.0/23RADBNo ROA
120.142.0.0/23RADBNo ROA
120.142.2.0/23RADBNo ROA
120.142.4.0/22RADBNo ROA
120.142.8.0/22RADBNo ROA
120.142.44.0/22RADBNo ROA
120.142.64.0/22RADBNo ROA
120.142.84.0/22RADBNo ROA
120.142.120.0/21RADBNo ROA
120.142.136.0/22RADBNo ROA
120.142.228.0/22RADBNo ROA
120.142.240.0/23RADBNo ROA
120.142.244.0/23RADBNo ROA
120.142.254.0/23RADBNo ROA
121.174.157.0/24RADBNo ROA
124.5.192.0/21RADBNo ROA
211.33.137.0/24RADBNo ROA
211.63.171.0/24RADBNo ROA
211.210.99.0/24RADBNo ROA
211.236.18.0/24RADBNo 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.