bgpreport

Network · data from 2026-11-12

AS136191 CHINATELECOM-HUBEI-YICHANG-IDC - YICHANG, Hubei Province, P.R.China.

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

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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 AS136191, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136191, 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.
58.50.184.0/24 Valid Other IRR onlyRADB 672 100% 67
61.183.52.0/24 Valid Other IRR onlyRADB 672 100% 67
116.207.98.0/23 Valid Other IRR onlyRADB 672 100% 67
219.138.102.0/24 Valid Other IRR onlyRADB 672 100% 67
116.207.128.0/18 Valid Other IRR onlyRADB 669 99% 67
240e:d:b000::/37 Valid Other IRR onlyRADB 636 100% 68
240e:95d:1000::/38 Valid Other IRR onlyRADB 636 100% 68
240e:95e:4000::/40 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS136191 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: RIR58.50.184.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.183.52.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.207.98.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.138.102.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.207.128.0/18Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR240e:d:b000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:95d:1000::/38Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:95e:4000::/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 AS136191 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.