asn.dev

Observed topology

AS263483 DIRECT LAN TELECOMUNICACOES SOROCABA LTDA

Residential LACNIC Cable/DSL/ISP

Upstreams 7 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 4
Upstream graph Who carries AS263483, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS263483 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6123
AS6939Hurricane Electric LLCTransitIPv4 IPv669
AS28189JR & JS ENGENHARIA E COMERCIO LTDAUnclassifiedIPv413
AS24482SG.GSHostingIPv4 IPv65
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS28649Desktop Sigmanet Comunicacao Multimidia SAResidentialIPv41

Transit

Downstream networks

inferred

Networks for which AS263483 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS267380Via Rapida InternetUnclassifiedIPv4 IPv639

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS263483 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6139
AS6939Hurricane Electric LLCTransitIPv4 IPv686
AS267380Via Rapida InternetUnclassifiedIPv4 IPv639
AS28189JR & JS ENGENHARIA E COMERCIO LTDAUnclassifiedIPv418
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS28649Desktop Sigmanet Comunicacao Multimidia SAResidentialIPv41

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.