bgpreport

Network · data from 2026-11-12

AS59692 IQWeb FZ LLC

Registry name: IQWEB IQWeb FZ-LLC, AE · PeeringDB

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

Announced routes

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

45.132.16.0/24 No ROA Other origin only 645 96% 66
186.2.160.0/24 Valid RIR databaseRIPE 673 100% 67
186.2.168.0/24 Valid RIR databaseRIPE 671 100% 67
31.57.152.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
87.82.252.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
89.125.171.0/24 Valid RIR databaseRIPE 669 99% 67
89.219.1.0/24 Valid RIR databaseRIPE 669 99% 67
93.171.200.0/24 Valid RIR databaseRIPE 669 99% 67
152.237.231.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
181.214.208.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
186.2.161.0/24 Valid RIR databaseRIPE 669 99% 67
186.2.162.0/24 Valid RIR databaseRIPE 669 99% 67
186.2.163.0/24 Valid RIR databaseRIPE 669 99% 67
186.2.165.0/24 Valid RIR databaseRIPE 669 99% 67
186.2.166.0/24 Valid RIR databaseRIPE 669 99% 67
186.2.170.0/24 Valid RIR databaseRIPE 669 99% 67
186.2.171.0/24 Valid RIR databaseRIPE 669 99% 67
186.2.174.0/24 Valid RIR databaseRIPE 669 99% 67
186.2.175.0/24 Valid RIR databaseRIPE 669 99% 67
45.135.239.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.16.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.17.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.18.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.19.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.20.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.21.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.22.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.24.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.25.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.26.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.27.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.28.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.30.0/24 Valid RIR databaseRIPE 668 99% 67
190.115.31.0/24 Valid RIR databaseRIPE 668 99% 67
186.2.167.0/24 Valid RIR databaseRIPE 666 99% 67
185.9.185.0/24 Valid RIR databaseRIPE 646 96% 66

AS-SET

PeeringDB's irr_as_set for AS59692: AS59692:AS-IQWEB. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS59692 isn't in the set, or no route object for AS59692 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS59692 in itNot covered
AS59692:AS-IQWEB RIPElists itself further down5 member sets in no database: AS-ART-COM-CUSTOM, AS-DVCOM, AS-SKYTEL_AS-SET, AS-WESTCOM, AS207567:AS-INTEZIO 1,04615538,094 Yes 1

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

  • ROA: none1
  • Route object: none1
  • AS-SET: missing member5
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none45.132.16.0/24No ROA covers it. Add a ROA for AS59692, maxLength 24.645 of 673
Route object: none45.132.16.0/24Route objects for it name AS57724. Add a route object with origin AS59692 in the RIR database for the space.645 of 673
AS-SET: missing memberAS59692:AS-IQWEBAS59692:AS-IQWEB (RIPE) lists AS-ART-COM-CUSTOM; no IRR database read has it.
AS-SET: missing memberAS59692:AS-IQWEBAS59692:AS-IQWEB (RIPE) lists AS-DVCOM; no IRR database read has it.
AS-SET: missing memberAS59692:AS-IQWEBAS59692:AS-IQWEB (RIPE) lists AS-SKYTEL_AS-SET; no IRR database read has it.
AS-SET: missing memberAS59692:AS-IQWEBAS59692:AS-IQWEB (RIPE) lists AS-WESTCOM; no IRR database read has it.
AS-SET: missing memberAS59692:AS-IQWEBAS59692:AS-IQWEB (RIPE) lists AS207567:AS-INTEZIO; no IRR database read has it.

Route objects not announced

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

45.183.4.0/22RIPEValid
186.2.164.0/24RIPEValid
186.2.169.0/24RIPEValid
186.2.172.0/24RIPEValid
186.2.173.0/24RIPEValid
190.115.23.0/24RIPEValid
190.115.29.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.