Observed topology
AS266103 AGILITY TELECOM
Unclassified LACNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS266103: 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 AS266103 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS263383 | L GONZAGA JUNIOR SERVICOS DE INTERNET - ME | Unclassified | IPv4 | 252 |
| AS265168 | M. S. Ferreira Alves | Unclassified | IPv4 IPv6 | 180 |
| AS271676 | ACESSE WIFI | Unclassified | IPv4 IPv6 | 93 |
| AS268883 | Infortec - Informatica & Tecnologia Ltda - ME | Residential | IPv4 | 60 |
| AS275669 | OLIVEIRA E NOBRE SERV. DE PROV. DE INTERNET LTDA | Unclassified | IPv6 | 33 |
| AS273447 | ASLAN TELECOM LTDA | Unclassified | IPv6 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS266103 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS28126 | BRISANET SERVICOS DE TELECOMUNICACOES S.A | Residential | IPv4 IPv6 | 917 |
| AS263383 | L GONZAGA JUNIOR SERVICOS DE INTERNET - ME | Unclassified | IPv4 | 252 |
| AS265168 | M. S. Ferreira Alves | Unclassified | IPv4 IPv6 | 180 |
| AS61832 | DB3 SERVICOS DE TELECOMUNICACOES S.A | Unclassified | IPv4 | 119 |
| AS271676 | ACESSE WIFI | Unclassified | IPv4 IPv6 | 93 |
| AS273447 | ASLAN TELECOM LTDA | Unclassified | IPv4 IPv6 | 77 |
| AS268883 | Infortec - Informatica & Tecnologia Ltda - ME | Residential | IPv4 | 60 |
| AS275669 | OLIVEIRA E NOBRE SERV. DE PROV. DE INTERNET LTDA | Unclassified | IPv6 | 33 |
| AS28368 | SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - ME | Residential | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.