Network · data from 2026-11-12
AS135110 HKLINKINFINITY-AS-AP - HONGKONG LINK INFINITY TECHNOLOGY LIMITED
Registry name: HKLINKINFINITY-AS-AP - HONGKONG LINK INFINITY TECHNOLOGY LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135110, 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.113.60.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.239.102.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 157.119.21.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
AS135110 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 11 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.113.60.0/24 | No ROA covers it. Add a ROA for AS135110, maxLength 24. |
| Route object: RIR | 103.113.60.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135110 whose prefix no peer sees AS135110 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.113.60.0/22 | RADB | No ROA |
| 103.113.62.0/23 | RADB | No ROA |
| 103.113.62.0/24 | RADB | No ROA |
| 103.113.63.0/24 | RADB | No ROA |
| 103.172.53.0/24 | RADB | No ROA |
| 154.84.15.0/24 | RADB | No ROA |
| 154.214.2.0/23 | RADB | No ROA |
| 202.57.208.0/22 | RADB | No ROA |
| 203.176.128.0/20 | 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.