bgpreport

Network · data from 2026-11-12

AS211484 YSZ YSZ TRADING CO., LIMITED

Registry name: YSZ YSZ TRADING CO., LIMITED, HK · not in PeeringDB

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

Announced routes

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

194.147.17.0/24 Invalid: origin Other origin only 2 0%low visibility 2
45.139.211.0/24 No ROA None 2 0%low visibility 2
154.6.60.0/24 Valid None 673 100% 66
154.6.61.0/24 Valid None 673 100% 66
154.6.193.0/24 Valid None 673 100% 66
155.117.252.0/24 Valid Nonecovered by 155.117.252.0/23 673 100% 66
155.117.253.0/24 Valid Nonecovered by 155.117.252.0/23 673 100% 66
185.229.240.0/24 Valid Other origin only 673 100% 66
185.229.241.0/24 Valid Other origin only 673 100% 66
5.180.48.0/24 Valid Other IRR onlyRADB 673 100% 66
31.57.144.0/24 Valid Other IRR onlyRADB 673 100% 66
95.134.201.0/24 Valid Other IRR onlyRADB 673 100% 66
98.142.244.0/24 Valid Other IRR onlyRADB 673 100% 66
154.16.180.0/24 Valid Other IRR onlyRADB 673 100% 66
181.215.178.0/24 Valid Other IRR onlyRADB 673 100% 66
185.135.157.0/24 Valid Other IRR onlyRADB 673 100% 66
191.96.100.0/24 Valid Other IRR onlyRADB 673 100% 66
212.18.115.0/24 Valid Other IRR onlyRADB 673 100% 66
131.123.23.0/24 Valid RIR databaseRIPE 673 100% 67
172.110.219.0/24 Valid RIR databaseRIPE 673 100% 67
185.233.18.0/24 Valid RIR databaseRIPE 673 100% 67
194.35.227.0/24 Valid RIR databaseRIPE 673 100% 67
194.76.0.0/24 Valid RIR databaseRIPE 673 100% 67
217.216.231.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
45.136.174.0/24 Valid RIR databaseRIPE 672 100% 67
45.8.178.0/24 Valid RIR databaseRIPE 670 100% 66
45.12.32.0/24 Valid RIR databaseRIPE 670 100% 66
45.12.33.0/24 Valid RIR databaseRIPE 670 100% 66
45.142.0.0/24 Valid RIR databaseRIPE 670 100% 66
45.142.3.0/24 Valid RIR databaseRIPE 670 100% 66
45.148.147.0/24 Valid RIR databaseRIPE 670 100% 66

AS-SET

AS211484 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 22 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none9
  • Route object: RIR9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin194.147.17.0/24ROAs covering it name AS834, not AS211484. If AS211484 should announce it, add a ROA for AS211484.2 of 673
Route object: none194.147.17.0/24Route objects for it name AS834. Add a route object with origin AS211484 in the RIR database for the space.2 of 673
ROA: none45.139.211.0/24No ROA covers it. Add a ROA for AS211484, maxLength 24.2 of 673
Route object: none45.139.211.0/24No route object for it. Add a route object with origin AS211484 in the RIR database for the space.2 of 673
Route object: none154.6.60.0/24No route object for it. Add a route object with origin AS211484 in the RIR database for the space.673 of 673
Route object: none154.6.61.0/24No route object for it. Add a route object with origin AS211484 in the RIR database for the space.673 of 673
Route object: none154.6.193.0/24No route object for it. Add a route object with origin AS211484 in the RIR database for the space.673 of 673
Route object: none155.117.252.0/24No route object for it. A route object for 155.117.252.0/23 with origin AS211484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211484 in the RIR database for the space.673 of 673
Route object: none155.117.253.0/24No route object for it. A route object for 155.117.252.0/23 with origin AS211484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211484 in the RIR database for the space.673 of 673
Route object: none185.229.240.0/24Route objects for it name AS215224. Add a route object with origin AS211484 in the RIR database for the space.673 of 673
Route object: none185.229.241.0/24Route objects for it name AS215224. Add a route object with origin AS211484 in the RIR database for the space.673 of 673
Route object: RIR5.180.48.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR31.57.144.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR95.134.201.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR98.142.244.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR154.16.180.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR181.215.178.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR185.135.157.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR191.96.100.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR212.18.115.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

155.117.252.0/23RADBValid
172.110.222.0/24RIPEValid

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.