asn.dev

Observed topology

AS270586 B2 NETWORKS MULTIMIDIA LTDA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270586: 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
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv694
AS6939Hurricane Electric LLCTransitIPv4 IPv662
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS269475E D Sousa telecomunicacoesResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270489GALAXY NET TELECOM LTDAUnclassifiedIPv4102
AS272533NETSPACE TELECOM LTDAUnclassifiedIPv662
AS270844AXION3 TELECOM LTDAUnclassifiedIPv458
AS269475E D Sousa telecomunicacoesResidentialIPv4 IPv617

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6162
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6117
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS270489GALAXY NET TELECOM LTDAUnclassifiedIPv4102
AS272533NETSPACE TELECOM LTDAUnclassifiedIPv662
AS270844AXION3 TELECOM LTDAUnclassifiedIPv458
AS269475E D Sousa telecomunicacoesResidentialIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS35280F5 Networks SARLHostingIPv4 IPv64

Provenance

Where this comes from

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