bgpreport

Network · data from 2026-11-12

AS45086 YOVOLE

Registry name: YOVOLE - Shanghai Yovole Networks Inc., CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45086, 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.
175.102.28.0/22 Valid None 5 1%low visibility 6
175.102.136.0/21 Valid None 5 1%low visibility 6
175.102.144.0/21 Valid None 5 1%low visibility 6
175.102.152.0/24 Valid None 5 1%low visibility 6
175.102.22.0/24 Valid None 1 0%low visibility 3
175.102.26.0/24 Valid None 1 0%low visibility 3
175.102.28.0/24 Valid None 1 0%low visibility 3
175.102.29.0/24 Valid None 1 0%low visibility 3
175.102.30.0/24 Valid None 1 0%low visibility 3
175.102.31.0/24 Valid None 1 0%low visibility 3

AS-SET

AS45086's PeeringDB record names no 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 14 are in fix.csv.

  • Route object: none10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none175.102.28.0/22No route object for it. Add a route object with origin AS45086 in the RIR database for the space.5 of 673
Route object: none175.102.136.0/21No route object for it. Add a route object with origin AS45086 in the RIR database for the space.5 of 673
Route object: none175.102.144.0/21No route object for it. Add a route object with origin AS45086 in the RIR database for the space.5 of 673
Route object: none175.102.152.0/24No route object for it. Add a route object with origin AS45086 in the RIR database for the space.5 of 673
Route object: none175.102.22.0/24No route object for it. Add a route object with origin AS45086 in the RIR database for the space.1 of 673
Route object: none175.102.26.0/24No route object for it. Add a route object with origin AS45086 in the RIR database for the space.1 of 673
Route object: none175.102.28.0/24No route object for it. Add a route object with origin AS45086 in the RIR database for the space.1 of 673
Route object: none175.102.29.0/24No route object for it. Add a route object with origin AS45086 in the RIR database for the space.1 of 673
Route object: none175.102.30.0/24No route object for it. Add a route object with origin AS45086 in the RIR database for the space.1 of 673
Route object: none175.102.31.0/24No route object for it. Add a route object with origin AS45086 in the RIR database for the space.1 of 673

Route objects not announced

Route objects with origin AS45086 whose prefix no peer sees AS45086 announce. Many are kept on purpose (backup routes, space announced only in some places).

175.102.16.0/24NTTCOM, RADBValid
175.102.17.0/24NTTCOM, RADBValid
175.102.18.0/24NTTCOM, RADBValid
175.102.19.0/24NTTCOM, RADBValid

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.