Network · data from 2026-11-12

AS211443 SINOWORLDWIDE SINO WORLDWIDE TRADING LIMITED

Registry name: SINOWORLDWIDE SINO WORLDWIDE TRADING LIMITED, HK · not in PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

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 AS211443, seen from no peer

Announced routes

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


213.21.239.0/24	Valid	RIR databaseRIPE	672 100%	66
93.152.210.0/24	Valid	RIR databaseRIPE	671 100%	66
93.152.233.0/24	Valid	RIR databaseRIPE	671 100%	66
178.215.227.0/24	Valid	RIR databaseRIPE	671 100%	66
85.11.187.0/24	Valid	RIR databaseRIPE	670 100%	68
94.26.36.0/24	Valid	RIR databaseRIPE	670 100%	66
46.151.178.0/24	Valid	RIR databaseRIPE	669 99%	66
91.92.41.0/24	Valid	RIR databaseRIPE	669 99%	66
87.120.104.0/24	Valid	RIR databaseRIPE	665 99%	68
2a10:ca80:1::/48	Valid	RIR databaseRIPE	630 99%	67

AS-SET

AS211443 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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