Network · data from 2026-11-12
AS139184 CCDC-CN - China Central Depository & Clearing Co., Ltd.
Registry name: CCDC-CN - China Central Depository & Clearing Co., Ltd., CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139184, 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.
| 163.128.254.0/23 | No ROA | None | 60 9%low visibility |
| 2402:5920::/48 | No ROA | None | 45 7%low visibility |
AS-SET
AS139184 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: none2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 163.128.254.0/23 | No ROA covers it. Add a ROA for AS139184, maxLength 23. |
| Route object: none | 163.128.254.0/23 | No route object for it. Add a route object with origin AS139184 in the RIR database for the space. |
| ROA: none | 2402:5920::/48 | No ROA covers it. Add a ROA for AS139184, maxLength 48. |
| Route object: none | 2402:5920::/48 | No route object for it. Add a route object with origin AS139184 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS139184 is announced.
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.