Observed topology
AS266516 Naveganet Comercio e Servicos Eirele
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS266516: 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 AS266516 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS266129 | LOCALLINK TELECOMUNICACOES LTDA - ME | Residential | IPv4 | 222 |
| AS268423 | susana g de souza me | Unclassified | IPv4 IPv6 | 161 |
| AS269704 | G DE OLIVEIRA LIMA SERVICOS DE TELECOMUNICOES | Unclassified | IPv4 IPv6 | 128 |
| AS266084 | F DOS S BEZERRA PONTES - ME | Unclassified | IPv4 IPv6 | 95 |
| AS266159 | SIN FIBRA SERVICOS DE COMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 92 |
| AS270369 | Naveganet Comercio e Servico LTDA | Unclassified | IPv4 | 62 |
| AS270397 | CELNEET TELECOM | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS266516 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 IPv6 | 471 |
| AS52965 | 1TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDA | Unclassified | IPv4 IPv6 | 440 |
| AS266129 | LOCALLINK TELECOMUNICACOES LTDA - ME | Residential | IPv4 | 222 |
| AS265377 | FLASH NET TELECOMUNICACOES LTDA - ME | Unclassified | IPv4 IPv6 | 191 |
| AS266084 | F DOS S BEZERRA PONTES - ME | Unclassified | IPv4 IPv6 | 185 |
| AS268423 | susana g de souza me | Unclassified | IPv4 IPv6 | 161 |
| AS269704 | G DE OLIVEIRA LIMA SERVICOS DE TELECOMUNICOES | Unclassified | IPv4 IPv6 | 128 |
| AS266159 | SIN FIBRA SERVICOS DE COMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 92 |
| AS270369 | Naveganet Comercio e Servico LTDA | Unclassified | IPv4 | 62 |
| AS270397 | CELNEET TELECOM | Unclassified | IPv4 | 59 |
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.