bgpreport

Network · data from 2026-11-12

AS210513 Masarat Al-Iraq Information Technology Co., Ltd

Registry name: MASARAT-ALIRAQ Masarat Al-Iraq Information Technology Co., Ltd, IQ · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
26IPv6 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
11Route objects not announced registered with origin AS210513, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210513, 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.
185.65.255.0/24 Valid RIR databaseRIPE 673 100% 67
62.3.56.0/24 Valid RIR databaseRIPE 670 100% 68
80.173.228.0/24 Valid RIR databaseRIPE 669 99% 67
80.173.229.0/24 Valid RIR databaseRIPE 669 99% 67
2a12:100:13::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:14::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:1a::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:1b::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:1e::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:1f::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:22::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:23::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:24::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:2a::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:2b::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:2e::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:2f::/48 Valid RIR databaseRIPE 634 100% 67
2a12:100:12::/48 Valid RIR databaseRIPE 633 100% 67
2a12:100:18::/48 Valid RIR databaseRIPE 629 99% 67
2a12:100:1d::/48 Valid RIR databaseRIPE 629 99% 67
2a12:100:28::/48 Valid RIR databaseRIPE 629 99% 67
2a12:100:2d::/48 Valid RIR databaseRIPE 629 99% 67
2a12:100:16::/48 Valid RIR databaseRIPE 628 99% 67
2a12:100:19::/48 Valid RIR databaseRIPE 628 99% 67
2a12:100:1c::/48 Valid RIR databaseRIPE 628 99% 67
2a12:100:26::/48 Valid RIR databaseRIPE 628 99% 67
2a12:100:29::/48 Valid RIR databaseRIPE 628 99% 67
2a12:100:2c::/48 Valid RIR databaseRIPE 628 99% 67
2a12:100:17::/48 Valid RIR databaseRIPE 627 99% 67
2a12:100:27::/48 Valid RIR databaseRIPE 627 99% 67

AS-SET

AS210513'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 11 are in fix.csv.

  • Route object: not announced11

Route objects not announced

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

80.173.228.0/23RIPEValid
212.126.115.0/24RIPEInvalid: origin
2a12:100::/29RIPEValid
2a12:100:10::/48RIPEValid
2a12:100:11::/48RIPEValid
2a12:100:15::/48RIPEValid
2a12:100:20::/48RIPEValid
2a12:100:21::/48RIPEValid
2a12:100:25::/48RIPEValid
2a12:100:30::/48RIPEValid
2a12:100:31::/48RIPEValid

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.