Network · data from 2026-11-12
AS9775 HANNAM-AS-KR - Hannam University
Registry name: HANNAM-AS-KR - Hannam University, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9775, 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.
| 59.26.221.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 59.26.222.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 59.26.223.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 202.30.54.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.241.32.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.247.32.0/19 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.247.212.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 210.125.104.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 210.125.105.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 210.125.106.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
AS-SET
AS9775 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 22 are in fix.csv.
- ROA: none10
- Route object: RIR10
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 59.26.221.0/24 | No ROA covers it. Add a ROA for AS9775, maxLength 24. |
| Route object: RIR | 59.26.221.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 59.26.222.0/24 | No ROA covers it. Add a ROA for AS9775, maxLength 24. |
| Route object: RIR | 59.26.222.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 59.26.223.0/24 | No ROA covers it. Add a ROA for AS9775, maxLength 24. |
| Route object: RIR | 59.26.223.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 202.30.54.0/24 | No ROA covers it. Add a ROA for AS9775, maxLength 24. |
| Route object: RIR | 202.30.54.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.241.32.0/21 | No ROA covers it. Add a ROA for AS9775, maxLength 21. |
| Route object: RIR | 203.241.32.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.247.32.0/19 | No ROA covers it. Add a ROA for AS9775, maxLength 19. |
| Route object: RIR | 203.247.32.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.247.212.0/22 | No ROA covers it. Add a ROA for AS9775, maxLength 22. |
| Route object: RIR | 203.247.212.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.125.104.0/24 | No ROA covers it. Add a ROA for AS9775, maxLength 24. |
| Route object: RIR | 210.125.104.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 210.125.105.0/24 | No ROA covers it. Add a ROA for AS9775, maxLength 24. |
| Route object: RIR | 210.125.105.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 210.125.106.0/24 | No ROA covers it. Add a ROA for AS9775, maxLength 24. |
| Route object: RIR | 210.125.106.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9775 whose prefix no peer sees AS9775 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 59.26.222.0/23 | RADB | No ROA |
| 210.125.104.0/23 | 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.