Network · data from 2026-11-12
AS140853 CHINATELECOM-JIANGXI-NANCHANG-5G-NETWORK - CHINATELECOM Jiangxi province Nanchang 5G network
Registry name: CHINATELECOM-JIANGXI-NANCHANG-5G-NETWORK - CHINATELECOM Jiangxi province Nanchang 5G network, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140853, 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.
| 240e:13:801::/48 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
AS140853 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 23 are in fix.csv.
- Route object: RIR1
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 240e:13:801::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140853 whose prefix no peer sees AS140853 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 59.53.40.0/21 | RADB | Valid |
| 59.53.136.0/21 | RADB | Valid |
| 106.4.172.0/22 | RADB | Valid |
| 106.4.252.0/22 | RADB | Valid |
| 106.5.164.0/22 | RADB | Valid |
| 106.228.0.0/17 | RADB | Valid |
| 111.76.40.0/21 | RADB | Valid |
| 111.76.200.0/21 | RADB | Valid |
| 111.78.104.0/21 | RADB | Valid |
| 115.148.168.0/21 | RADB | Valid |
| 115.152.80.0/21 | RADB | Valid |
| 115.153.8.0/21 | RADB | Valid |
| 117.40.100.0/22 | RADB | Valid |
| 117.43.120.0/21 | RADB | Valid |
| 117.43.184.0/21 | RADB | Valid |
| 182.85.172.0/22 | RADB | Valid |
| 182.85.184.0/22 | RADB | Valid |
| 182.85.192.0/22 | RADB | Valid |
| 182.87.88.0/21 | RADB | Valid |
| 182.96.144.0/21 | RADB | Valid |
| 182.96.232.0/21 | RADB | Valid |
| 220.175.80.0/20 | 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.