bgpreport

Network · data from 2026-11-12

AS9761 ASIANA-AS-KR - ASIANAIDT

Registry name: ASIANA-AS-KR - ASIANAIDT, KR · not in PeeringDB

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

Announced routes

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

120.73.0.0/16 No ROA Other origin only 673 100% 67
165.141.0.0/16 No ROA None 673 100% 67
165.141.112.0/20 No ROA Other origin only 673 100% 67
165.141.160.0/20 No ROA None 673 100% 67
165.141.176.0/21 No ROA None 673 100% 67
165.141.128.0/19 No ROA None 672 100% 67
165.141.168.0/24 No ROA None 671 100% 67
120.73.118.0/24 No ROA Other IRR onlyRADB 673 100% 66
120.73.123.0/24 No ROA Other IRR onlyRADB 673 100% 66
120.73.124.0/24 No ROA Other IRR onlyRADB 673 100% 66
120.73.125.0/24 No ROA Other IRR onlyRADB 673 100% 66
120.73.126.0/24 No ROA Other IRR onlyRADB 673 100% 66
120.73.127.0/24 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS9761 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 107 are in fix.csv.

  • ROA: none13
  • Route object: none7
  • Route object: RIR6
  • Route object: not announced81
ChangePrefix or setDetailFull-table peers
ROA: none120.73.0.0/16No ROA covers it. Add a ROA for AS9761, maxLength 16.673 of 673
Route object: none120.73.0.0/16Route objects for it name AS3786. Add a route object with origin AS9761 in the RIR database for the space.673 of 673
ROA: none165.141.0.0/16No ROA covers it. Add a ROA for AS9761, maxLength 16.673 of 673
Route object: none165.141.0.0/16No route object for it. Add a route object with origin AS9761 in the RIR database for the space.673 of 673
ROA: none165.141.112.0/20No ROA covers it. Add a ROA for AS9761, maxLength 20.673 of 673
Route object: none165.141.112.0/20Route objects for it name AS4766. Add a route object with origin AS9761 in the RIR database for the space.673 of 673
ROA: none165.141.160.0/20No ROA covers it. Add a ROA for AS9761, maxLength 20.673 of 673
Route object: none165.141.160.0/20No route object for it. Add a route object with origin AS9761 in the RIR database for the space.673 of 673
ROA: none165.141.176.0/21No ROA covers it. Add a ROA for AS9761, maxLength 21.673 of 673
Route object: none165.141.176.0/21No route object for it. Add a route object with origin AS9761 in the RIR database for the space.673 of 673
ROA: none165.141.128.0/19No ROA covers it. Add a ROA for AS9761, maxLength 19.672 of 673
Route object: none165.141.128.0/19No route object for it. Add a route object with origin AS9761 in the RIR database for the space.672 of 673
ROA: none165.141.168.0/24No ROA covers it. Add a ROA for AS9761, maxLength 24.671 of 673
Route object: none165.141.168.0/24No route object for it. Add a route object with origin AS9761 in the RIR database for the space.671 of 673
ROA: none120.73.118.0/24No ROA covers it. Add a ROA for AS9761, maxLength 24.673 of 673
Route object: RIR120.73.118.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none120.73.123.0/24No ROA covers it. Add a ROA for AS9761, maxLength 24.673 of 673
Route object: RIR120.73.123.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none120.73.124.0/24No ROA covers it. Add a ROA for AS9761, maxLength 24.673 of 673
Route object: RIR120.73.124.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none120.73.125.0/24No ROA covers it. Add a ROA for AS9761, maxLength 24.673 of 673
Route object: RIR120.73.125.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none120.73.126.0/24No ROA covers it. Add a ROA for AS9761, maxLength 24.673 of 673
Route object: RIR120.73.126.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none120.73.127.0/24No ROA covers it. Add a ROA for AS9761, maxLength 24.673 of 673
Route object: RIR120.73.127.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

120.73.122.0/24RADBNo ROA
123.141.238.0/23RADBNo ROA
165.141.0.0/19RADBNo ROA
165.141.0.0/20RADBNo ROA
165.141.8.0/24RADBNo ROA
165.141.16.0/20RADBNo ROA
165.141.16.0/21RADBNo ROA
165.141.24.0/22RADBNo ROA
165.141.28.0/23RADBNo ROA
165.141.30.0/24RADBNo ROA
165.141.96.0/20RADBNo ROA
165.141.96.0/21RADBNo ROA
165.141.104.0/21RADBNo ROA
165.141.111.0/24RADBNo ROA
165.141.176.0/23RADBNo ROA
165.141.176.0/24RADBNo ROA
165.141.178.0/24RADBNo ROA
165.141.179.0/24RADBNo ROA
165.141.184.0/22RADBNo ROA
165.141.184.0/24RADBNo ROA
165.141.185.0/24RADBNo ROA
165.141.186.0/24RADBNo ROA
165.141.195.0/24RADBNo ROA
165.141.196.0/24RADBNo ROA
165.141.197.0/24RADBNo ROA
165.141.200.0/21RADBNo ROA
165.141.200.0/23RADBNo ROA
165.141.201.0/24RADBNo ROA
165.141.202.0/23RADBNo ROA
165.141.202.0/24RADBNo ROA
165.141.203.0/24RADBNo ROA
165.141.204.0/23RADBNo ROA
165.141.204.0/24RADBNo ROA
165.141.205.0/24RADBNo ROA
165.141.206.0/24RADBNo ROA
165.141.207.0/24RADBNo ROA
165.141.208.0/20RADBNo ROA
165.141.208.0/22RADBNo ROA
165.141.210.0/24RADBNo ROA
165.141.211.0/24RADBNo ROA
165.141.212.0/22RADBNo ROA
165.141.212.0/24RADBNo ROA
165.141.213.0/24RADBNo ROA
165.141.214.0/24RADBNo ROA
165.141.215.0/24RADBNo ROA
165.141.216.0/24RADBNo ROA
165.141.217.0/24RADBNo ROA
165.141.218.0/24RADBNo ROA
165.141.219.0/24RADBNo ROA
165.141.220.0/24RADBNo ROA
165.141.221.0/24RADBNo ROA
165.141.222.0/24RADBNo ROA
165.141.223.0/24RADBNo ROA
165.141.224.0/22RADBNo ROA
165.141.227.0/24RADBNo ROA
165.141.228.0/23RADBNo ROA
165.141.233.0/24RADBNo ROA
165.141.236.0/24RADBNo ROA
165.141.238.0/23RADBNo ROA
165.141.238.0/24RADBNo ROA
165.141.239.0/24RADBNo ROA
165.141.240.0/22RADBNo ROA
165.141.240.0/24RADBNo ROA
165.141.241.0/24RADBNo ROA
165.141.242.0/24RADBNo ROA
165.141.243.0/24RADBNo ROA
165.141.244.0/24RADBNo ROA
165.141.245.0/24RADBNo ROA
165.141.246.0/23RADBNo ROA
165.141.246.0/24RADBNo ROA
165.141.247.0/24RADBNo ROA
165.141.248.0/24RADBNo ROA
165.141.249.0/24RADBNo ROA
165.141.250.0/24RADBNo ROA
168.126.60.0/23RADBNo ROA
203.248.168.0/24RADBNo ROA
203.248.169.0/24RADBNo ROA
203.248.170.0/24RADBNo ROA
203.248.171.0/24RADBNo ROA
203.248.172.0/24RADBNo ROA
203.248.173.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.