bgpreport

Network · data from 2026-11-12

AS140313 CHINATELECOM-GUANGDONG-ZHAOQING-5G-NETWORK - CHINATELECOM Guangdong province Zhaoqing 5G network

Registry name: CHINATELECOM-GUANGDONG-ZHAOQING-5G-NETWORK - CHINATELECOM Guangdong province Zhaoqing 5G network, CN · not in PeeringDB

0IPv4 routes
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
81Route objects not announced registered with origin AS140313, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS140313, 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:108:4055::/48 Valid Other IRR onlyRADB 636 100% 68
240e:108:4855::/48 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS140313 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 83 are in fix.csv.

  • Route object: RIR2
  • Route object: not announced81
ChangePrefix or setDetailFull-table peers
Route object: RIR240e:108:4055::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:108:4855::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Route objects with origin AS140313 whose prefix no peer sees AS140313 announce. Many are kept on purpose (backup routes, space announced only in some places).

14.21.12.0/22RADBNo ROA
14.21.72.0/22RADBNo ROA
14.148.96.0/21RADBNo ROA
14.149.192.0/18RADBNo ROA
14.152.0.0/19RADBNo ROA
61.143.230.0/23RADBNo ROA
61.143.232.0/21RADBNo ROA
61.146.224.0/20RADBNo ROA
113.64.192.0/20RADBNo ROA
113.64.228.0/23RADBNo ROA
113.64.250.0/24RADBNo ROA
113.94.0.0/20RADBNo ROA
113.94.16.0/20RADBNo ROA
113.94.32.0/20RADBNo ROA
113.94.48.0/20RADBNo ROA
113.94.64.0/19RADBNo ROA
113.94.96.0/19RADBNo ROA
116.19.28.0/23RADBNo ROA
116.19.140.0/24RADBNo ROA
116.27.0.0/20RADBNo ROA
116.27.16.0/21RADBNo ROA
116.27.24.0/21RADBNo ROA
116.27.32.0/20RADBNo ROA
116.27.48.0/21RADBNo ROA
116.27.56.0/21RADBNo ROA
116.27.64.0/19RADBNo ROA
116.31.76.0/22RADBNo ROA
119.121.202.0/23RADBNo ROA
119.121.204.0/23RADBNo ROA
119.134.0.0/21RADBNo ROA
119.134.8.0/21RADBNo ROA
119.134.16.0/20RADBNo ROA
119.134.32.0/19RADBNo ROA
119.134.64.0/20RADBNo ROA
119.134.80.0/22RADBNo ROA
119.134.84.0/22RADBNo ROA
119.134.88.0/21RADBNo ROA
119.134.96.0/21RADBNo ROA
119.134.104.0/21RADBNo ROA
119.134.112.0/20RADBNo ROA
119.139.0.0/21RADBNo ROA
119.146.112.0/23RADBNo ROA
119.146.114.0/23RADBNo ROA
119.146.116.0/22RADBNo ROA
125.90.80.0/22RADBNo ROA
125.90.84.0/22RADBNo ROA
125.90.89.0/24RADBNo ROA
125.90.90.0/23RADBNo ROA
125.90.92.0/24RADBNo ROA
125.90.94.0/23RADBNo ROA
125.90.96.0/21RADBNo ROA
183.0.128.0/17RADBNo ROA
183.2.0.0/18RADBNo ROA
183.20.96.0/19RADBNo ROA
183.21.0.0/18RADBNo ROA
183.21.64.0/19RADBNo ROA
183.21.96.0/19RADBNo ROA
183.44.64.0/18RADBNo ROA
183.51.0.0/20RADBNo ROA
183.51.16.0/20RADBNo ROA
183.51.176.0/20RADBNo ROA
183.57.32.0/22RADBNo ROA
183.57.156.0/22RADBNo ROA
183.57.184.0/24RADBNo ROA
183.58.120.0/22RADBNo ROA
183.59.22.0/24RADBNo ROA
183.59.23.0/24RADBNo ROA
183.59.236.0/24RADBNo ROA
183.59.237.0/24RADBNo ROA
183.59.238.0/24RADBNo ROA
183.59.239.0/24RADBNo ROA
183.63.44.0/22RADBNo ROA
202.104.216.0/23RADBNo ROA
202.105.6.0/24RADBNo ROA
202.105.234.0/23RADBNo ROA
202.105.236.0/23RADBNo ROA
240e:1e:4000::/36RADBNo ROA
240e:ff:c014::/48RADBNo ROA
240e:7b2::/36RADBNo ROA
240e:7b2:3000::/36RADBNo ROA
240e:7b7:2000::/36RADBNo 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.