bgpreport

Network · data from 2026-11-12

AS212330 IRAQ-IXP

Registry name: IRAQIXP Civilisation Information Technology, communication and internet services Co., LTD, IQ · PeeringDB

19IPv4 routes 94.7% RPKI valid · 94.7% with a route object
5IPv6 routes 100.0% RPKI valid · 80.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS212330, seen from no peer

Announced routes

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

192.168.20.1/32 bogon No ROA None 0 0%low visibility 1
2a10:fa44:a00::/40 Valid None 1 0%low visibility 1
93.115.252.0/24 Valid RIR databaseRIPE 673 100% 66
122.102.116.0/24 Valid RIR databaseRIPE 673 100% 66
185.113.104.0/24 Valid RIR databaseRIPE 673 100% 67
31.223.185.0/24 Valid RIR databaseRIPE 672 100% 67
86.105.220.0/24 Valid RIR databaseRIPE 672 100% 66
86.111.150.0/24 Valid RIR databaseRIPE 672 100% 66
94.176.40.0/24 Valid RIR databaseRIPE 672 100% 67
103.229.80.0/24 Valid RIR databaseRIPE 672 100% 68
109.230.121.0/24 Valid RIR databaseRIPE 672 100% 68
109.230.122.0/24 Valid RIR databaseRIPE 672 100% 67
109.230.125.0/24 Valid RIR databaseRIPE 672 100% 68
185.16.25.0/24 Valid RIR databaseRIPE 672 100% 67
185.96.160.0/24 Valid RIR databaseRIPE 672 100% 67
185.113.106.0/24 Valid RIR databaseRIPE 672 100% 67
45.113.239.0/24 Valid RIR databaseRIPE 671 100% 67
193.3.137.0/24 Valid RIR databaseRIPE 671 100% 67
86.111.151.0/24 Valid RIR databaseRIPE 667 99% 67
2a10:fa46::/32 Valid RIR databaseRIPE 635 100% 69
2a10:fa46:5::/48 Valid RIR databaseRIPE 634 100% 68
2a10:fa45::/32 Valid RIR databaseRIPE 633 100% 67
2a10:fa47::/32 Valid RIR databaseRIPE 633 100% 67
79.132.195.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS212330's PeeringDB record names no 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 8 are in fix.csv.

  • Bogon prefix1
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Bogon prefix192.168.20.1/32In IANA's special-purpose registry: Private-Use (RFC 1918).0 of 673
Route object: none2a10:fa44:a00::/40No route object for it. Add a route object with origin AS212330 in the RIR database for the space.1 of 636

Route objects not announced

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

77.81.176.0/24RIPENo ROA
109.230.124.0/24RIPEValid
185.21.139.0/24RIPEValid
185.53.34.0/24RIPEInvalid: origin
2a10:fa42::/32RIPEValid
2a10:fa43::/32RIPEValid

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.