Observed topology
AS262285 VIVAS TELECOMUNICACOES LTDA
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS262285: 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 | 574 |
| AS13786 | Seabras 1 USA, LLC | Unclassified | IPv4 IPv6 | 522 |
| AS61832 | DB3 SERVICOS DE TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 271 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 17 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 | 16 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 16 |
| AS28368 | SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - ME | Residential | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS262285 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS262281 | M.M.V.A do Brasil Multimidia Ltda. | Unclassified | IPv4 | 297 |
Adjacency
Adjacent networks
Every AS seen directly next to AS262285 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS13786 | Seabras 1 USA, LLC | Unclassified | IPv4 IPv6 | 622 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 619 |
| AS61832 | DB3 SERVICOS DE TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 418 |
| AS262281 | M.M.V.A do Brasil Multimidia Ltda. | Unclassified | IPv4 | 297 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 20 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 | 16 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 16 |
| AS28368 | SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - ME | Residential | IPv4 | 6 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 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.