bgpreport

Network · data from 2026-11-12

AS136192 CHINATELECOM-HUBEI-XIANGYANG-IDC - Xiangyang, Hubei Province, P.R.China.

Registry name: CHINATELECOM-HUBEI-XIANGYANG-IDC - Xiangyang, Hubei Province, P.R.China., CN · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.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 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 AS136192, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136192, 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.
27.22.52.0/22 Valid Other IRR onlyRADB 672 100% 67
27.22.56.0/22 Valid Other IRR onlyRADB 672 100% 67
111.177.0.0/20 Valid Other IRR onlyRADB 672 100% 67
111.177.16.0/21 Valid Other IRR onlyRADB 672 100% 67
111.177.24.0/21 Valid Other IRR onlyRADB 672 100% 67
111.177.32.0/20 Valid Other IRR onlyRADB 672 100% 67
240e:d:a800::/37 Valid Other IRR onlyRADB 636 100% 68
240e:95d:800::/38 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS136192 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 8 are in fix.csv.

  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: RIR27.22.52.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR27.22.56.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.177.0.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.177.16.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.177.24.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.177.32.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR240e:d:a800::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:95d:800::/38Route 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 AS136192 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.