Network · data from 2026-11-12
AS17764 HKMU-AS-AP - Hong Kong Metropolitan University
Registry name: HKMU-AS-AP - Hong Kong Metropolitan University, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17764, 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.
| 175.159.216.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 202.125.232.0/21 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.125.234.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.159.216.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 175.159.220.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 192.207.91.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.40.157.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.40.219.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.40.220.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.40.222.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS17764 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 47 are in fix.csv.
- ROA: none10
- Route object: RIR10
- Route object: not announced27
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 175.159.216.0/21 | No ROA covers it. Add a ROA for AS17764, maxLength 21. |
| Route object: RIR | 175.159.216.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.125.232.0/21 | No ROA covers it. Add a ROA for AS17764, maxLength 21. |
| Route object: RIR | 202.125.232.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.125.234.0/24 | No ROA covers it. Add a ROA for AS17764, maxLength 24. |
| Route object: RIR | 202.125.234.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 175.159.216.0/22 | No ROA covers it. Add a ROA for AS17764, maxLength 22. |
| Route object: RIR | 175.159.216.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 175.159.220.0/22 | No ROA covers it. Add a ROA for AS17764, maxLength 22. |
| Route object: RIR | 175.159.220.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 192.207.91.0/24 | No ROA covers it. Add a ROA for AS17764, maxLength 24. |
| Route object: RIR | 192.207.91.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.40.157.0/24 | No ROA covers it. Add a ROA for AS17764, maxLength 24. |
| Route object: RIR | 202.40.157.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.40.219.0/24 | No ROA covers it. Add a ROA for AS17764, maxLength 24. |
| Route object: RIR | 202.40.219.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.40.220.0/24 | No ROA covers it. Add a ROA for AS17764, maxLength 24. |
| Route object: RIR | 202.40.220.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.40.222.0/23 | No ROA covers it. Add a ROA for AS17764, maxLength 23. |
| Route object: RIR | 202.40.222.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17764 whose prefix no peer sees AS17764 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 175.159.216.0/23 | NTTCOM, RADB | No ROA |
| 175.159.216.0/24 | NTTCOM, RADB | No ROA |
| 175.159.217.0/24 | NTTCOM, RADB | No ROA |
| 175.159.218.0/23 | NTTCOM, RADB | No ROA |
| 175.159.218.0/24 | NTTCOM, RADB | No ROA |
| 175.159.219.0/24 | NTTCOM, RADB | No ROA |
| 175.159.220.0/23 | NTTCOM, RADB | No ROA |
| 175.159.220.0/24 | NTTCOM, RADB | No ROA |
| 175.159.221.0/24 | NTTCOM, RADB | No ROA |
| 175.159.222.0/23 | NTTCOM, RADB | No ROA |
| 175.159.222.0/24 | NTTCOM, RADB | No ROA |
| 175.159.223.0/24 | NTTCOM, RADB | No ROA |
| 202.40.222.0/24 | NTTCOM, RADB | No ROA |
| 202.40.223.0/24 | NTTCOM, RADB | No ROA |
| 202.125.232.0/22 | NTTCOM, RADB | No ROA |
| 202.125.232.0/23 | NTTCOM, RADB | No ROA |
| 202.125.232.0/24 | NTTCOM, RADB | No ROA |
| 202.125.233.0/24 | NTTCOM, RADB | No ROA |
| 202.125.234.0/23 | NTTCOM, RADB | No ROA |
| 202.125.235.0/24 | NTTCOM, RADB | No ROA |
| 202.125.236.0/22 | NTTCOM, RADB | No ROA |
| 202.125.236.0/23 | NTTCOM, RADB | No ROA |
| 202.125.236.0/24 | NTTCOM, RADB | No ROA |
| 202.125.237.0/24 | NTTCOM, RADB | No ROA |
| 202.125.238.0/23 | NTTCOM, RADB | No ROA |
| 202.125.238.0/24 | NTTCOM, RADB | No ROA |
| 202.125.239.0/24 | NTTCOM, 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.