Network · data from 2026-11-12
AS140316 CHINATELECOM-GUANGDONG-CHAOZHOU-5G-NETWORK - CHINATELECOM Guangdong province Chaozhou 5G network
Registry name: CHINATELECOM-GUANGDONG-CHAOZHOU-5G-NETWORK - CHINATELECOM Guangdong province Chaozhou 5G network, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140316, 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.228.0/24 | Valid | None | 3 0%low visibility |
| 240e:108:404f::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:108:484f::/48 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
AS140316 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 70 are in fix.csv.
- Route object: none1
- Route object: RIR2
- Route object: not announced67
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 218.15.228.0/24 | No route object for it. Add a route object with origin AS140316 in the RIR database for the space. |
| Route object: RIR | 240e:108:404f::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:108:484f::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140316 whose prefix no peer sees AS140316 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 14.18.128.0/21 | RADB | No ROA |
| 14.21.62.0/24 | RADB | No ROA |
| 14.29.73.0/24 | RADB | No ROA |
| 14.118.0.0/17 | RADB | No ROA |
| 14.121.128.0/20 | RADB | No ROA |
| 14.121.192.0/18 | RADB | No ROA |
| 14.148.120.0/21 | RADB | No ROA |
| 61.143.208.0/23 | RADB | No ROA |
| 61.143.212.0/22 | RADB | No ROA |
| 61.143.216.0/22 | RADB | No ROA |
| 61.143.223.0/24 | RADB | No ROA |
| 61.143.226.0/23 | RADB | No ROA |
| 61.143.228.0/23 | RADB | No ROA |
| 61.146.208.0/21 | RADB | No ROA |
| 61.146.216.0/22 | RADB | No ROA |
| 61.146.220.0/23 | RADB | No ROA |
| 61.146.222.0/24 | RADB | No ROA |
| 113.85.128.0/20 | RADB | No ROA |
| 113.85.144.0/20 | RADB | No ROA |
| 113.85.160.0/20 | RADB | No ROA |
| 113.85.176.0/20 | RADB | No ROA |
| 113.85.192.0/18 | RADB | No ROA |
| 113.95.128.0/19 | RADB | No ROA |
| 113.95.160.0/19 | RADB | No ROA |
| 113.95.192.0/20 | RADB | No ROA |
| 113.95.208.0/20 | RADB | No ROA |
| 113.95.224.0/19 | RADB | No ROA |
| 116.19.30.0/23 | RADB | No ROA |
| 116.19.141.0/24 | RADB | No ROA |
| 116.19.160.0/21 | RADB | No ROA |
| 116.19.168.0/21 | RADB | No ROA |
| 116.19.176.0/20 | RADB | No ROA |
| 116.19.192.0/18 | RADB | No ROA |
| 119.121.212.0/22 | RADB | No ROA |
| 119.125.136.0/21 | RADB | No ROA |
| 119.125.144.0/21 | RADB | No ROA |
| 119.125.152.0/21 | RADB | No ROA |
| 119.125.160.0/20 | RADB | No ROA |
| 119.125.176.0/20 | RADB | No ROA |
| 119.125.192.0/19 | RADB | No ROA |
| 119.125.224.0/20 | RADB | No ROA |
| 119.125.240.0/20 | RADB | No ROA |
| 119.140.240.0/22 | RADB | No ROA |
| 119.146.96.0/22 | RADB | No ROA |
| 125.90.172.0/22 | RADB | No ROA |
| 125.90.176.0/20 | RADB | No ROA |
| 125.90.198.0/23 | RADB | No ROA |
| 125.90.200.0/22 | RADB | No ROA |
| 125.90.208.0/20 | RADB | No ROA |
| 125.90.224.0/19 | RADB | No ROA |
| 183.18.128.0/19 | RADB | No ROA |
| 183.18.160.0/20 | RADB | No ROA |
| 183.19.0.0/18 | RADB | No ROA |
| 183.19.64.0/19 | RADB | No ROA |
| 183.19.96.0/19 | RADB | No ROA |
| 183.19.128.0/17 | RADB | No ROA |
| 183.50.128.0/19 | RADB | No ROA |
| 183.50.160.0/19 | RADB | No ROA |
| 183.57.185.0/24 | RADB | No ROA |
| 183.59.20.0/23 | RADB | No ROA |
| 183.59.31.0/24 | RADB | No ROA |
| 183.59.220.0/22 | RADB | No ROA |
| 202.104.208.0/22 | RADB | No ROA |
| 202.105.230.0/23 | RADB | No ROA |
| 240e:1e:7000::/36 | RADB | No ROA |
| 240e:ff:c013::/48 | RADB | No ROA |
| 240e:7b6:b000::/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.