bgpreport

Network · data from 2026-11-12

AS58772 ChinaNet-Fujian-Fuzhou-IDC - CHINANET Fujian province Fuzhou IDC network

Registry name: ChinaNet-Fujian-Fuzhou-IDC - CHINANET Fujian province Fuzhou IDC network, CN · not in PeeringDB

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

Announced routes

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

110.80.144.0/23 Valid Nonecovered by 110.80.144.0/20 672 100% 67
110.80.157.0/24 Valid Nonecovered by 110.80.144.0/20 672 100% 67
240e:980:8530::/48 Valid None 636 100% 68
240e:964:5400::/46 Valid Nonecovered by 240e:964:5000::/37 635 100% 68
27.156.26.0/23 Valid Other IRR onlyRADB 672 100% 67
110.80.144.0/20 Valid Other IRR onlyRADB 672 100% 67
117.24.160.0/20 Valid Other IRR onlyRADB 672 100% 67
117.24.166.0/24 Valid Other IRR onlyRADB 672 100% 67
124.72.128.0/21 Valid Other IRR onlyRADB 672 100% 67
124.72.136.0/22 Valid Other IRR onlyRADB 672 100% 67
182.44.64.0/19 Valid Other IRR onlyRADB 672 100% 67
182.44.64.0/23 Valid Other IRR onlyRADB 672 100% 67
203.55.128.0/23 Valid Other IRR onlyRADB 672 100% 67
240e:108:1185::/48 Valid Other IRR onlyRADB 636 100% 68
240e:264:a000::/36 Valid Other IRR onlyRADB 636 100% 68
240e:964:5000::/37 Valid Other IRR onlyRADB 636 100% 68
240e:964:a800::/38 Valid Other IRR onlyRADB 636 100% 68
240e:964:d400::/39 Valid Other IRR onlyRADB 636 100% 68
240e:964:f400::/39 Valid Other IRR onlyRADB 636 100% 68
240e:965:5000::/37 Valid Other IRR onlyRADB 636 100% 68
240e:965:a800::/38 Valid Other IRR onlyRADB 636 100% 68
240e:965:d400::/39 Valid Other IRR onlyRADB 636 100% 68
240e:965:f400::/39 Valid Other IRR onlyRADB 636 100% 68
240e:966:5000::/37 Valid Other IRR onlyRADB 636 100% 68
240e:966:a800::/38 Valid Other IRR onlyRADB 636 100% 68
240e:966:d400::/39 Valid Other IRR onlyRADB 636 100% 68
240e:966:f400::/39 Valid Other IRR onlyRADB 636 100% 68
240e:967:5000::/37 Valid Other IRR onlyRADB 636 100% 68
240e:967:a800::/38 Valid Other IRR onlyRADB 636 100% 68
240e:967:d400::/39 Valid Other IRR onlyRADB 636 100% 68
240e:967:f400::/39 Valid Other IRR onlyRADB 636 100% 68
240e:982:8500::/40 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS58772 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 34 are in fix.csv.

  • Route object: none4
  • Route object: RIR28
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none110.80.144.0/23No route object for it. A route object for 110.80.144.0/20 with origin AS58772 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58772 in the RIR database for the space.672 of 673
Route object: none110.80.157.0/24No route object for it. A route object for 110.80.144.0/20 with origin AS58772 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58772 in the RIR database for the space.672 of 673
Route object: none240e:980:8530::/48No route object for it. Add a route object with origin AS58772 in the RIR database for the space.636 of 636
Route object: none240e:964:5400::/46No route object for it. A route object for 240e:964:5000::/37 with origin AS58772 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58772 in the RIR database for the space.635 of 636
Route object: RIR27.156.26.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR110.80.144.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.24.160.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.24.166.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.72.128.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR124.72.136.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR182.44.64.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR182.44.64.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.128.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR240e:108:1185::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:264:a000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:964:5000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:964:a800::/38Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:964:d400::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:964:f400::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:965:5000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:965:a800::/38Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:965:d400::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:965:f400::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:966:5000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:966:a800::/38Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:966:d400::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:966:f400::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:967:5000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:967:a800::/38Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:967:d400::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:967:f400::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:982:8500::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

220.154.84.0/24RADBValid
220.154.85.0/24RADBValid

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.