Network · data from 2026-11-12
AS17794 HTCL-ORANGE-HK-AP - Hutchison Telephone Company Limited
Registry name: HTCL-ORANGE-HK-AP - Hutchison Telephone Company Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17794, 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.
| 203.145.73.0/24 | Valid | Other origin only | 671 100% |
| 203.145.71.0/24 | Valid | Other origin only | 670 100% |
| 203.145.72.0/24 | Valid | Other origin only | 670 100% |
| 203.145.76.0/24 | Valid | Other origin only | 670 100% |
| 203.145.77.0/24 | Valid | Other origin only | 670 100% |
| 203.145.82.0/24 | Valid | Other origin only | 670 100% |
| 202.45.88.0/24 | Valid | None | 647 96% |
| 203.145.74.0/24 | Valid | Other origin only | 647 96% |
| 203.145.78.0/24 | Valid | Other origin only | 647 96% |
| 103.247.92.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 103.247.94.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 202.45.82.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 202.45.85.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
AS-SET
AS17794 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 19 are in fix.csv.
- Route object: none9
- Route object: RIR4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 203.145.73.0/24 | Route objects for it name AS10118. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: none | 203.145.71.0/24 | Route objects for it name AS10116. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: none | 203.145.72.0/24 | Route objects for it name AS10118. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: none | 203.145.76.0/24 | Route objects for it name AS10118. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: none | 203.145.77.0/24 | Route objects for it name AS10118. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: none | 203.145.82.0/24 | Route objects for it name AS10118. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: none | 202.45.88.0/24 | No route object for it. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: none | 203.145.74.0/24 | Route objects for it name AS10118. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: none | 203.145.78.0/24 | Route objects for it name AS10118. Add a route object with origin AS17794 in the RIR database for the space. |
| Route object: RIR | 103.247.92.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.247.94.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.45.82.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.45.85.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 AS17794 whose prefix no peer sees AS17794 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.247.92.0/22 | NTTCOM, RADB | No ROA |
| 103.247.92.0/23 | NTTCOM, RADB | No ROA |
| 103.247.93.0/24 | NTTCOM, RADB | No ROA |
| 103.247.94.0/23 | NTTCOM, RADB | No ROA |
| 103.247.95.0/24 | NTTCOM, RADB | No ROA |
| 203.184.147.0/24 | APNIC, RADB | Valid |
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.