asn.dev

Observed topology

AS265435 E.W de Aguiar Lima e Comercio EPP

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265435: 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
AS266445SEA TELECOM LTDAUnclassifiedIPv4 IPv6367
AS26615TIM S/AMobileIPv4 IPv6300
AS264509CONECTA AMAZONIA TELECOM LTDA. - MEUnclassifiedIPv4124

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265034SPEEDBIT TELECOMUNICACOES LTDA - MEUnclassifiedIPv4305
AS267044MARCELO A DOS SANTOS EIRELE -MEUnclassifiedIPv4246
AS265263MULTI TELECOM E COMERCIO DE INFORMATICA EIRELI MEUnclassifiedIPv4177
AS266235CONECTAR TELECOMUNICACOES DO BRASIL LTDA - MEUnclassifiedIPv4 IPv691
AS264509CONECTA AMAZONIA TELECOM LTDA. - MEUnclassifiedIPv4 IPv668

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS26615TIM S/AMobileIPv4 IPv6784
AS266445SEA TELECOM LTDAUnclassifiedIPv4 IPv6771
AS265034SPEEDBIT TELECOMUNICACOES LTDA - MEUnclassifiedIPv4305
AS267044MARCELO A DOS SANTOS EIRELE -MEUnclassifiedIPv4246
AS264509CONECTA AMAZONIA TELECOM LTDA. - MEUnclassifiedIPv4 IPv6199
AS265263MULTI TELECOM E COMERCIO DE INFORMATICA EIRELI MEUnclassifiedIPv4177
AS266235CONECTAR TELECOMUNICACOES DO BRASIL LTDA - MEUnclassifiedIPv4 IPv691

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.