bgpreport

Network · data from 2026-11-12

AS140083 CHINANET-ANHUI-AS-AP - China Telecom

Registry name: CHINANET-ANHUI-AS-AP - China Telecom, CN · not in PeeringDB

8IPv4 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 4 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS140083, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS140083, 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.
117.66.0.0/22 Valid Nonecovered by 117.66.0.0/20 6 1%low visibility 5
117.66.4.0/22 Valid Nonecovered by 117.66.0.0/20 6 1%low visibility 5
117.68.8.0/24 Valid Nonecovered by 117.68.0.0/19 6 1%low visibility 5
117.68.9.0/24 Valid Nonecovered by 117.68.0.0/19 6 1%low visibility 5
240e:6:d130::/44 Valid Other IRR onlyRADB 636 100% 68
240e:95a:3000::/36 Valid Other IRR onlyRADB 636 100% 68
61.191.48.0/24 Valid Other IRR onlyRADB 28 4%low visibility 16
117.66.0.0/20 Valid Other IRR onlyRADB 28 4%low visibility 16
117.68.0.0/19 Valid Other IRR onlyRADB 28 4%low visibility 16
117.71.0.0/22 Valid Other IRR onlyRADB 28 4%low visibility 16

AS-SET

AS140083 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 10 are in fix.csv.

  • Route object: none4
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none117.66.0.0/22No route object for it. A route object for 117.66.0.0/20 with origin AS140083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140083 in the RIR database for the space.6 of 673
Route object: none117.66.4.0/22No route object for it. A route object for 117.66.0.0/20 with origin AS140083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140083 in the RIR database for the space.6 of 673
Route object: none117.68.8.0/24No route object for it. A route object for 117.68.0.0/19 with origin AS140083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140083 in the RIR database for the space.6 of 673
Route object: none117.68.9.0/24No route object for it. A route object for 117.68.0.0/19 with origin AS140083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140083 in the RIR database for the space.6 of 673
Route object: RIR240e:6:d130::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:95a:3000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR61.191.48.0/24Route object only in RADB. Add it in the RIR database for the space.28 of 673
Route object: RIR117.66.0.0/20Route object only in RADB. Add it in the RIR database for the space.28 of 673
Route object: RIR117.68.0.0/19Route object only in RADB. Add it in the RIR database for the space.28 of 673
Route object: RIR117.71.0.0/22Route object only in RADB. Add it in the RIR database for the space.28 of 673

Route objects not announced

Every route object with origin AS140083 is announced.

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.