bgpreport

Network · data from 2026-11-12

AS131522 YOVOLECLOUD - Beijing Yovole Cloud Computing Technology Company Limited

Registry name: YOVOLECLOUD - Beijing Yovole Cloud Computing Technology Company Limited, CN · not in PeeringDB

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

Announced routes

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

103.79.24.0/24 Valid None 5 1%low visibility 6
103.79.25.0/24 Valid None 5 1%low visibility 6
103.79.27.0/24 Valid None 5 1%low visibility 6
175.102.185.0/24 Valid None 5 1%low visibility 6
175.102.186.0/24 Valid None 5 1%low visibility 6
175.102.187.0/24 Valid None 5 1%low visibility 6
175.102.188.0/24 Valid None 5 1%low visibility 6
175.102.189.0/24 Valid None 5 1%low visibility 6
175.102.190.0/24 Valid None 5 1%low visibility 6

AS-SET

AS131522 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 9 are in fix.csv.

  • Route object: none9
ChangePrefix or setDetailFull-table peers
Route object: none103.79.24.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673
Route object: none103.79.25.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673
Route object: none103.79.27.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673
Route object: none175.102.185.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673
Route object: none175.102.186.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673
Route object: none175.102.187.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673
Route object: none175.102.188.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673
Route object: none175.102.189.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673
Route object: none175.102.190.0/24No route object for it. Add a route object with origin AS131522 in the RIR database for the space.5 of 673

Route objects not announced

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