Network · data from 2026-11-12
AS212330 IRAQ-IXP
Registry name: IRAQIXP Civilisation Information Technology, communication and internet services Co., LTD, IQ · PeeringDB
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 |
| 2a10:fa44:a00::/40 | Valid | None | 1 0%low visibility |
| 93.115.252.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 122.102.116.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.113.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.223.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.105.220.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.111.150.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.176.40.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 103.229.80.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.230.121.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.230.122.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.230.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.16.25.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.96.160.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.113.106.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.113.239.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.3.137.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 86.111.151.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 2a10:fa46::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a10:fa46:5::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:fa45::/32 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:fa47::/32 | Valid | RIR databaseRIPE | 633 100% |
| 79.132.195.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
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
| Change | Prefix or set | Detail |
|---|---|---|
| Bogon prefix | 192.168.20.1/32 | In IANA's special-purpose registry: Private-Use (RFC 1918). |
| Route object: none | 2a10:fa44:a00::/40 | No route object for it. Add a route object with origin AS212330 in the RIR database for the space. |
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/24 | RIPE | No ROA |
| 109.230.124.0/24 | RIPE | Valid |
| 185.21.139.0/24 | RIPE | Valid |
| 185.53.34.0/24 | RIPE | Invalid: origin |
| 2a10:fa42::/32 | RIPE | Valid |
| 2a10:fa43::/32 | RIPE | Valid |
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.