Network · data from 2026-11-12
AS142020 HFHYTC-AS-AP - HONGKONG FA HE YONG TECHNOLOGY
Registry name: HFHYTC-AS-AP - HONGKONG FA HE YONG TECHNOLOGY, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS142020, 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.
| 103.162.138.0/23 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.162.138.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.162.139.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
AS142020 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 4 are in fix.csv.
- ROA: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.162.138.0/23 | No ROA covers it. Add a ROA for AS142020, maxLength 23. |
| ROA: none | 103.162.138.0/24 | No ROA covers it. Add a ROA for AS142020, maxLength 24. |
| ROA: none | 103.162.139.0/24 | No ROA covers it. Add a ROA for AS142020, maxLength 24. |
Route objects not announced
Route objects with origin AS142020 whose prefix no peer sees AS142020 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df6:5680::/48 | APNIC, 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.