asn.dev

Observed topology

AS49535 EMIND E-Mind Srl

Residential RIPE Cable/DSL/ISP

Upstreams 8 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 5
Upstream graph Who carries AS49535, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS49535 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49535: 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.

ASNetworkTypeFamiliesPaths seen
AS12874Fastweb SpAResidentialIPv4394
AS174Cogent Communications, LLCTransitIPv4 IPv6312
AS6939Hurricane Electric LLCTransitIPv614
AS24482SG.GSHostingIPv4 IPv613
AS31543myNet GmbHResidentialIPv4 IPv613
AS21309HERABIT S.p.A.ResidentialIPv412
AS59919Brainbox S.r.l.ResidentialIPv412
AS29632Netassist International EOODUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204903FLASHSTART GROUP SRLUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12874Fastweb SpAResidentialIPv4394
AS174Cogent Communications, LLCTransitIPv4 IPv6312
AS6939Hurricane Electric LLCTransitIPv614
AS24482SG.GSHostingIPv4 IPv613
AS31543myNet GmbHResidentialIPv4 IPv613
AS59919Brainbox S.r.l.ResidentialIPv413
AS21309HERABIT S.p.A.ResidentialIPv412
AS29632Netassist International EOODUnclassifiedIPv61
AS204903FLASHSTART GROUP SRLUnclassifiedIPv41

Provenance

Where this comes from

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