Observed topology
AS262872 DIGICONTROL SERVICOS DE PROVEDORES LTDA
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS262872: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 229 |
| AS266388 | ZAZ NATAL | Residential | IPv4 IPv6 | 208 |
| AS265080 | AD TELECOM | Unclassified | IPv4 IPv6 | 184 |
| AS271253 | LINK BRASIL TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 95 |
| AS268959 | INOVANET EMPREENDIMENTOS LTDA | Unclassified | IPv4 | 23 |
| AS1031 | PEER 1031 LLC | Unclassified | IPv4 | 16 |
| AS24482 | SG.GS | Hosting | IPv4 | 4 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 | 3 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS262872 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS262872 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS265080 | AD TELECOM | Unclassified | IPv4 IPv6 | 411 |
| AS271253 | LINK BRASIL TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 314 |
| AS270511 | Ultra Cabo | Unclassified | IPv4 IPv6 | 309 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 262 |
| AS266388 | ZAZ NATAL | Residential | IPv4 IPv6 | 208 |
| AS270872 | BENTO BIDIO DAS NEVES | Unclassified | IPv4 IPv6 | 183 |
| AS268959 | INOVANET EMPREENDIMENTOS LTDA | Unclassified | IPv4 | 81 |
| AS264315 | Ciclo Tecnologia | Unclassified | IPv4 IPv6 | 34 |
| AS1031 | PEER 1031 LLC | Unclassified | IPv4 | 28 |
| AS268465 | L. P. DA SILVA BEZERRA ME | Unclassified | IPv4 IPv6 | 18 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.