Network · data from 2026-11-12

AS153773 METAQUOTES-AS-AP - MetaQuotes Ltd

Registry name: METAQUOTES-AS-AP - MetaQuotes Ltd, HK · not in PeeringDB

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

6IPv6 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 AS153773, seen from no peer

Announced routes

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


203.24.98.0/24	Valid	RIR databaseAPNIC	673 100%	67
203.29.60.0/24	Valid	RIR databaseAPNIC	673 100%	67
36.255.77.0/24	Valid	RIR databaseAPNIC	672 100%	67
36.255.78.0/24	Valid	RIR databaseAPNIC	672 100%	67
36.255.79.0/24	Valid	RIR databaseAPNIC	672 100%	67
36.255.76.0/24	Valid	RIR databaseAPNIC	669 99%	67
2401:fce0:10::/48	Valid	RIR databaseAPNIC	636 100%	68
2401:fce0:11::/48	Valid	RIR databaseAPNIC	635 100%	68
2401:fce0:21::/48	Valid	RIR databaseAPNIC	635 100%	68
2401:fce0:30::/48	Valid	RIR databaseAPNIC	634 100%	67
2401:fce0:31::/48	Valid	RIR databaseAPNIC	634 100%	68
2401:fce0:20::/48	Valid	RIR databaseAPNIC	605 95%	67

AS-SET

AS153773 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 AS153773 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.