bgpreport

Network · data from 2026-11-12

AS134764 CT-FoShan-IDC - CHINANET Guangdong province network

Registry name: CT-FoShan-IDC - CHINANET Guangdong province network, CN · not in PeeringDB

18IPv4 routes 55.6% RPKI valid · 83.3% with a route object
6IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
107Route objects not announced registered with origin AS134764, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134764, 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.

103.73.204.0/22 No ROA Other IRR onlyRADB 672 100% 67
120.31.66.0/24 No ROA Other IRR onlyRADB 672 100% 67
120.31.67.0/24 No ROA Other IRR onlyRADB 672 100% 67
120.31.68.0/23 No ROA Other IRR onlyRADB 672 100% 67
120.31.70.0/23 No ROA Other IRR onlyRADB 672 100% 67
120.31.128.0/21 No ROA Other IRR onlyRADB 672 100% 67
120.31.136.0/21 No ROA Other IRR onlyRADB 672 100% 67
160.22.188.0/24 No ROA Other IRR onlyRADB 672 100% 67
160.19.208.0/24 Valid Nonecovered by 160.19.208.0/22 672 100% 67
160.19.209.0/24 Valid Nonecovered by 160.19.208.0/22 672 100% 67
160.19.210.0/24 Valid Nonecovered by 160.19.208.0/22 672 100% 67
58.67.156.0/23 Valid Other IRR onlyRADB 672 100% 67
124.172.128.0/20 Valid Other IRR onlyRADB 672 100% 67
124.172.144.0/20 Valid Other IRR onlyRADB 672 100% 67
124.173.96.0/19 Valid Other IRR onlyRADB 672 100% 67
240e:1f:d000::/36 Valid Other IRR onlyRADB 636 100% 68
240e:ff:a000::/36 Valid Other IRR onlyRADB 636 100% 68
240e:108:11e1::/48 Valid Other IRR onlyRADB 636 100% 68
240e:97d:2000::/36 Valid Other IRR onlyRADB 636 100% 68
240e:982:e100::/40 Valid Other IRR onlyRADB 636 100% 68
240e:983:1e01::/48 Valid Other IRR onlyRADB 636 100% 68
43.255.212.0/22 Valid Other IRR onlyRADB 598 89% 67
103.228.160.0/22 Valid Other IRR onlyRADB 598 89% 67
139.5.60.0/22 Valid Other IRR onlyRADB 598 89% 67

AS-SET

AS134764 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 139 are in fix.csv.

  • ROA: none8
  • Route object: none3
  • Route object: RIR21
  • Route object: not announced107
ChangePrefix or setDetailFull-table peers
ROA: none103.73.204.0/22No ROA covers it. Add a ROA for AS134764, maxLength 22.672 of 673
Route object: RIR103.73.204.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none120.31.66.0/24No ROA covers it. Add a ROA for AS134764, maxLength 24.672 of 673
Route object: RIR120.31.66.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none120.31.67.0/24No ROA covers it. Add a ROA for AS134764, maxLength 24.672 of 673
Route object: RIR120.31.67.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none120.31.68.0/23No ROA covers it. Add a ROA for AS134764, maxLength 23.672 of 673
Route object: RIR120.31.68.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none120.31.70.0/23No ROA covers it. Add a ROA for AS134764, maxLength 23.672 of 673
Route object: RIR120.31.70.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none120.31.128.0/21No ROA covers it. Add a ROA for AS134764, maxLength 21.672 of 673
Route object: RIR120.31.128.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none120.31.136.0/21No ROA covers it. Add a ROA for AS134764, maxLength 21.672 of 673
Route object: RIR120.31.136.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none160.22.188.0/24No ROA covers it. Add a ROA for AS134764, maxLength 24.672 of 673
Route object: RIR160.22.188.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none160.19.208.0/24No route object for it. A route object for 160.19.208.0/22 with origin AS134764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134764 in the RIR database for the space.672 of 673
Route object: none160.19.209.0/24No route object for it. A route object for 160.19.208.0/22 with origin AS134764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134764 in the RIR database for the space.672 of 673
Route object: none160.19.210.0/24No route object for it. A route object for 160.19.208.0/22 with origin AS134764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134764 in the RIR database for the space.672 of 673
Route object: RIR58.67.156.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.172.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.172.144.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.173.96.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR240e:1f:d000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:ff:a000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:108:11e1::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:97d:2000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:982:e100::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:983:1e01::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR43.255.212.0/22Route object only in RADB. Add it in the RIR database for the space.598 of 673
Route object: RIR103.228.160.0/22Route object only in RADB. Add it in the RIR database for the space.598 of 673
Route object: RIR139.5.60.0/22Route object only in RADB. Add it in the RIR database for the space.598 of 673

Route objects not announced

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

