Network · data from 2026-11-12
AS10127 CLSA-AS-AP - CLSA Ltd
Registry name: CLSA-AS-AP - CLSA Ltd, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10127, 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.
| 202.124.28.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 202.124.31.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.124.29.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 202.124.30.0/24 | Valid | Other IRR onlyRADB | 670 100% |
AS-SET
AS10127 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 18 are in fix.csv.
- Route object: RIR4
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 202.124.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.124.31.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.124.29.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.124.30.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10127 whose prefix no peer sees AS10127 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 20.134.64.0/20 | REACH | No ROA |
| 20.139.12.0/22 | REACH | No ROA |
| 20.139.16.0/20 | REACH | No ROA |
| 20.139.32.0/20 | REACH | No ROA |
| 20.139.48.0/20 | REACH | No ROA |
| 20.139.64.0/20 | REACH | No ROA |
| 138.242.192.0/19 | REACH | Invalid: origin |
| 144.187.64.0/18 | REACH | No ROA |
| 192.88.167.0/24 | REACH | No ROA |
| 192.88.170.0/24 | REACH | No ROA |
| 202.64.124.0/24 | REACH | Invalid: origin |
| 202.64.184.0/24 | REACH | Invalid: origin |
| 202.124.28.0/22 | RADB, REACH | No ROA |
| 202.124.28.0/23 | 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.