Observed topology

AS59441 HOSTIRAN-NETWORK

Hosting RIPE Content

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

Upstream graph Who carries AS59441, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS59441 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59441: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

AS	Network	Type	Families	Paths seen
AS42337	Respina Networks & Beyond PJSC	Unclassified	IPv4	3,403
AS12880	Iran Information Technology Company PJSC	Residential	IPv4 IPv6	678
AS48011	Turunc Smart Bilgisayar Teknoloji Ve Dis Ticaret Limited Sirketi	Hosting	IPv4	600
AS197207	Mobile Communication Company of Iran PLC	Unclassified	IPv4	122
AS202468	Noyan Abr Arvan Co. ( Private Joint Stock)	Unclassified	IPv4	62

Transit

Downstream networks

inferred

Networks for which AS59441 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS48029	NOAVARAN SHABAKEH SABZ MEHREGAN (Ltd.)	Unclassified	IPv4	186

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS59441 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS42337	Respina Networks & Beyond PJSC	Unclassified	IPv4	3,589
AS12880	Iran Information Technology Company PJSC	Residential	IPv4 IPv6	678
AS48011	Turunc Smart Bilgisayar Teknoloji Ve Dis Ticaret Limited Sirketi	Hosting	IPv4	600
AS48029	NOAVARAN SHABAKEH SABZ MEHREGAN (Ltd.)	Unclassified	IPv4	186
AS197207	Mobile Communication Company of Iran PLC	Unclassified	IPv4	122
AS202468	Noyan Abr Arvan Co. ( Private Joint Stock)	Unclassified	IPv4	62

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.