bgpreport

Network · data from 2026-11-12

AS44090 MahanNet-AS Enteghal Dadeh Mahan Co. PJSC

Registry name: MahanNet-AS Enteghal Dadeh Mahan Co. PJSC, IR · not in PeeringDB

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

Announced routes

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

91.213.83.0/24 Valid None 670 100% 67
193.107.44.0/24 Valid None 670 100% 67
2a12:2500::/29 Valid None 631 99% 67
2.57.3.0/24 Valid RIR databaseRIPE 671 100% 67
5.202.72.0/22 Valid RIR databaseRIPE 671 100% 66
5.202.72.0/23 Valid RIR databaseRIPE 671 100% 67
5.202.72.0/24 Valid RIR databaseRIPE 671 100% 67
5.202.74.0/24 Valid RIR databaseRIPE 671 100% 66
5.202.75.0/24 Valid RIR databaseRIPE 671 100% 66
5.202.102.0/24 Valid RIR databaseRIPE 671 100% 66
91.227.27.0/24 Valid RIR databaseRIPE 671 100% 67
109.70.237.0/24 Valid RIR databaseRIPE 671 100% 66
185.179.168.0/22 Valid RIR databaseRIPE 671 100% 66
185.179.168.0/24 Valid RIR databaseRIPE 671 100% 66
213.176.7.0/24 Valid RIR databaseRIPE 671 100% 66
213.176.127.0/24 Valid RIR databaseRIPE 671 100% 66
45.142.189.0/24 Valid RIR databaseRIPE 670 100% 66
185.129.232.0/22 Valid RIR databaseRIPE 670 100% 66
185.129.238.0/23 Valid RIR databaseRIPE 670 100% 66
185.129.236.0/23 Valid RIR databaseRIPE 669 99% 66
2a0a:74c0::/32 Valid RIR databaseRIPE 634 100% 67
2a04:1400::/29 Valid RIR databaseRIPE 633 100% 67
2a11:900::/29 Valid RIR databaseRIPE 631 99% 67
2a11:4e00::/29 Valid RIR databaseRIPE 631 99% 67
2a12:2700::/29 Valid RIR databaseRIPE 631 99% 67

AS-SET

AS44090 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: none3
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none91.213.83.0/24No route object for it. Add a route object with origin AS44090 in the RIR database for the space.670 of 673
Route object: none193.107.44.0/24No route object for it. Add a route object with origin AS44090 in the RIR database for the space.670 of 673
Route object: none2a12:2500::/29No route object for it. Add a route object with origin AS44090 in the RIR database for the space.631 of 636

Route objects not announced

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

5.202.73.0/24RIPEValid
5.202.74.0/23RIPEValid
185.129.232.0/21RIPEValid
185.169.39.0/24RIPEValid
185.179.169.0/24RIPEInvalid: maxLength
185.179.170.0/24RIPEInvalid: maxLength
185.179.171.0/24RIPEInvalid: maxLength
2a0a:74c0::/36RIPEInvalid: maxLength
2a0a:74c0::/40RIPEInvalid: maxLength
2a0a:74c0:1000::/36RIPEInvalid: maxLength
2a0a:74c0:2000::/36RIPEInvalid: maxLength
2a0a:74c0:3000::/36RIPEInvalid: maxLength
2a0a:74c0:4000::/36RIPEInvalid: maxLength
2a0a:74c0:5000::/36RIPEInvalid: maxLength

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.