Observed topology

AS206495 IR-RESANEHPARDAZ Gostaresh Ertebat Azin Kia Company PJSC

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206495: 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
AS24631	Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS	Unclassified	IPv4 IPv6	412

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS57563	isfahan university of medical sciences & health services	Unclassified	IPv4	189
AS211408	Fanavaran Nicsepehr Zenderood Ltd.	Unclassified	IPv4	189
AS57474	Nazhin Sepahan IT and data processing plc	Unclassified	IPv4	63
AS213069	Maya Pardazesh Iranian LLC	Unclassified	IPv4	63
AS215271	Isfahan Science & Technology Town	Unclassified	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS24631	Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS	Unclassified	IPv4 IPv6	976
AS57563	isfahan university of medical sciences & health services	Unclassified	IPv4	189
AS211408	Fanavaran Nicsepehr Zenderood Ltd.	Unclassified	IPv4	189
AS57474	Nazhin Sepahan IT and data processing plc	Unclassified	IPv4	63
AS213069	Maya Pardazesh Iranian LLC	Unclassified	IPv4	63
AS215271	Isfahan Science & Technology Town	Unclassified	IPv4	60

Provenance

Where this comes from

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