bgpreport

Network · data from 2026-11-12

AS9712 KPIN-AS-KR-KR - INet Technologies Co., Ltd.

Registry name: KPIN-AS-KR-KR - INet Technologies Co., Ltd., KR · not in PeeringDB

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

Announced routes

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

43.242.112.0/23 No ROA Nonecovered by 43.242.112.0/22 673 100% 67
43.242.114.0/23 No ROA Nonecovered by 43.242.112.0/22 673 100% 67
103.38.24.0/23 No ROA Nonecovered by 103.38.24.0/22 673 100% 67
103.38.26.0/23 No ROA Nonecovered by 103.38.24.0/22 673 100% 67
211.35.64.0/21 No ROA Other origin onlycovered by 211.35.64.0/20 673 100% 67
202.136.112.0/21 No ROA Nonecovered by 202.136.112.0/20 672 100% 67
202.136.120.0/21 No ROA Nonecovered by 202.136.112.0/20 672 100% 67
211.35.72.0/21 No ROA Nonecovered by 211.35.64.0/20 672 100% 67
202.136.121.0/24 No ROA Other origin onlycovered by 202.136.112.0/20 671 100% 67
38.226.64.0/19 No ROA Other IRR onlyRADB 673 100% 67
119.42.160.0/20 No ROA Other IRR onlyNTTCOM 673 100% 67
119.42.176.0/20 No ROA Other IRR onlyNTTCOM 673 100% 67
202.167.208.0/21 No ROA Other IRR onlyNTTCOM 673 100% 67
202.167.216.0/21 No ROA Other IRR onlyNTTCOM 673 100% 67
221.133.48.0/21 No ROA Other IRR onlyNTTCOM 673 100% 67
221.133.56.0/21 No ROA Other IRR onlyNTTCOM 673 100% 67
221.133.61.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.38.26.0/24 No ROA Other IRR onlyRADB 671 100% 67
202.167.209.0/24 No ROA Other IRR onlyRADB 671 100% 67
211.35.74.0/23 No ROA Other IRR onlyRADB 671 100% 67
221.133.54.0/24 No ROA Other IRR onlyRADB 671 100% 67
221.133.63.0/24 No ROA Other IRR onlyRADB 671 100% 67
43.231.204.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
104.251.56.0/21 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS9712 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 63 are in fix.csv.

  • ROA: none22
  • Route object: none9
  • Route object: RIR13
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none43.242.112.0/23No ROA covers it. Add a ROA for AS9712, maxLength 23.673 of 673
Route object: none43.242.112.0/23No route object for it. A route object for 43.242.112.0/22 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.673 of 673
ROA: none43.242.114.0/23No ROA covers it. Add a ROA for AS9712, maxLength 23.673 of 673
Route object: none43.242.114.0/23No route object for it. A route object for 43.242.112.0/22 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.673 of 673
ROA: none103.38.24.0/23No ROA covers it. Add a ROA for AS9712, maxLength 23.673 of 673
Route object: none103.38.24.0/23No route object for it. A route object for 103.38.24.0/22 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.673 of 673
ROA: none103.38.26.0/23No ROA covers it. Add a ROA for AS9712, maxLength 23.673 of 673
Route object: none103.38.26.0/23No route object for it. A route object for 103.38.24.0/22 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.673 of 673
ROA: none211.35.64.0/21No ROA covers it. Add a ROA for AS9712, maxLength 21.673 of 673
Route object: none211.35.64.0/21Route objects for it name AS9694. A route object for 211.35.64.0/20 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.673 of 673
ROA: none202.136.112.0/21No ROA covers it. Add a ROA for AS9712, maxLength 21.672 of 673
Route object: none202.136.112.0/21No route object for it. A route object for 202.136.112.0/20 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.672 of 673
ROA: none202.136.120.0/21No ROA covers it. Add a ROA for AS9712, maxLength 21.672 of 673
Route object: none202.136.120.0/21No route object for it. A route object for 202.136.112.0/20 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.672 of 673
ROA: none211.35.72.0/21No ROA covers it. Add a ROA for AS9712, maxLength 21.672 of 673
Route object: none211.35.72.0/21No route object for it. A route object for 211.35.64.0/20 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.672 of 673
ROA: none202.136.121.0/24No ROA covers it. Add a ROA for AS9712, maxLength 24.671 of 673
Route object: none202.136.121.0/24Route objects for it name AS45996. A route object for 202.136.112.0/20 with origin AS9712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9712 in the RIR database for the space.671 of 673
ROA: none38.226.64.0/19No ROA covers it. Add a ROA for AS9712, maxLength 19.673 of 673
Route object: RIR38.226.64.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none119.42.160.0/20No ROA covers it. Add a ROA for AS9712, maxLength 20.673 of 673
Route object: RIR119.42.160.0/20Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none119.42.176.0/20No ROA covers it. Add a ROA for AS9712, maxLength 20.673 of 673
Route object: RIR119.42.176.0/20Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none202.167.208.0/21No ROA covers it. Add a ROA for AS9712, maxLength 21.673 of 673
Route object: RIR202.167.208.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none202.167.216.0/21No ROA covers it. Add a ROA for AS9712, maxLength 21.673 of 673
Route object: RIR202.167.216.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none221.133.48.0/21No ROA covers it. Add a ROA for AS9712, maxLength 21.673 of 673
Route object: RIR221.133.48.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none221.133.56.0/21No ROA covers it. Add a ROA for AS9712, maxLength 21.673 of 673
Route object: RIR221.133.56.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none221.133.61.0/24No ROA covers it. Add a ROA for AS9712, maxLength 24.672 of 673
Route object: RIR221.133.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.38.26.0/24No ROA covers it. Add a ROA for AS9712, maxLength 24.671 of 673
Route object: RIR103.38.26.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.167.209.0/24No ROA covers it. Add a ROA for AS9712, maxLength 24.671 of 673
Route object: RIR202.167.209.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none211.35.74.0/23No ROA covers it. Add a ROA for AS9712, maxLength 23.671 of 673
Route object: RIR211.35.74.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none221.133.54.0/24No ROA covers it. Add a ROA for AS9712, maxLength 24.671 of 673
Route object: RIR221.133.54.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none221.133.63.0/24No ROA covers it. Add a ROA for AS9712, maxLength 24.671 of 673
Route object: RIR221.133.63.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

38.210.62.0/24RADBNo ROA
43.242.112.0/22RADBNo ROA
103.38.24.0/22RADBNo ROA
103.38.27.0/24RADBNo ROA
119.42.160.0/19RADBNo ROA
119.42.190.0/24NTTCOMNo ROA
119.42.191.0/24RADBNo ROA
121.78.142.0/23RADBNo ROA
202.136.112.0/20NTTCOM, RADBNo ROA
202.136.112.0/23RADBNo ROA
202.136.122.0/24NTTCOMNo ROA
202.136.127.0/24NTTCOMNo ROA
202.167.208.0/20RADBNo ROA
202.167.223.0/24RADBNo ROA
211.35.64.0/20NTTCOM, RADBNo ROA
211.35.64.0/24RADBNo ROA
211.35.70.0/23NTTCOMNo ROA
211.35.72.0/24NTTCOMNo ROA
221.133.48.0/20RADBNo 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.