bgpreport

Network · data from 2026-11-12

AS138982 CHINANET-Hubei-Jiangxia-IDC - Hubei Jiangxia IDC

Registry name: CHINANET-Hubei-Jiangxia-IDC - Hubei Jiangxia IDC, CN · not in PeeringDB

12IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 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
0Route objects not announced registered with origin AS138982, seen from no peer

Announced routes

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

111.172.192.0/22 Valid Other IRR onlyRADB 672 100% 67
111.172.195.0/24 Valid Other IRR onlyRADB 672 100% 67
111.172.196.0/22 Valid Other IRR onlyRADB 672 100% 67
111.172.204.0/24 Valid Other IRR onlyRADB 672 100% 67
111.172.216.0/22 Valid Other IRR onlyRADB 672 100% 67
111.172.224.0/21 Valid Other IRR onlyRADB 672 100% 67
111.172.232.0/22 Valid Other IRR onlyRADB 672 100% 67
111.172.236.0/22 Valid Other IRR onlyRADB 672 100% 67
111.172.240.0/20 Valid Other IRR onlyRADB 672 100% 67
119.97.164.0/22 Valid Other IRR onlyRADB 672 100% 67
119.97.168.0/21 Valid Other IRR onlyRADB 672 100% 67
119.97.176.0/20 Valid Other IRR onlyRADB 672 100% 67
240e:105:e600::/39 Valid Other IRR onlyRADB 636 100% 68
240e:108:1161::/48 Valid Other IRR onlyRADB 636 100% 68
240e:95c:5000::/36 Valid Other IRR onlyRADB 636 100% 68
240e:982:6100::/40 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS138982 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 16 are in fix.csv.

  • Route object: RIR16
ChangePrefix or setDetailFull-table peers
Route object: RIR111.172.192.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.172.195.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.172.196.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.172.204.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.172.216.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.172.224.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.172.232.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.172.236.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.172.240.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.97.164.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.97.168.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.97.176.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR240e:105:e600::/39Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:108:1161::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:95c:5000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:982:6100::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS138982 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.