Network · data from 2026-11-12
AS140485 CHINATELECOM-ZHEJIANG-HANGZHOU-5GC-NETWORK - CHINATELECOM ZHEJIANG province HANGZHOU 5GC network
Registry name: CHINATELECOM-ZHEJIANG-HANGZHOU-5GC-NETWORK - CHINATELECOM ZHEJIANG province HANGZHOU 5GC network, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140485, 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.
| 60.163.64.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 115.220.64.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 115.233.185.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 183.137.0.0/17 | Valid | Other IRR onlyRADB | 672 100% |
| 36.21.0.0/17 | Valid | Other IRR onlyRADB | 671 100% |
| 36.28.0.0/17 | Valid | Other IRR onlyRADB | 671 100% |
| 240e:1c7:10::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:473::/32 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:473:ddff::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:473:eeee::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:473:ff00::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:473:ffff::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:870::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:870:80::/46 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:871::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:473:eeec::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 240e:473:eeed::/48 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS140485 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 17 are in fix.csv.
- Route object: RIR17
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 60.163.64.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.220.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.233.185.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.137.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 36.21.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 36.28.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:1c7:10::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:473::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:473:ddff::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:473:eeee::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:473:ff00::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:473:ffff::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:870::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:870:80::/46 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:871::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:473:eeec::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:473:eeed::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS140485 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.