Observed topology
AS264589 AGRESTE LINK
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS264589: 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 AS264589 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS269392 | J FELIX JUNIOR - ME | Unclassified | IPv4 | 413 |
| AS268314 | EWERTON DA SILVA LOPES TELECOMUNICACOES | Unclassified | IPv4 IPv6 | 256 |
| AS273630 | BROWN NET | Unclassified | IPv6 | 215 |
| AS268181 | TELECOMUNICACOES JUPI LTDA | Unclassified | IPv4 | 174 |
| AS273748 | L Henrique Ferreira Zoby | Unclassified | IPv4 IPv6 | 75 |
| AS274802 | SUPERNET LINE SERVICO DE COMUNICACOES LTDA | Unclassified | IPv4 | 59 |
| AS271350 | FSNET PROVEDOR DE INTERNET LTDA | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS264589 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS61568 | ALOO TELECOM - FSF TECNOLOGIA SA | Residential | IPv4 IPv6 | 1,227 |
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 IPv6 | 567 |
| AS268314 | EWERTON DA SILVA LOPES TELECOMUNICACOES | Unclassified | IPv4 IPv6 | 528 |
| AS269392 | J FELIX JUNIOR - ME | Unclassified | IPv4 | 413 |
| AS273630 | BROWN NET | Unclassified | IPv6 | 215 |
| AS268181 | TELECOMUNICACOES JUPI LTDA | Unclassified | IPv4 | 174 |
| AS264595 | FALCAO NET PROVEDOR DE INTERNET LTDA | Residential | IPv4 IPv6 | 96 |
| AS273748 | L Henrique Ferreira Zoby | Unclassified | IPv4 IPv6 | 75 |
| AS274802 | SUPERNET LINE SERVICO DE COMUNICACOES LTDA | Unclassified | IPv4 | 59 |
| AS271350 | FSNET PROVEDOR DE INTERNET LTDA | Unclassified | 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.