asn.dev

Observed topology

AS270854 MCL SERVICOS E COMUNICACOES LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270854: 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
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6277
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4 IPv6130
AS265061MIRIANE ARAUJO LIMA DE OLIVEIRA - MEUnclassifiedIPv4 IPv626
AS6939Hurricane Electric LLCTransitIPv4 IPv625
AS265017TUDO ALL TELECOM SERVICOS DE INTERNET LTDAResidentialIPv4 IPv64
AS262532NET ONDA SERVICOS DE INTERNET LTDAResidentialIPv43
AS28368SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - MEResidentialIPv42

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6277
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4 IPv6130
AS265061MIRIANE ARAUJO LIMA DE OLIVEIRA - MEUnclassifiedIPv4 IPv626
AS6939Hurricane Electric LLCTransitIPv4 IPv625
AS265017TUDO ALL TELECOM SERVICOS DE INTERNET LTDAResidentialIPv4 IPv64
AS262532NET ONDA SERVICOS DE INTERNET LTDAResidentialIPv43
AS28368SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - MEResidentialIPv42

Provenance

Where this comes from

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