bgpreport

Network · data from 2026-11-12

AS58851 YOUWE - Priority of Fashion(Beijing)Information Technology Co.,Ltd

Registry name: YOUWE - Priority of Fashion(Beijing)Information Technology Co.,Ltd, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58851, 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.
1.119.0.0/17 Valid Other IRR onlyRADB 672 100% 67
1.119.124.0/22 Valid Other IRR onlyRADB 672 100% 67
1.119.128.0/18 Valid Other IRR onlyRADB 672 100% 67
1.119.192.0/20 Valid Other IRR onlyRADB 672 100% 67
43.248.232.0/22 Valid Other IRR onlyRADB 672 100% 67
103.16.124.0/22 Valid Other IRR onlyRADB 672 100% 67
103.244.64.0/22 Valid Other IRR onlyRADB 672 100% 67
103.254.112.0/22 Valid Other IRR onlyRADB 672 100% 67
114.112.136.0/21 Valid Other IRR onlyRADB 672 100% 67
114.112.144.0/21 Valid Other IRR onlyRADB 672 100% 67
211.102.208.0/20 Valid Other IRR onlyRADB 672 100% 67
1.119.178.0/23 Valid Other IRR onlyRADB 109 16% 44

AS-SET

AS58851 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 12 are in fix.csv.

  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
Route object: RIR1.119.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.119.124.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.119.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.119.192.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR43.248.232.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.16.124.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.244.64.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.254.112.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR114.112.136.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR114.112.144.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.102.208.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.119.178.0/23Route object only in RADB. Add it in the RIR database for the space.109 of 673

Route objects not announced

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