asn.dev

Observed topology

AS270280 AS DOS SANTOS ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270280: 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
AS263144R2 TECNOLOGIA E TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv6172
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv694
AS267113CLICKCONNECT SOLUCOES EM INTERNET E TECNOLOGIAResidentialIPv460
AS266240A2 TELECOM EIRELI - MEUnclassifiedIPv49
AS269646G4 Telecom FibraResidentialIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS2707213COMNECT TELECOM LTDAUnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263144R2 TECNOLOGIA E TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv6172
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6126
AS267113CLICKCONNECT SOLUCOES EM INTERNET E TECNOLOGIAResidentialIPv460
AS2707213COMNECT TELECOM LTDAUnclassifiedIPv632
AS266240A2 TELECOM EIRELI - MEUnclassifiedIPv49
AS269646G4 Telecom FibraResidentialIPv49

Provenance

Where this comes from

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