Observed topology
AS269586 ARENNA FIBRA TELECOM
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS269586: 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 |
|---|---|---|---|---|
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 IPv6 | 90 |
| AS270644 | Lagoanet Telecomunicacoes | Unclassified | IPv4 IPv6 | 65 |
| AS274749 | Speed Connect | Residential | IPv4 IPv6 | 63 |
| AS267613 | ELETRONET S.A. | Unclassified | IPv4 | 49 |
| AS266520 | VOOB TELECOM | Residential | IPv6 | 31 |
| AS267256 | ONETIS TECNOLOGIA LTDA | Unclassified | IPv6 | 27 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS268960 | STARLINE SERVICOS DE INTERNET - ME | Residential | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS269586 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS262727 | AtualNet Provedor de Internet Ltda | Residential | IPv4 IPv6 | 94 |
Adjacency
Adjacent networks
Every AS seen directly next to AS269586 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS274749 | Speed Connect | Residential | IPv4 IPv6 | 105 |
| AS262727 | AtualNet Provedor de Internet Ltda | Residential | IPv4 IPv6 | 94 |
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 IPv6 | 90 |
| AS266520 | VOOB TELECOM | Residential | IPv4 IPv6 | 83 |
| AS270644 | Lagoanet Telecomunicacoes | Unclassified | IPv4 IPv6 | 65 |
| AS267613 | ELETRONET S.A. | Unclassified | IPv4 | 49 |
| AS267256 | ONETIS TECNOLOGIA LTDA | Unclassified | IPv6 | 27 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS268960 | STARLINE SERVICOS DE INTERNET - ME | Residential | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 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.