Observed topology

AS16322 PARSONLINE Tehran - IRAN

Unclassified APNIC

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16322: 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
AS42440	Rayaneh Danesh Golestan Complex P.J.S. Co.	Unclassified	IPv4	1,616

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS60976	Parsan Lin Co. PJS	Unclassified	IPv4	2,671
AS61061	Parsan Lin Co. PJS	Unclassified	IPv4	61
AS60315	Tehran Securities Exchange Technology Management Co. PLC	Unclassified	IPv4	59
AS62367	Pardakht Nowin Arian PJSC	Unclassified	IPv4	59
AS204787	FANAVARAN NOVIN BONYAN PASARGAD Co., (psj)	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS42440	Rayaneh Danesh Golestan Complex P.J.S. Co.	Unclassified	IPv4	7,554
AS60976	Parsan Lin Co. PJS	Unclassified	IPv4	5,820
AS61061	Parsan Lin Co. PJS	Unclassified	IPv4	61
AS60315	Tehran Securities Exchange Technology Management Co. PLC	Unclassified	IPv4	59
AS62367	Pardakht Nowin Arian PJSC	Unclassified	IPv4	59
AS204787	FANAVARAN NOVIN BONYAN PASARGAD Co., (psj)	Unclassified	IPv4	59

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.