asn.dev

Observed topology

AS270309 TURBONET - Provedor de Acesso a Internet

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270309: 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
AS53087TELY Ltda.ResidentialIPv4 IPv693
AS266964INFOWAYNET TELECOMUnclassifiedIPv460
AS274614VELOX NETWORK SOLUCOES TECNOLOGICAS LTDAResidentialIPv4 IPv659
AS262490Ambiente Virtual Sistemas e Conectividade LtdaResidentialIPv4 IPv645
AS262773PROXXIMA TELECOMUNICACOES SAUnclassifiedIPv444
AS267146Stec Provedor de Internet LTDAUnclassifiedIPv4 IPv633
AS273658VIRTUAX PROVIMENTO SERVICOS DE TELECOMUNICACOES LTUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS274709FERREIRA TELECOM LTDAUnclassifiedIPv4 IPv6114

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262773PROXXIMA TELECOMUNICACOES SAUnclassifiedIPv4 IPv6161
AS274709FERREIRA TELECOM LTDAUnclassifiedIPv4 IPv6117
AS53087TELY Ltda.ResidentialIPv4 IPv693
AS266964INFOWAYNET TELECOMUnclassifiedIPv460
AS274614VELOX NETWORK SOLUCOES TECNOLOGICAS LTDAResidentialIPv4 IPv659
AS262490Ambiente Virtual Sistemas e Conectividade LtdaResidentialIPv4 IPv645
AS267146Stec Provedor de Internet LTDAUnclassifiedIPv4 IPv633
AS273658VIRTUAX PROVIMENTO SERVICOS DE TELECOMUNICACOES LTUnclassifiedIPv62

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.