Observed topology

AS204650 ERTEBATATESABETEAVAARVAND

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204650: 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 IPv6	2,075

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS197343	Toloe Rayaneh Loghman Educational and Cultural Co. LTD	Unclassified	IPv4	1,920
AS62250	SINA ATINET Company (Ltd)	Unclassified	IPv4	900
AS213727	Varesh Cloud Hosting Limited Liability Company	Unclassified	IPv4	240
AS206507	Noavaran System Sarv Co.Ltd	Unclassified	IPv4	181
AS212036	Parsway Shomal Company Ltd	Unclassified	IPv4	180
AS39466	Ahang Rayan Malayer Co. LTD	Hosting	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS42337	Respina Networks & Beyond PJSC	Unclassified	IPv4 IPv6	5,556
AS197343	Toloe Rayaneh Loghman Educational and Cultural Co. LTD	Unclassified	IPv4	1,920
AS62250	SINA ATINET Company (Ltd)	Unclassified	IPv4	900
AS213727	Varesh Cloud Hosting Limited Liability Company	Unclassified	IPv4	240
AS206507	Noavaran System Sarv Co.Ltd	Unclassified	IPv4	181
AS212036	Parsway Shomal Company Ltd	Unclassified	IPv4	180
AS39466	Ahang Rayan Malayer Co. LTD	Hosting	IPv4	60

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.