Network · data from 2026-11-12
AS24334 Cyberport Hong Kong
Registry name: CYBERPORT-HK-AP - Cyberport Hong Kong, HK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24334, 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.
| 2404:1a0:1005::/48 | Invalid: maxLength | Nonecovered by 2404:1a0::/32 | 4 1%low visibility |
| 2404:1a0:ffff::/48 | Invalid: maxLength | Nonecovered by 2404:1a0::/32 | 4 1%low visibility |
| 103.11.88.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.83.240.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.171.208.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.142.88.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.11.89.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.11.88.0/22 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.11.90.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.11.91.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.83.240.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.83.241.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.83.242.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.83.243.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.83.244.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.83.245.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.83.246.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.83.247.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.171.208.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.171.209.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.171.210.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.171.211.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.171.212.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.171.213.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.171.214.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.171.215.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.142.89.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.142.90.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.142.91.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.142.92.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.142.93.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.142.95.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.142.94.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 2404:1a0::/30 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 635 100% |
| 2404:1a0:2008::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2404:1a3::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2404:1a0::/32 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 634 100% |
| 2404:1a0:1002::/48 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 634 100% |
| 2404:1a1::/32 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 634 100% |
| 2404:1a2::/32 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 634 100% |
| 203.142.88.0/24 | Valid | RIR databaseAPNIC, RADB | 172 26% |
AS-SET
AS24334's PeeringDB record names no 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 8 are in fix.csv.
- ROA: maxLength2
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2404:1a0:1005::/48 | ROA 2404:1a0::/30 AS24334 has maxLength 30; ROA 2404:1a0::/32 AS24334 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2404:1a0:1005::/48. |
| Route object: none | 2404:1a0:1005::/48 | No route object for it. A route object for 2404:1a0::/32 with origin AS24334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24334 in the RIR database for the space. |
| ROA: maxLength | 2404:1a0:ffff::/48 | ROA 2404:1a0::/30 AS24334 has maxLength 30; ROA 2404:1a0::/32 AS24334 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2404:1a0:ffff::/48. |
| Route object: none | 2404:1a0:ffff::/48 | No route object for it. A route object for 2404:1a0::/32 with origin AS24334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24334 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24334 whose prefix no peer sees AS24334 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.142.88.0/22 | APNIC | Invalid: maxLength |
| 2404:1a0:1000::/46 | APNIC, RADB | Valid |
| 2404:1a0:1000::/47 | APNIC, RADB | Valid |
| 2404:1a0:1001::/48 | 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.