Network · data from 2026-11-12
AS9765 AS9765-13 - KRNIC-ASBLOCK-AP
Registry name: AS9765-13 - KRNIC-ASBLOCK-AP, KR · not in PeeringDB
8IPv4 routes
0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
8No ROA
8 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
24Route objects not announced
registered with origin AS9765, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS9765, 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.
| 111.66.192.0/22 | No ROA | Other origin onlycovered by 111.66.192.0/18 | 673 100% |
| 111.66.196.0/22 | No ROA | Nonecovered by 111.66.192.0/18 | 673 100% |
| 111.66.200.0/22 | No ROA | Nonecovered by 111.66.192.0/18 | 673 100% |
| 111.66.204.0/22 | No ROA | Other origin onlycovered by 111.66.192.0/18 | 673 100% |
| 111.66.208.0/22 | No ROA | Nonecovered by 111.66.192.0/18 | 673 100% |
| 111.66.212.0/22 | No ROA | Other origin onlycovered by 111.66.192.0/18 | 673 100% |
| 111.66.216.0/22 | No ROA | Nonecovered by 111.66.192.0/18 | 673 100% |
| 111.66.220.0/22 | No ROA | Nonecovered by 111.66.192.0/18 | 673 100% |
AS-SET
AS9765 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 40 are in fix.csv.
- ROA: none8
- Route object: none8
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 111.66.192.0/22 | No ROA covers it. Add a ROA for AS9765, maxLength 22. |
| Route object: none | 111.66.192.0/22 | Route objects for it name AS17718. A route object for 111.66.192.0/18 with origin AS9765 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9765 in the RIR database for the space. |
| ROA: none | 111.66.196.0/22 | No ROA covers it. Add a ROA for AS9765, maxLength 22. |
| Route object: none | 111.66.196.0/22 | No route object for it. A route object for 111.66.192.0/18 with origin AS9765 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9765 in the RIR database for the space. |
| ROA: none | 111.66.200.0/22 | No ROA covers it. Add a ROA for AS9765, maxLength 22. |
| Route object: none | 111.66.200.0/22 | No route object for it. A route object for 111.66.192.0/18 with origin AS9765 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9765 in the RIR database for the space. |
| ROA: none | 111.66.204.0/22 | No ROA covers it. Add a ROA for AS9765, maxLength 22. |
| Route object: none | 111.66.204.0/22 | Route objects for it name AS17718. A route object for 111.66.192.0/18 with origin AS9765 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9765 in the RIR database for the space. |
| ROA: none | 111.66.208.0/22 | No ROA covers it. Add a ROA for AS9765, maxLength 22. |
| Route object: none | 111.66.208.0/22 | No route object for it. A route object for 111.66.192.0/18 with origin AS9765 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9765 in the RIR database for the space. |
| ROA: none | 111.66.212.0/22 | No ROA covers it. Add a ROA for AS9765, maxLength 22. |
| Route object: none | 111.66.212.0/22 | Route objects for it name AS17718. A route object for 111.66.192.0/18 with origin AS9765 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9765 in the RIR database for the space. |
| ROA: none | 111.66.216.0/22 | No ROA covers it. Add a ROA for AS9765, maxLength 22. |
| Route object: none | 111.66.216.0/22 | No route object for it. A route object for 111.66.192.0/18 with origin AS9765 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9765 in the RIR database for the space. |
| ROA: none | 111.66.220.0/22 | No ROA covers it. Add a ROA for AS9765, maxLength 22. |
| Route object: none | 111.66.220.0/22 | No route object for it. A route object for 111.66.192.0/18 with origin AS9765 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9765 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9765 whose prefix no peer sees AS9765 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.138.192.0/18 | RADB | No ROA |
| 61.251.110.208/28 | NTTCOM | No ROA |
| 61.251.110.208/29 | NTTCOM | No ROA |
| 61.251.110.216/29 | NTTCOM | No ROA |
| 103.25.16.0/22 | RADB | No ROA |
| 111.66.192.0/18 | RADB | No ROA |
| 113.21.0.0/19 | RADB | No ROA |
| 114.110.128.0/17 | RADB | No ROA |
| 161.248.110.0/23 | RADB | No ROA |
| 161.248.112.0/23 | RADB | No ROA |
| 175.107.64.0/18 | RADB | No ROA |
| 182.255.128.0/17 | RADB | No ROA |
| 202.163.128.0/19 | RADB | No ROA |
| 210.97.224.0/20 | RADB | No ROA |
| 210.107.28.0/24 | RADB | No ROA |
| 210.112.16.0/20 | RADB | No ROA |
| 210.112.48.0/20 | RADB | No ROA |
| 210.112.90.0/23 | RADB | No ROA |
| 210.112.92.0/22 | RADB | No ROA |
| 211.111.192.0/20 | RADB | No ROA |
| 211.116.27.0/24 | RADB | No ROA |
| 211.116.182.0/23 | RADB | No ROA |
| 211.116.184.0/21 | RADB | No ROA |
| 211.236.236.0/22 | 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.