Network · data from 2026-11-12

AS49972 FANHAB NAMAVARAN e ASR e Novin Information Technology (FANHAB) , Private Joint-Stock Co

Registry name: FANHAB NAMAVARAN e ASR e Novin Information Technology (FANHAB) , Private Joint-Stock Co, IR · not in PeeringDB

23IPv4 routes 95.7% RPKI valid · 95.7% 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

6Route objects not announced registered with origin AS49972, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49972, 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.192.115.0/24	No ROA	RIR databaseRIPE	668 99%	67
91.232.73.0/24	Valid	Other origin only	670 100%	66
31.214.168.0/24	Valid	RIR databaseRIPE	670 100%	66
31.214.169.0/24	Valid	RIR databaseRIPE	670 100%	66
31.214.170.0/24	Valid	RIR databaseRIPE	670 100%	66
31.214.171.0/24	Valid	RIR databaseRIPE	670 100%	66
31.214.172.0/24	Valid	RIR databaseRIPE	670 100%	66
31.214.173.0/24	Valid	RIR databaseRIPE	670 100%	66
31.214.174.0/24	Valid	RIR databaseRIPE	670 100%	66
31.214.175.0/24	Valid	RIR databaseRIPE	670 100%	66
134.255.200.0/21	Valid	RIR databaseRIPE	670 100%	66
134.255.200.0/24	Valid	RIR databaseRIPE	670 100%	66
134.255.201.0/24	Valid	RIR databaseRIPE	670 100%	66
134.255.202.0/24	Valid	RIR databaseRIPE	670 100%	66
134.255.203.0/24	Valid	RIR databaseRIPE	670 100%	66
134.255.204.0/24	Valid	RIR databaseRIPE	670 100%	66
134.255.205.0/24	Valid	RIR databaseRIPE	670 100%	66
134.255.206.0/24	Valid	RIR databaseRIPE	670 100%	66
134.255.207.0/24	Valid	RIR databaseRIPE	670 100%	66
185.192.112.0/24	Valid	RIR databaseRIPE	670 100%	66
185.192.113.0/24	Valid	RIR databaseRIPE	670 100%	66
194.32.209.0/24	Valid	RIR databaseRIPE	669 99%	67
185.192.114.0/24	Valid	RIR databaseRIPE	668 99%	67

AS-SET

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

ROA: none1
Route object: none1
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.192.115.0/24	No ROA covers it. Add a ROA for AS49972, maxLength 24.	668 of 673
Route object: none	91.232.73.0/24	Route objects for it name AS60976. Add a route object with origin AS49972 in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.192.115.0/24

No ROA covers it. Add a ROA for AS49972, maxLength 24.

668 of 673

Route object: none

91.232.73.0/24

Route objects for it name AS60976. Add a route object with origin AS49972 in the RIR database for the space.

670 of 673

Route objects not announced

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


31.214.168.0/21	RIPE	Valid
91.216.171.0/24	RIPE	Valid
185.44.36.0/22	RIPE	Valid
185.129.168.0/24	RIPE	Valid
194.180.224.0/24	RIPE	No ROA
2a0a:32c0::/32	RIPE	No ROA

31.214.168.0/21

RIPE

Valid

91.216.171.0/24

RIPE

Valid

185.44.36.0/22

RIPE

Valid

185.129.168.0/24

RIPE

Valid

194.180.224.0/24

RIPE

No ROA

2a0a:32c0::/32

RIPE

No ROA

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.