Observed topology
AS52721 TOLEDO FIBRA TELECOMUNICACAO LTDA
Residential LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS52721: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 389 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 226 |
| AS22356 | Durand do Brasil Ltda | Unclassified | IPv4 IPv6 | 133 |
| AS267613 | ELETRONET S.A. | Unclassified | IPv4 IPv6 | 52 |
| AS1031 | PEER 1031 LLC | Unclassified | IPv4 | 51 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 11 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 9 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
Transit
Downstream networks
Networks for which AS52721 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS264088 | TOLEDO FIBRA TELECOMUNICACAO LTDA | Unclassified | IPv4 IPv6 | 550 |
| AS61719 | SP TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 237 |
| AS266517 | M.B. SERVICOS EM TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 232 |
| AS275615 | R de Abreu Machado | Unclassified | IPv6 | 31 |
| AS268737 | CONECT TELECOM COMUNICACAO LTDA | Unclassified | IPv4 IPv6 | 7 |
| AS266613 | COMMTEL TRANSMISSAO DE DADOS E INTERNET LTDA | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS52721 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 1,326 |
| AS61719 | SP TELECOMUNICACOES EIRELI | Unclassified | IPv4 IPv6 | 568 |
| AS264088 | TOLEDO FIBRA TELECOMUNICACAO LTDA | Unclassified | IPv4 IPv6 | 550 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 450 |
| AS266517 | M.B. SERVICOS EM TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 232 |
| AS22356 | Durand do Brasil Ltda | Unclassified | IPv4 IPv6 | 208 |
| AS267613 | ELETRONET S.A. | Unclassified | IPv4 IPv6 | 164 |
| AS1031 | PEER 1031 LLC | Unclassified | IPv4 | 93 |
| AS268737 | CONECT TELECOM COMUNICACAO LTDA | Unclassified | IPv4 IPv6 | 35 |
| AS275615 | R de Abreu Machado | Unclassified | IPv6 | 31 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.