Observed topology
AS263483 DIRECT LAN TELECOMUNICACOES SOROCABA LTDA
Residential LACNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS263483: 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 |
|---|---|---|---|---|
| AS52468 | UFINET PANAMA S.A. | Unclassified | IPv4 IPv6 | 123 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 69 |
| AS28189 | JR & JS ENGENHARIA E COMERCIO LTDA | Unclassified | IPv4 | 13 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 5 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 | 4 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 4 |
| AS28649 | Desktop Sigmanet Comunicacao Multimidia SA | Residential | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS263483 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS267380 | Via Rapida Internet | Unclassified | IPv4 IPv6 | 39 |
Adjacency
Adjacent networks
Every AS seen directly next to AS263483 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS52468 | UFINET PANAMA S.A. | Unclassified | IPv4 IPv6 | 139 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 86 |
| AS267380 | Via Rapida Internet | Unclassified | IPv4 IPv6 | 39 |
| AS28189 | JR & JS ENGENHARIA E COMERCIO LTDA | Unclassified | IPv4 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 | 4 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 4 |
| AS28649 | Desktop Sigmanet Comunicacao Multimidia SA | 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.