Observed topology
AS269713 VOO TELECOM AP LTDA
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS269713: 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.
Transit
Downstream networks
Networks for which AS269713 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS270464 | NewFast Telecom | Unclassified | IPv4 IPv6 | 252 |
| AS269213 | UPLINK MAIS FIBRA | Unclassified | IPv4 | 144 |
| AS270380 | PROVELINK TELECOM LTDA | Unclassified | IPv4 IPv6 | 99 |
| AS270237 | Mult3 Telecom | Unclassified | IPv4 IPv6 | 95 |
| AS271377 | Torres Alves e Brandao Ltda - ME | Unclassified | IPv4 IPv6 | 84 |
| AS268636 | Netway solucoes em redes de acesso e comunicacao l | Unclassified | IPv4 | 7 |
Adjacency
Adjacent networks
Every AS seen directly next to AS269713 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS266302 | RENOVENET TELECOMUNICACOES LTDA - ME | Unclassified | IPv4 | 498 |
| AS265038 | TELFO SERVICO DE TELECOMUNICACOES LTDA | Residential | IPv4 IPv6 | 401 |
| AS270464 | NewFast Telecom | Unclassified | IPv4 IPv6 | 252 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 163 |
| AS269213 | UPLINK MAIS FIBRA | Unclassified | IPv4 IPv6 | 158 |
| AS270380 | PROVELINK TELECOM LTDA | Unclassified | IPv4 IPv6 | 124 |
| AS270237 | Mult3 Telecom | Unclassified | IPv4 IPv6 | 95 |
| AS271377 | Torres Alves e Brandao Ltda - ME | Unclassified | IPv4 IPv6 | 84 |
| AS268512 | VOO TELECOM | Residential | IPv4 | 59 |
| AS24482 | SG.GS | Hosting | IPv6 | 14 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.