bgpreport

Network · data from 2026-11-12

AS140312 CHINATELECOM-GUANGDONG-ZHANJIANG-5G-NETWORK - CHINATELECOM Guangdong province Zhanjiang 5G network

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140312, 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.14.246.0/24 Valid None 3 0%low visibility 4
240e:108:404e::/48 Valid Other IRR onlyRADB 636 100% 68
240e:108:484e::/48 Valid Other IRR onlyRADB 636 100% 68
219.129.33.0/24 Valid Other IRR onlyRADB 3 0%low visibility 4

AS-SET

AS140312 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 79 are in fix.csv.

  • Route object: none1
  • Route object: RIR3
  • Route object: not announced75
ChangePrefix or setDetailFull-table peers
Route object: none218.14.246.0/24No route object for it. Add a route object with origin AS140312 in the RIR database for the space.3 of 673
Route object: RIR240e:108:404e::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:108:484e::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR219.129.33.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

14.18.9.0/24RADBNo ROA
14.119.128.0/18RADBNo ROA
14.119.192.0/18RADBNo ROA
14.122.128.0/18RADBNo ROA
14.148.88.0/21RADBNo ROA
14.148.180.0/22RADBNo ROA
61.143.64.0/19RADBNo ROA
61.143.96.0/22RADBNo ROA
61.146.0.0/19RADBNo ROA
61.146.32.0/21RADBNo ROA
113.86.128.0/20RADBNo ROA
113.86.144.0/20RADBNo ROA
113.86.160.0/19RADBNo ROA
113.86.192.0/19RADBNo ROA
113.86.200.0/22RADBNo ROA
113.86.224.0/19RADBNo ROA
116.19.26.0/23RADBNo ROA
116.19.139.0/24RADBNo ROA
116.28.168.0/21RADBNo ROA
116.28.176.0/21RADBNo ROA
116.28.184.0/22RADBNo ROA
116.28.188.0/22RADBNo ROA
116.28.192.0/21RADBNo ROA
116.28.200.0/22RADBNo ROA
116.28.204.0/22RADBNo ROA
116.28.208.0/20RADBNo ROA
116.28.224.0/21RADBNo ROA
116.28.232.0/22RADBNo ROA
116.28.236.0/22RADBNo ROA
116.28.240.0/20RADBNo ROA
119.121.198.0/23RADBNo ROA
119.121.200.0/23RADBNo ROA
119.135.0.0/20RADBNo ROA
119.135.16.0/20RADBNo ROA
119.135.32.0/20RADBNo ROA
119.135.48.0/20RADBNo ROA
119.135.64.0/20RADBNo ROA
119.135.80.0/20RADBNo ROA
119.135.96.0/20RADBNo ROA
119.140.96.0/20RADBNo ROA
119.140.112.0/20RADBNo ROA
119.146.216.0/22RADBNo ROA
125.89.80.0/21RADBNo ROA
125.89.88.0/22RADBNo ROA
125.90.0.0/20RADBNo ROA
125.90.16.0/20RADBNo ROA
125.90.32.0/19RADBNo ROA
125.90.68.0/22RADBNo ROA
125.90.72.0/22RADBNo ROA
125.90.76.0/22RADBNo ROA
183.0.0.0/17RADBNo ROA
183.18.0.0/19RADBNo ROA
183.18.32.0/19RADBNo ROA
183.18.64.0/19RADBNo ROA
183.18.96.0/19RADBNo ROA
183.44.128.0/18RADBNo ROA
183.44.192.0/20RADBNo ROA
183.50.64.0/20RADBNo ROA
183.50.80.0/20RADBNo ROA
183.50.96.0/19RADBNo ROA
183.53.208.0/21RADBNo ROA
183.57.128.0/21RADBNo ROA
183.57.136.0/21RADBNo ROA
183.57.183.0/24RADBNo ROA
183.59.136.0/21RADBNo ROA
183.59.224.0/22RADBNo ROA
202.104.218.0/23RADBNo ROA
202.104.220.0/23RADBNo ROA
202.104.222.0/23RADBNo ROA
202.104.224.0/23RADBNo ROA
202.105.220.0/23RADBNo ROA
202.105.222.0/23RADBNo ROA
240e:1e:3000::/36RADBNo ROA
240e:ff:c012::/48RADBNo ROA
240e:7b6:9000::/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.