asn.dev

Observed topology

AS262609 AS262609 - CL9 Tecnologias Ltda.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262609: 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
AS52925Ascenty Data Centers e Telecomunicacoes S/AUnclassifiedIPv4 IPv6153
AS16735ALGAR TELECOM S/AUnclassifiedIPv4108
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv480
AS6939Hurricane Electric LLCTransitIPv464
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv447
AS10429TELEFONICA BRASIL S.AResidentialIPv48
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS35280F5 Networks SARLHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263034Akna Tecnologia da Informacao Ltda.UnclassifiedIPv41,102

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv41,149
AS263034Akna Tecnologia da Informacao Ltda.UnclassifiedIPv41,102
AS52925Ascenty Data Centers e Telecomunicacoes S/AUnclassifiedIPv4 IPv6153
AS16735ALGAR TELECOM S/AUnclassifiedIPv4108
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv480
AS6939Hurricane Electric LLCTransitIPv464
AS10429TELEFONICA BRASIL S.AResidentialIPv48
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS35280F5 Networks SARLHostingIPv41

Provenance

Where this comes from

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