bgpreport

Network · data from 2026-11-12

AS17592 IBK-AS-KR-KR - Industrial Bank of Korea

Registry name: IBK-AS-KR-KR - Industrial Bank of Korea, KR · not in PeeringDB

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

Announced routes

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

112.170.14.128/27 No ROA None 14 2%low visibility 13
61.253.111.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
203.227.232.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.235.67.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.235.68.0/24 No ROA Other IRR onlyRADB 672 100% 66
203.235.72.0/24 No ROA Other IRR onlyRADB 670 100% 67
114.52.78.0/24 No ROA Other IRR onlyRADB 669 99% 67

AS-SET

AS17592 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 16 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none112.170.14.128/27No ROA covers it. Add a ROA for AS17592, maxLength 27.14 of 673
Route object: none112.170.14.128/27No route object for it. Add a route object with origin AS17592 in the RIR database for the space.14 of 673
ROA: none61.253.111.0/24No ROA covers it. Add a ROA for AS17592, maxLength 24.673 of 673
Route object: RIR61.253.111.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none203.227.232.0/24No ROA covers it. Add a ROA for AS17592, maxLength 24.673 of 673
Route object: RIR203.227.232.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.235.67.0/24No ROA covers it. Add a ROA for AS17592, maxLength 24.673 of 673
Route object: RIR203.235.67.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.235.68.0/24No ROA covers it. Add a ROA for AS17592, maxLength 24.672 of 673
Route object: RIR203.235.68.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.235.72.0/24No ROA covers it. Add a ROA for AS17592, maxLength 24.670 of 673
Route object: RIR203.235.72.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none114.52.78.0/24No ROA covers it. Add a ROA for AS17592, maxLength 24.669 of 673
Route object: RIR114.52.78.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

203.235.70.0/24RADBNo ROA
211.110.82.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.