Observed topology
AS61588 DIGITAL PROVEDOR DE ACESSO A INTERNET LTDA
Residential ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS61588: 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 AS61588 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS267219 | Netware Telecomunicacoes e Informatica EIRELI | Residential | IPv4 IPv6 | 237 |
| AS263968 | RF TELECOM | Unclassified | IPv4 | 229 |
| AS270411 | GOMES & SILVA INTERNET LTDA | Unclassified | IPv4 IPv6 | 219 |
| AS269664 | MAIS TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 96 |
| AS271272 | REDE W10 - PROVEDOR DE INTERNET LTDA | Unclassified | IPv4 IPv6 | 95 |
| AS263417 | UNIVERSIDADE CATOLICA DOM BOSCO | Unclassified | IPv4 | 39 |
| AS270750 | Link Net Telecom | Unclassified | IPv4 | 16 |
Adjacency
Adjacent networks
Every AS seen directly next to AS61588 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS53062 | GGNET TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 1,033 |
| AS4230 | CLARO S.A. | Residential | IPv4 IPv6 | 942 |
| AS267219 | Netware Telecomunicacoes e Informatica EIRELI | Residential | IPv4 IPv6 | 552 |
| AS10429 | TELEFONICA BRASIL S.A | Residential | IPv4 IPv6 | 385 |
| AS263968 | RF TELECOM | Unclassified | IPv4 | 229 |
| AS270411 | GOMES & SILVA INTERNET LTDA | Unclassified | IPv4 IPv6 | 219 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 165 |
| AS269664 | MAIS TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 96 |
| AS271272 | REDE W10 - PROVEDOR DE INTERNET LTDA | Unclassified | IPv4 IPv6 | 95 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 48 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.