asn.dev

Observed topology

AS270706 AS270706 - LAN TELECOM INTERNET BANDA LARGA LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270706: 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
AS266101MARTINS.NET SERVICOS DE TELECOMUNICACOES LTDAResidentialIPv4334
AS26615TIM S/AMobileIPv4 IPv653
AS6939Hurricane Electric LLCTransitIPv430
AS10429TELEFONICA BRASIL S.AResidentialIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266101MARTINS.NET SERVICOS DE TELECOMUNICACOES LTDAResidentialIPv4107
AS268693EVOX SISTEMAS DIGITAIS LTDAUnclassifiedIPv4 IPv623
AS272167NCWEB TELECOMResidentialIPv62

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS266101MARTINS.NET SERVICOS DE TELECOMUNICACOES LTDAResidentialIPv4500
AS26615TIM S/AMobileIPv4 IPv6111
AS6939Hurricane Electric LLCTransitIPv477
AS272167NCWEB TELECOMResidentialIPv4 IPv661
AS10429TELEFONICA BRASIL S.AResidentialIPv4 IPv642
AS268693EVOX SISTEMAS DIGITAIS LTDAUnclassifiedIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62

Provenance

Where this comes from

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