bgpreport

Network · data from 2026-11-12

AS42943 TOPNET Dar Al-Mustawred Trading Group Limited

Registry name: TOPNET Dar Al-Mustawred Trading Group Limited, SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42943, 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.
77.240.80.0/22 Valid Nonecovered by 77.240.80.0/20 673 100% 67
77.240.86.0/23 Valid Nonecovered by 77.240.80.0/20 673 100% 67
85.184.232.0/22 Valid Nonecovered by 85.184.232.0/21 673 100% 67
85.184.236.0/23 Valid Nonecovered by 85.184.232.0/21 673 100% 67
2a0c:1a40::/29 Valid None 635 100% 67
2a0c:1a40::/31 Valid None 634 100% 67
2a0c:1a42::/31 Valid None 634 100% 67
2a0c:1a44::/31 Valid None 634 100% 67
2a0c:1a46::/31 Valid None 634 100% 67
85.184.232.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
85.184.234.0/24 Valid RIR databaseRIPE 673 100% 67
85.184.235.0/24 Valid RIR databaseRIPE 673 100% 67
185.109.176.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
185.109.176.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.109.177.0/24 Valid RIR databaseRIPE 673 100% 67
185.109.179.0/24 Valid RIR databaseRIPE 673 100% 67
77.240.80.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.81.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.82.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.83.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.86.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.87.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.88.0/21 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.88.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.89.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.91.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.92.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.93.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.94.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.240.95.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
85.184.236.0/24 Valid RIR databaseRIPE 672 100% 67
185.109.178.0/24 Valid RIR databaseRIPE 672 100% 67
77.240.90.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
85.184.233.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS42943 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 17 are in fix.csv.

  • Route object: none9
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none77.240.80.0/22No route object for it. A route object for 77.240.80.0/20 with origin AS42943 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42943 in the RIR database for the space.673 of 673
Route object: none77.240.86.0/23No route object for it. A route object for 77.240.80.0/20 with origin AS42943 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42943 in the RIR database for the space.673 of 673
Route object: none85.184.232.0/22No route object for it. A route object for 85.184.232.0/21 with origin AS42943 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42943 in the RIR database for the space.673 of 673
Route object: none85.184.236.0/23No route object for it. A route object for 85.184.232.0/21 with origin AS42943 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42943 in the RIR database for the space.673 of 673
Route object: none2a0c:1a40::/29No route object for it. Add a route object with origin AS42943 in the RIR database for the space.635 of 636
Route object: none2a0c:1a40::/31No route object for it. Add a route object with origin AS42943 in the RIR database for the space.634 of 636
Route object: none2a0c:1a42::/31No route object for it. Add a route object with origin AS42943 in the RIR database for the space.634 of 636
Route object: none2a0c:1a44::/31No route object for it. Add a route object with origin AS42943 in the RIR database for the space.634 of 636
Route object: none2a0c:1a46::/31No route object for it. Add a route object with origin AS42943 in the RIR database for the space.634 of 636

Route objects not announced

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

77.240.80.0/20RADBNo ROA
77.240.80.0/23RIPEInvalid: maxLength
77.240.84.0/24RIPEInvalid: origin
77.240.85.0/24RIPEInvalid: origin
85.184.232.0/21RADB, RIPENo ROA
85.184.237.0/24RIPEInvalid: maxLength
85.184.238.0/24RIPEInvalid: origin
85.184.239.0/24RIPEInvalid: origin

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.