Observed topology
AS264159 AS264159 - INEXA TELECOM LTDA
Residential LACNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS264159: 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 AS264159 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS262299 | FLAVIO JOSE PENSO JUNIOR LTDA | Unclassified | IPv4 IPv6 | 590 |
| AS266214 | UTIL PROVEDOR DE INTERNET LTDA - ME | Unclassified | IPv4 | 157 |
| AS263563 | MULTIWARE TECNOLOGIA | Unclassified | IPv4 IPv6 | 112 |
| AS274671 | ABRP TEC SERVICOS DE COMUNICACAO MULTIMIDIA LTDA | Unclassified | IPv6 | 90 |
| AS271737 | NEONETTECHNETCONECTAR BRASIL | Unclassified | IPv4 | 60 |
| AS274790 | LEGACY TELECOM LTDA | Unclassified | IPv6 | 33 |
| AS274803 | CONECTAR BRASIL LTDA | Unclassified | IPv6 | 33 |
| AS270384 | OTILIA ANTONIA CELSO | Unclassified | IPv4 | 22 |
Adjacency
Adjacent networks
Every AS seen directly next to AS264159 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4230 | CLARO S.A. | Residential | IPv4 IPv6 | 810 |
| AS7738 | V tal | Unclassified | IPv4 | 807 |
| AS266214 | UTIL PROVEDOR DE INTERNET LTDA - ME | Unclassified | IPv4 | 634 |
| AS262299 | FLAVIO JOSE PENSO JUNIOR LTDA | Unclassified | IPv4 IPv6 | 590 |
| AS8167 | V tal | Residential | IPv4 | 335 |
| AS274671 | ABRP TEC SERVICOS DE COMUNICACAO MULTIMIDIA LTDA | Unclassified | IPv4 IPv6 | 202 |
| AS263563 | MULTIWARE TECNOLOGIA | Unclassified | IPv4 IPv6 | 112 |
| AS274790 | LEGACY TELECOM LTDA | Unclassified | IPv4 IPv6 | 96 |
| AS271737 | NEONETTECHNETCONECTAR BRASIL | Unclassified | IPv4 | 60 |
| AS270384 | OTILIA ANTONIA CELSO | Unclassified | IPv4 | 43 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.