Observed topology
AS268512 VOO TELECOM
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS268512: 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 |
|---|---|---|---|---|
| AS265038 | TELFO SERVICO DE TELECOMUNICACOES LTDA | Residential | IPv4 IPv6 | 188 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 131 |
| AS264531 | HET INTERNET LTDA | Unclassified | IPv4 | 60 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 7 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS268512 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS263878 | FONTNET ME | Unclassified | IPv4 IPv6 | 326 |
| AS264047 | FOX NET TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 207 |
| AS52611 | GROWNET E SERVICOS | Unclassified | IPv4 | 150 |
| AS61943 | Francisco Jose Rodrigues Teixeira - ME | Unclassified | IPv4 IPv6 | 147 |
| AS269108 | SET BRASIL SERVICO DE TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 91 |
| AS269679 | PAULO IDELWARTON THOMAZ FERNANDES | Unclassified | IPv4 | 59 |
| AS269713 | VOO TELECOM AP LTDA | Residential | IPv4 | 59 |
| AS272594 | BESTNET TELECOM LTDA | Unclassified | IPv6 | 31 |
| AS274489 | PLANETANET TELECOM TELECOMUNICACOES LTDA | Unclassified | IPv6 | 31 |
| AS273451 | BRANDAONET SERVICOS DE TELECOMUNICACOES LDTA | Unclassified | IPv4 IPv6 | 28 |
Adjacency
Adjacent networks
Every AS seen directly next to AS268512 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS265038 | TELFO SERVICO DE TELECOMUNICACOES LTDA | Residential | IPv4 IPv6 | 1,160 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 334 |
| AS263878 | FONTNET ME | Unclassified | IPv4 IPv6 | 326 |
| AS264047 | FOX NET TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 207 |
| AS52611 | GROWNET E SERVICOS | Unclassified | IPv4 | 150 |
| AS61943 | Francisco Jose Rodrigues Teixeira - ME | Unclassified | IPv4 IPv6 | 147 |
| AS269108 | SET BRASIL SERVICO DE TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 91 |
| AS272594 | BESTNET TELECOM LTDA | Unclassified | IPv4 IPv6 | 90 |
| AS264531 | HET INTERNET LTDA | Unclassified | IPv4 | 60 |
| AS269679 | PAULO IDELWARTON THOMAZ FERNANDES | Unclassified | IPv4 | 59 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 16:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.19M 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.