Network · data from 2026-11-12
AS141750 HCJBTC-AS-AP - PC Cloud
Registry name: HCJBTC-AS-AP - PC Cloud, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141750, 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.
| 217.216.137.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 77.216.24.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 77.216.26.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 79.182.67.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 89.31.211.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.47.119.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 191.44.98.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 204.10.163.0/24 | Valid | RIR databaseARIN | 673 100% |
| 217.216.179.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 77.246.222.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS141750 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 5 are in fix.csv.
- Route object: RIR4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 217.216.137.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 77.216.24.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 77.216.26.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 79.182.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS141750 whose prefix no peer sees AS141750 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 163.53.16.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.