asn.dev

Observed topology

AS265086 GUARATIBA TELECOM SERVICOS DE COMUNICACOES LTDA ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265086: 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
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4 IPv6154
AS6939Hurricane Electric LLCTransitIPv638
AS35280F5 Networks SARLHostingIPv4 IPv66
AS24482SG.GSHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS3356Level 3 Parent, LLCTransitIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268160Globalcom Com. e Serv. de Inf. ltdaResidentialIPv4 IPv6150
AS264402MS NUNES INFORMACAO TECNOLOGICA LTDAUnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4 IPv6313
AS268160Globalcom Com. e Serv. de Inf. ltdaResidentialIPv4 IPv6150
AS6939Hurricane Electric LLCTransitIPv4 IPv676
AS264402MS NUNES INFORMACAO TECNOLOGICA LTDAUnclassifiedIPv462
AS24482SG.GSHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS35280F5 Networks SARLHostingIPv4 IPv68
AS3356Level 3 Parent, LLCTransitIPv42

Provenance

Where this comes from

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