Observed topology

AS35372 DataCom GeniusMind S.A.

Unclassified RIPE

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35372: 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
AS206065	Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS	Unclassified	IPv4 IPv6	272
AS211421	Asiatech Data Transmission company	Unclassified	IPv4	249
AS65000	unnamed	Unclassified	IPv6	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS215350	Abr Ayande Iranian Co. (Private Joint Stock)	Unclassified	IPv4	187
AS219142	Avrin Telecom Industry Development Company (Private Joint Stock)	Unclassified	IPv4	61
AS210707	Dadeh Pardazesh Boroumand Kerman co. LLC	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS211421	Asiatech Data Transmission company	Unclassified	IPv4	497
AS206065	Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS	Unclassified	IPv4 IPv6	272
AS215350	Abr Ayande Iranian Co. (Private Joint Stock)	Unclassified	IPv4	187
AS219142	Avrin Telecom Industry Development Company (Private Joint Stock)	Unclassified	IPv4	61
AS60248	Sefroyek Pardaz Engineering PJSC	Unclassified	IPv4	2
AS65000	unnamed	Unclassified	IPv6	2
AS210707	Dadeh Pardazesh Boroumand Kerman co. LLC	Unclassified	IPv4	2

Provenance

Where this comes from

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