Observed topology
AS274614 VELOX NETWORK SOLUCOES TECNOLOGICAS LTDA
Residential LACNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS274614: 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 AS274614 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS268278 | PING.NET Multimidia LTDA ME | Unclassified | IPv4 IPv6 | 181 |
| AS270899 | Worksul Telecom | Unclassified | IPv4 IPv6 | 172 |
| AS264920 | Shel Net Informatica Ltda | Residential | IPv4 IPv6 | 129 |
| AS266386 | BLUS TELECOM LTDA - EPP | Unclassified | IPv4 IPv6 | 90 |
| AS270309 | TURBONET - Provedor de Acesso a Internet | Unclassified | IPv4 IPv6 | 62 |
| AS262551 | Farol Telecom | Unclassified | IPv4 | 61 |
| AS271620 | Portonet Servicos de Telecomunicao Ltda | Unclassified | IPv4 | 25 |
| AS264216 | Fenix Wireless Internet Ltda | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS274614 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,295 |
| AS264920 | Shel Net Informatica Ltda | Residential | IPv4 IPv6 | 271 |
| AS268278 | PING.NET Multimidia LTDA ME | Unclassified | IPv4 IPv6 | 181 |
| AS270899 | Worksul Telecom | Unclassified | IPv4 IPv6 | 172 |
| AS271620 | Portonet Servicos de Telecomunicao Ltda | Unclassified | IPv4 IPv6 | 101 |
| AS266386 | BLUS TELECOM LTDA - EPP | Unclassified | IPv4 IPv6 | 90 |
| AS270309 | TURBONET - Provedor de Acesso a Internet | Unclassified | IPv4 IPv6 | 62 |
| AS262551 | Farol Telecom | Unclassified | IPv4 | 61 |
| AS16735 | ALGAR TELECOM S/A | Unclassified | IPv4 | 26 |
| AS264216 | Fenix Wireless Internet Ltda | Unclassified | IPv4 | 9 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.