asn.dev

Observed topology

AS270738 R&R comercio de informartica e equipamentos LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270738: 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
AS264500SoulTelecom - Provedor de Acesso a InternetUnclassifiedIPv4 IPv6421
AS266236VELPRO TELECOMUNICACOES EIRELIResidentialIPv4 IPv6116
AS14840BR.Digital TelecomUnclassifiedIPv449
AS265482NET EXPRESS BRASIL LTDA - MEResidentialIPv4 IPv615

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267987Falcon NetUnclassifiedIPv4 IPv6171
AS268142MAXXTELECOM LTDAUnclassifiedIPv491
AS266327NCS-Fibra ( New Central Solutions )UnclassifiedIPv458
AS264500SoulTelecom - Provedor de Acesso a InternetUnclassifiedIPv634

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264500SoulTelecom - Provedor de Acesso a InternetUnclassifiedIPv4 IPv6455
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6300
AS267987Falcon NetUnclassifiedIPv4 IPv6171
AS265482NET EXPRESS BRASIL LTDA - MEResidentialIPv4 IPv6118
AS266236VELPRO TELECOMUNICACOES EIRELIResidentialIPv4 IPv6116
AS268142MAXXTELECOM LTDAUnclassifiedIPv491
AS266327NCS-Fibra ( New Central Solutions )UnclassifiedIPv458

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.