bgpreport

Network · data from 2026-11-12

AS18330 HONGIK-AS-KR-KR - HONGIK UNIVERSITY

Registry name: HONGIK-AS-KR-KR - HONGIK UNIVERSITY, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18330, 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.
203.249.64.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.249.80.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
220.95.128.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
220.95.144.0/21 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
223.194.54.0/23 No ROA Other IRR onlyRADB 672 100% 67
223.194.61.0/24 No ROA Other IRR onlyRADB 672 100% 67
223.194.64.0/19 No ROA Other IRR onlyRADB 672 100% 67
223.194.109.0/24 No ROA Other IRR onlyRADB 672 100% 67
223.194.110.0/23 No ROA Other IRR onlyRADB 672 100% 67
223.194.228.0/23 No ROA Other IRR onlyRADB 672 100% 67
223.195.94.0/23 No ROA Other IRR onlyRADB 672 100% 67
223.195.126.0/23 No ROA Other IRR onlyRADB 672 100% 67
223.195.147.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS18330 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 41 are in fix.csv.

  • ROA: none13
  • Route object: RIR13
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none203.249.64.0/20No ROA covers it. Add a ROA for AS18330, maxLength 20.673 of 673
Route object: RIR203.249.64.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.249.80.0/22No ROA covers it. Add a ROA for AS18330, maxLength 22.673 of 673
Route object: RIR203.249.80.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.95.128.0/20No ROA covers it. Add a ROA for AS18330, maxLength 20.673 of 673
Route object: RIR220.95.128.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.95.144.0/21No ROA covers it. Add a ROA for AS18330, maxLength 21.673 of 673
Route object: RIR220.95.144.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none223.194.54.0/23No ROA covers it. Add a ROA for AS18330, maxLength 23.672 of 673
Route object: RIR223.194.54.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none223.194.61.0/24No ROA covers it. Add a ROA for AS18330, maxLength 24.672 of 673
Route object: RIR223.194.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none223.194.64.0/19No ROA covers it. Add a ROA for AS18330, maxLength 19.672 of 673
Route object: RIR223.194.64.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none223.194.109.0/24No ROA covers it. Add a ROA for AS18330, maxLength 24.672 of 673
Route object: RIR223.194.109.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none223.194.110.0/23No ROA covers it. Add a ROA for AS18330, maxLength 23.672 of 673
Route object: RIR223.194.110.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none223.194.228.0/23No ROA covers it. Add a ROA for AS18330, maxLength 23.672 of 673
Route object: RIR223.194.228.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none223.195.94.0/23No ROA covers it. Add a ROA for AS18330, maxLength 23.672 of 673
Route object: RIR223.195.94.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none223.195.126.0/23No ROA covers it. Add a ROA for AS18330, maxLength 23.672 of 673
Route object: RIR223.195.126.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none223.195.147.0/24No ROA covers it. Add a ROA for AS18330, maxLength 24.672 of 673
Route object: RIR223.195.147.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

116.122.48.0/21NTTCOM, RADBNo ROA
116.122.56.0/22NTTCOM, RADBNo ROA
180.92.240.0/20NTTCOM, RADBNo ROA
203.249.124.0/23RADBNo ROA
210.93.82.0/24RADBNo ROA
210.119.176.0/24RADBNo ROA
211.42.108.0/22RADBNo ROA
211.42.112.0/24RADBNo ROA
211.42.113.0/24RADBNo ROA
211.42.115.0/24RADBNo ROA
220.73.77.0/24RADBNo ROA
220.73.78.0/23RADBNo ROA
223.194.96.0/21RADBNo ROA
223.194.104.0/22RADBNo ROA
223.194.108.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.