Network · data from 2026-11-12
AS140366 CHINATELECOM-HUNAN-HENGYANG-5G-NETWORK - CHINATELECOM Hunan province Hengyang 5G network
Registry name: CHINATELECOM-HUNAN-HENGYANG-5G-NETWORK - CHINATELECOM Hunan province Hengyang 5G network, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140366, 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:96b:6006::/48 | Valid | None | 636 100% |
| 240e:96b:6007::/48 | Valid | None | 636 100% |
| 240e:96b:6008::/48 | Valid | None | 636 100% |
AS-SET
AS140366 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 3 are in fix.csv.
- Route object: none3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 240e:96b:6006::/48 | No route object for it. Add a route object with origin AS140366 in the RIR database for the space. |
| Route object: none | 240e:96b:6007::/48 | No route object for it. Add a route object with origin AS140366 in the RIR database for the space. |
| Route object: none | 240e:96b:6008::/48 | No route object for it. Add a route object with origin AS140366 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS140366 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.