14.17.96.0/22RADBNo ROA
14.17.100.0/22RADBNo ROA
14.17.104.0/21RADBNo ROA
14.17.112.0/23RADBNo ROA
14.22.16.0/22RADBNo ROA
14.29.32.0/19RADBNo ROA
14.119.64.0/20RADBNo ROA
14.119.80.0/21RADBNo ROA
14.149.72.0/22RADBNo ROA
14.152.32.0/19RADBNo ROA
43.254.128.0/22RADBNo ROA
45.65.28.0/22RADBNo ROA
61.142.132.0/23RADBNo ROA
61.142.166.0/24RADBNo ROA
61.142.175.0/24RADBNo ROA
61.142.176.0/24RADBNo ROA
61.142.208.0/24RADBNo ROA
61.142.250.0/24RADBNo ROA
61.142.253.0/24RADBNo ROA
61.142.254.0/24RADBNo ROA
61.146.72.0/23RADBNo ROA
103.223.108.0/22RADBNo ROA
103.249.12.0/22RADBNo ROA
116.31.96.0/19RADBNo ROA
119.145.130.0/23RADBNo ROA
119.145.138.0/23RADBNo ROA
119.145.144.0/22RADBNo ROA
119.145.148.0/23RADBNo ROA
119.145.151.0/24RADBNo ROA
119.147.136.0/21RADBNo ROA
121.9.13.0/24APNIC, RADBValid
121.9.100.0/24APNIC, RADBValid
121.9.201.0/24APNIC, RADBValid
121.9.202.0/23APNIC, RADBValid
121.9.204.0/22APNIC, RADBValid
121.9.208.0/22APNIC, RADBValid
121.9.212.0/23APNIC, RADBValid
121.9.214.0/24APNIC, RADBValid
121.9.219.0/24APNIC, RADBValid
121.9.220.0/22APNIC, RADBValid
121.9.227.0/24APNIC, RADBValid
121.9.228.0/23APNIC, RADBValid
121.9.232.0/24APNIC, RADBValid
121.9.234.0/23APNIC, RADBValid
121.9.238.0/23APNIC, RADBValid
121.9.240.0/22APNIC, RADBValid
121.9.244.0/23APNIC, RADBValid
121.9.246.0/24APNIC, RADBValid
121.9.247.0/24APNIC, RADBValid
121.11.32.0/19APNIC, RADBValid
121.32.240.0/21APNIC, RADBValid
121.32.248.0/21APNIC, RADBValid
121.46.0.0/23RADBValid
121.46.2.0/23RADBValid
121.46.4.0/23RADBValid
121.46.6.0/23RADBValid
121.46.8.0/23RADBValid
121.46.10.0/23RADBValid
125.88.144.0/20APNIC, RADBValid
125.88.176.0/20APNIC, RADBValid
125.94.64.0/18RADBNo ROA
125.94.144.0/21RADBNo ROA
125.94.224.0/19RADBNo ROA
160.19.208.0/22RADBNo ROA
183.2.208.0/23RADBNo ROA
183.2.210.0/24RADBNo ROA
183.2.212.0/23RADBNo ROA
183.2.214.0/23RADBNo ROA
183.2.216.0/21RADBNo ROA
183.2.232.0/22RADBNo ROA
183.3.202.0/23RADBNo ROA
183.3.204.0/22RADBNo ROA
183.6.203.0/24RADBNo ROA
183.6.204.0/22RADBNo ROA
183.6.208.0/20RADBNo ROA
183.47.200.0/21RADBNo ROA
183.47.224.0/21RADBNo ROA
183.47.236.0/22RADBNo ROA
183.47.240.0/23RADBNo ROA
183.56.96.0/24RADBNo ROA
183.56.172.0/22RADBNo ROA
183.57.144.0/21RADBNo ROA
183.57.152.0/22RADBNo ROA
183.60.106.0/23RADBNo ROA
183.60.108.0/22RADBNo ROA
183.60.192.0/20RADBNo ROA
183.60.206.0/24RADBNo ROA
183.60.208.0/23RADBNo ROA
183.60.210.0/23RADBNo ROA
183.60.212.0/24RADBNo ROA
183.60.213.0/24RADBNo ROA
183.60.214.0/23RADBNo ROA
183.60.216.0/24RADBNo ROA
183.60.217.0/24RADBNo ROA
183.60.218.0/23RADBNo ROA
183.60.220.0/22RADBNo ROA
183.60.232.0/22RADBNo ROA
183.61.88.0/21RADBNo ROA
183.61.146.0/23RADBNo ROA
183.61.148.0/22RADBNo ROA
202.103.160.0/24APNIC, RADBValid
202.104.19.0/24APNIC, RADBValid
202.105.13.0/24APNIC, RADBValid
202.105.19.0/24APNIC, RADBValid
202.105.21.0/24APNIC, RADBValid
2406:fe80::/32RADBNo ROA
240e:ff:c01e::/48RADBNo 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.