Observed topology

AS208555 Mobinhost Dade Pardazi Mobinhost Co LTD

Unclassified RIPE

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208555: 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
AS25184	Afranet	Unclassified	IPv4	868
AS42337	Respina Networks & Beyond PJSC	Unclassified	IPv4	244
AS60976	Parsan Lin Co. PJS	Unclassified	IPv4	61

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS51026	Dade Pardazi Mobinhost Co LTD	Unclassified	IPv4	245
AS215708	Mobin Arvand Infrastructure Company LTD	Unclassified	IPv4	61
AS198596	Seyed Mojtaba Imani	Unclassified	IPv4	24

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS25184	Afranet	Unclassified	IPv4	892
AS42337	Respina Networks & Beyond PJSC	Unclassified	IPv4	366
AS51026	Dade Pardazi Mobinhost Co LTD	Unclassified	IPv4	245
AS60976	Parsan Lin Co. PJS	Unclassified	IPv4	245
AS215708	Mobin Arvand Infrastructure Company LTD	Unclassified	IPv4	61
AS198596	Seyed Mojtaba Imani	Unclassified	IPv4	24

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.