asn.dev

Observed topology

AS262691 AS262691 - CONECTA LTDA.

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262691: 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
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv62,495
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6205
AS24482SG.GSHostingIPv4 IPv6104
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv659
AS35280F5 Networks SARLHostingIPv454

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28219Net Rosas Telecomunicacoes Ltda.ResidentialIPv4 IPv6809

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv63,333
AS28219Net Rosas Telecomunicacoes Ltda.ResidentialIPv4 IPv6875
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6242
AS24482SG.GSHostingIPv4 IPv6104
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv659
AS35280F5 Networks SARLHostingIPv454

Provenance

Where this comes from

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