asn.dev

Observed topology

AS263906 AS263906 - SE-CONNECT INTERNET BANDA LARGA LTDA ME

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263906: 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
AS263527SERRA GERAL SOLUCOES PARA INTERNET LTDAUnclassifiedIPv4 IPv6376
AS28283Adylnet TelecomResidentialIPv4 IPv6239
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv640

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS274741DIAMANTE GERACAO DE ENERGIA LTDAUnclassifiedIPv4 IPv613

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263527SERRA GERAL SOLUCOES PARA INTERNET LTDAUnclassifiedIPv4 IPv6378
AS28283Adylnet TelecomResidentialIPv4 IPv6249
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv641
AS274741DIAMANTE GERACAO DE ENERGIA LTDAUnclassifiedIPv4 IPv613

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.