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
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% |
| 43.242.114.0/23 | No ROA | Nonecovered by 43.242.112.0/22 | 673 100% |
| 103.38.24.0/23 | No ROA | Nonecovered by 103.38.24.0/22 | 673 100% |
| 103.38.26.0/23 | No ROA | Nonecovered by 103.38.24.0/22 | 673 100% |
| 211.35.64.0/21 | No ROA | Other origin onlycovered by 211.35.64.0/20 | 673 100% |
| 202.136.112.0/21 | No ROA | Nonecovered by 202.136.112.0/20 | 672 100% |
| 202.136.120.0/21 | No ROA | Nonecovered by 202.136.112.0/20 | 672 100% |
| 211.35.72.0/21 | No ROA | Nonecovered by 211.35.64.0/20 | 672 100% |
| 202.136.121.0/24 | No ROA | Other origin onlycovered by 202.136.112.0/20 | 671 100% |
| 38.226.64.0/19 | No ROA | Other IRR onlyRADB | 673 100% |
| 119.42.160.0/20 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 119.42.176.0/20 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 202.167.208.0/21 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 202.167.216.0/21 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 221.133.48.0/21 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 221.133.56.0/21 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 221.133.61.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.38.26.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 202.167.209.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 211.35.74.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 221.133.54.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 221.133.63.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 43.231.204.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 104.251.56.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 43.242.112.0/23 | No ROA covers it. Add a ROA for AS9712, maxLength 23. |
| Route object: none | 43.242.112.0/23 | No 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. |
| ROA: none | 43.242.114.0/23 | No ROA covers it. Add a ROA for AS9712, maxLength 23. |
| Route object: none | 43.242.114.0/23 | No 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. |
| ROA: none | 103.38.24.0/23 | No ROA covers it. Add a ROA for AS9712, maxLength 23. |
| Route object: none | 103.38.24.0/23 | No 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. |
| ROA: none | 103.38.26.0/23 | No ROA covers it. Add a ROA for AS9712, maxLength 23. |
| Route object: none | 103.38.26.0/23 | No 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. |
| ROA: none | 211.35.64.0/21 | No ROA covers it. Add a ROA for AS9712, maxLength 21. |
| Route object: none | 211.35.64.0/21 | Route 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. |
| ROA: none | 202.136.112.0/21 | No ROA covers it. Add a ROA for AS9712, maxLength 21. |
| Route object: none | 202.136.112.0/21 | No 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. |
| ROA: none | 202.136.120.0/21 | No ROA covers it. Add a ROA for AS9712, maxLength 21. |
| Route object: none | 202.136.120.0/21 | No 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. |
| ROA: none | 211.35.72.0/21 | No ROA covers it. Add a ROA for AS9712, maxLength 21. |
| Route object: none | 211.35.72.0/21 | No 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. |
| ROA: none | 202.136.121.0/24 | No ROA covers it. Add a ROA for AS9712, maxLength 24. |
| Route object: none | 202.136.121.0/24 | Route 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. |
| ROA: none | 38.226.64.0/19 | No ROA covers it. Add a ROA for AS9712, maxLength 19. |
| Route object: RIR | 38.226.64.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 119.42.160.0/20 | No ROA covers it. Add a ROA for AS9712, maxLength 20. |
| Route object: RIR | 119.42.160.0/20 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 119.42.176.0/20 | No ROA covers it. Add a ROA for AS9712, maxLength 20. |
| Route object: RIR | 119.42.176.0/20 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 202.167.208.0/21 | No ROA covers it. Add a ROA for AS9712, maxLength 21. |
| Route object: RIR | 202.167.208.0/21 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 202.167.216.0/21 | No ROA covers it. Add a ROA for AS9712, maxLength 21. |
| Route object: RIR | 202.167.216.0/21 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 221.133.48.0/21 | No ROA covers it. Add a ROA for AS9712, maxLength 21. |
| Route object: RIR | 221.133.48.0/21 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 221.133.56.0/21 | No ROA covers it. Add a ROA for AS9712, maxLength 21. |
| Route object: RIR | 221.133.56.0/21 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 221.133.61.0/24 | No ROA covers it. Add a ROA for AS9712, maxLength 24. |
| Route object: RIR | 221.133.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.38.26.0/24 | No ROA covers it. Add a ROA for AS9712, maxLength 24. |
| Route object: RIR | 103.38.26.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.167.209.0/24 | No ROA covers it. Add a ROA for AS9712, maxLength 24. |
| Route object: RIR | 202.167.209.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.35.74.0/23 | No ROA covers it. Add a ROA for AS9712, maxLength 23. |
| Route object: RIR | 211.35.74.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 221.133.54.0/24 | No ROA covers it. Add a ROA for AS9712, maxLength 24. |
| Route object: RIR | 221.133.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 221.133.63.0/24 | No ROA covers it. Add a ROA for AS9712, maxLength 24. |
| Route object: RIR | 221.133.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
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/24 | RADB | No ROA |
| 43.242.112.0/22 | RADB | No ROA |
| 103.38.24.0/22 | RADB | No ROA |
| 103.38.27.0/24 | RADB | No ROA |
| 119.42.160.0/19 | RADB | No ROA |
| 119.42.190.0/24 | NTTCOM | No ROA |
| 119.42.191.0/24 | RADB | No ROA |
| 121.78.142.0/23 | RADB | No ROA |
| 202.136.112.0/20 | NTTCOM, RADB | No ROA |
| 202.136.112.0/23 | RADB | No ROA |
| 202.136.122.0/24 | NTTCOM | No ROA |
| 202.136.127.0/24 | NTTCOM | No ROA |
| 202.167.208.0/20 | RADB | No ROA |
| 202.167.223.0/24 | RADB | No ROA |
| 211.35.64.0/20 | NTTCOM, RADB | No ROA |
| 211.35.64.0/24 | RADB | No ROA |
| 211.35.70.0/23 | NTTCOM | No ROA |
| 211.35.72.0/24 | NTTCOM | No ROA |
| 221.133.48.0/20 | RADB | No 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.