Network · data from 2026-11-12
AS140315 CHINATELECOM-GUANGDONG-JIEYANG-5G-NETWORK - CHINATELECOM Guangdong province Jieyang 5G network
Registry name: CHINATELECOM-GUANGDONG-JIEYANG-5G-NETWORK - CHINATELECOM Guangdong province Jieyang 5G network, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140315, 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.
| 218.15.136.0/24 | Valid | None | 3 0%low visibility |
| 240e:108:4056::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:108:4856::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 61.143.134.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
AS-SET
AS140315 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 68 are in fix.csv.
- Route object: none1
- Route object: RIR3
- Route object: not announced64
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 218.15.136.0/24 | No route object for it. Add a route object with origin AS140315 in the RIR database for the space. |
| Route object: RIR | 240e:108:4056::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:108:4856::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.143.134.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140315 whose prefix no peer sees AS140315 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 14.21.29.0/24 | RADB | No ROA |
| 14.21.60.0/23 | RADB | No ROA |
| 14.21.84.0/22 | RADB | No ROA |
| 14.121.144.0/20 | RADB | No ROA |
| 14.148.112.0/21 | RADB | No ROA |
| 14.159.128.0/17 | RADB | No ROA |
| 61.143.128.0/21 | RADB | No ROA |
| 61.146.74.0/23 | RADB | No ROA |
| 61.146.76.0/22 | RADB | No ROA |
| 61.146.80.0/21 | RADB | No ROA |
| 61.146.88.0/22 | RADB | No ROA |
| 113.64.249.0/24 | RADB | No ROA |
| 113.94.128.0/20 | RADB | No ROA |
| 113.94.144.0/20 | RADB | No ROA |
| 113.94.160.0/19 | RADB | No ROA |
| 113.94.192.0/18 | RADB | No ROA |
| 116.19.32.0/23 | RADB | No ROA |
| 116.19.142.0/24 | RADB | No ROA |
| 116.29.0.0/20 | RADB | No ROA |
| 116.29.16.0/21 | RADB | No ROA |
| 116.29.24.0/21 | RADB | No ROA |
| 116.29.32.0/20 | RADB | No ROA |
| 116.29.48.0/21 | RADB | No ROA |
| 116.29.56.0/21 | RADB | No ROA |
| 116.29.64.0/20 | RADB | No ROA |
| 116.29.80.0/21 | RADB | No ROA |
| 116.29.88.0/21 | RADB | No ROA |
| 119.121.209.0/24 | RADB | No ROA |
| 119.121.210.0/23 | RADB | No ROA |
| 119.132.208.0/21 | RADB | No ROA |
| 119.132.216.0/21 | RADB | No ROA |
| 119.132.224.0/20 | RADB | No ROA |
| 119.132.248.0/21 | RADB | No ROA |
| 119.146.164.0/22 | RADB | No ROA |
| 125.90.104.0/21 | RADB | No ROA |
| 125.90.112.0/20 | RADB | No ROA |
| 125.90.128.0/21 | RADB | No ROA |
| 183.20.64.0/19 | RADB | No ROA |
| 183.20.128.0/18 | RADB | No ROA |
| 183.20.192.0/19 | RADB | No ROA |
| 183.20.224.0/19 | RADB | No ROA |
| 183.22.0.0/17 | RADB | No ROA |
| 183.47.0.0/24 | RADB | No ROA |
| 183.50.224.0/19 | RADB | No ROA |
| 183.51.32.0/19 | RADB | No ROA |
| 183.57.88.0/21 | RADB | No ROA |
| 183.57.96.0/21 | RADB | No ROA |
| 183.57.104.0/21 | RADB | No ROA |
| 183.57.186.0/24 | RADB | No ROA |
| 183.59.28.0/24 | RADB | No ROA |
| 183.59.29.0/24 | RADB | No ROA |
| 183.59.76.0/23 | RADB | No ROA |
| 183.59.228.0/24 | RADB | No ROA |
| 183.59.229.0/24 | RADB | No ROA |
| 183.59.230.0/24 | RADB | No ROA |
| 183.59.231.0/24 | RADB | No ROA |
| 183.62.184.0/21 | RADB | No ROA |
| 202.104.212.0/22 | RADB | No ROA |
| 202.105.216.0/22 | RADB | No ROA |
| 240e:1e:5000::/36 | RADB | No ROA |
| 240e:ff:c015::/48 | RADB | No ROA |
| 240e:7b3::/36 | RADB | No ROA |
| 240e:7b3:3000::/36 | RADB | No ROA |
| 240e:7b7:3000::/36 | 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.