asn.dev

Observed topology

AS264565 BERTASSO E CIA LTDA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264565: 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
AS263537Via Fibra Internet Banda Larga EIRELIResidentialIPv4 IPv6525
AS4230CLARO S.A.ResidentialIPv4 IPv6239
AS37468Angola CablesUnclassifiedIPv4 IPv6212

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267295PROVEDOR MIRASSOL LTDA - MEUnclassifiedIPv4 IPv6326
AS269521DUNETISP INTERNET LTDAUnclassifiedIPv4 IPv6326
AS273726DUNET TELECOM LTDAUnclassifiedIPv4 IPv6325
AS275678Hard Tech Telecomunicacoes LTDAUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv6739
AS37468Angola CablesUnclassifiedIPv4 IPv6722
AS263537Via Fibra Internet Banda Larga EIRELIResidentialIPv4 IPv6525
AS267295PROVEDOR MIRASSOL LTDA - MEUnclassifiedIPv4 IPv6326
AS269521DUNETISP INTERNET LTDAUnclassifiedIPv4 IPv6326
AS273726DUNET TELECOM LTDAUnclassifiedIPv4 IPv6325
AS275678Hard Tech Telecomunicacoes LTDAUnclassifiedIPv633

Provenance

Where this comes from

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