Network · data from 2026-11-12

AS212216 Netafraz

Registry name: Netafraz Netafraz Iranian Ltd., IR · PeeringDB

11IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

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

0Route objects not announced registered with origin AS212216, seen from no peer

Announced routes

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


89.42.44.0/24	Valid	RIR databaseRIPE	671 100%	66
185.73.226.0/24	Valid	RIR databaseRIPE	671 100%	66
80.249.115.0/24	Valid	RIR databaseRIPE	670 100%	66
93.95.27.0/24	Valid	RIR databaseRIPE	670 100%	67
185.106.200.0/24	Valid	RIR databaseRIPE	670 100%	67
185.106.201.0/24	Valid	RIR databaseRIPE	670 100%	67
185.106.202.0/24	Valid	RIR databaseRIPE	670 100%	67
185.223.160.0/24	Valid	RIR databaseRIPE	670 100%	67
195.28.10.0/24	Valid	RIR databaseRIPE	670 100%	67
195.28.168.0/24	Valid	RIR databaseRIPE	670 100%	67
195.28.169.0/24	Valid	RIR databaseRIPE	670 100%	67

AS-SET

AS212216's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS212216 is announced.

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.