bgpreport

Network · data from 2026-11-12

AS59011 YLWL - Beijing Yunlin Network Technology Co.,Ltd.

Registry name: YLWL - Beijing Yunlin Network Technology Co.,Ltd., CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59011, 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.
120.131.88.0/21 Invalid: origin None 134 20% 54
120.131.124.0/22 Invalid: origin None 134 20% 54
110.40.0.0/24 Invalid: origin None 109 16% 50
110.40.13.0/24 Invalid: origin None 28 4%low visibility 25
110.40.14.0/23 Invalid: origin None 28 4%low visibility 25

AS-SET

AS59011 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 16 are in fix.csv.

  • ROA: origin5
  • Route object: none5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin120.131.88.0/21ROAs covering it name AS56048, not AS59011. If AS59011 should announce it, add a ROA for AS59011.134 of 673
Route object: none120.131.88.0/21No route object for it. Add a route object with origin AS59011 in the RIR database for the space.134 of 673
ROA: origin120.131.124.0/22ROAs covering it name AS56048, not AS59011. If AS59011 should announce it, add a ROA for AS59011.134 of 673
Route object: none120.131.124.0/22No route object for it. Add a route object with origin AS59011 in the RIR database for the space.134 of 673
ROA: origin110.40.0.0/24ROAs covering it name AS56048, not AS59011; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS59011 should announce it, add a ROA for AS59011.109 of 673
Route object: none110.40.0.0/24No route object for it. Add a route object with origin AS59011 in the RIR database for the space.109 of 673
ROA: origin110.40.13.0/24ROAs covering it name AS4847, AS56048, not AS59011; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS59011 should announce it, add a ROA for AS59011.28 of 673
Route object: none110.40.13.0/24No route object for it. Add a route object with origin AS59011 in the RIR database for the space.28 of 673
ROA: origin110.40.14.0/23ROAs covering it name AS4847, AS56048, not AS59011; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS59011 should announce it, add a ROA for AS59011.28 of 673
Route object: none110.40.14.0/23No route object for it. Add a route object with origin AS59011 in the RIR database for the space.28 of 673

Route objects not announced

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

114.112.160.0/21RADBNo ROA
114.112.164.0/24RADBNo ROA
114.112.166.0/24RADBNo ROA
114.112.167.0/24RADBNo ROA
114.112.168.0/21RADBNo ROA
114.112.173.0/24RADBNo ROA

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.