Observed topology
AS269060 CLICK CONNECT TELECOM LTDA
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS269060: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS52468 | UFINET PANAMA S.A. | Unclassified | IPv4 IPv6 | 188 |
| AS11432 | Telium Telecomunicacoes Ltda | Hosting | IPv4 IPv6 | 186 |
| AS264872 | Brothers Lan House Ltda Me | Residential | IPv4 IPv6 | 48 |
| AS268397 | REINALDO DE JESUS | Residential | IPv6 | 32 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 11 |
| AS35280 | F5 Networks SARL | Hosting | IPv6 | 7 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv6 | 7 |
Transit
Downstream networks
Networks for which AS269060 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS268397 | REINALDO DE JESUS | Residential | IPv6 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS269060 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS52468 | UFINET PANAMA S.A. | Unclassified | IPv4 IPv6 | 188 |
| AS11432 | Telium Telecomunicacoes Ltda | Hosting | IPv4 IPv6 | 186 |
| AS264872 | Brothers Lan House Ltda Me | Residential | IPv4 IPv6 | 50 |
| AS268397 | REINALDO DE JESUS | Residential | IPv6 | 34 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 11 |
| AS35280 | F5 Networks SARL | Hosting | IPv6 | 7 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv6 | 7 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.