Observed topology

AS62442 Dade-Samane-Fanava Dade Samane Fanava Company (PJS)

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62442: 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
AS41881	Fanava Group	Unclassified	IPv4 IPv6	2,238

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS56815	GeniusMind S.A.	Unclassified	IPv4	472
AS44609	Fars News Agency Cultural Arts Institute	Unclassified	IPv4	117
AS50269	GuilaNet	Unclassified	IPv4	116
AS62229	Fars News Agency Cultural Arts Institute	Unclassified	IPv4	60
AS48551	Sindad Network Technology PJSC	Unclassified	IPv4	59
AS211162	Modiriat Saderat Ozhan Mashregh Pars Company PJS	Unclassified	IPv4	2
AS61036	Fanava Group	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS41881	Fanava Group	Unclassified	IPv4 IPv6	3,819
AS56815	GeniusMind S.A.	Unclassified	IPv4	1,226
AS44609	Fars News Agency Cultural Arts Institute	Unclassified	IPv4	117
AS50269	GuilaNet	Unclassified	IPv4	116
AS62229	Fars News Agency Cultural Arts Institute	Unclassified	IPv4	60
AS48551	Sindad Network Technology PJSC	Unclassified	IPv4	59
AS211162	Modiriat Saderat Ozhan Mashregh Pars Company PJS	Unclassified	IPv4	2
AS61036	Fanava Group	Unclassified	IPv4	1

Provenance

Where this comes from

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