asn.dev

Observed topology

AS263486 AS263486 - CONECTA SERVICOS E INTERNET LTDA

Unclassified LACNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263486: 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
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6301
AS269595VGRNET INFORMATICA LTDAResidentialIPv4 IPv676
AS28283Adylnet TelecomResidentialIPv4 IPv649
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv610
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271016G NETWEB TELECOM LTDA - MEUnclassifiedIPv4 IPv641

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6336
AS269595VGRNET INFORMATICA LTDAResidentialIPv4 IPv676
AS28283Adylnet TelecomResidentialIPv4 IPv655
AS271016G NETWEB TELECOM LTDA - MEUnclassifiedIPv4 IPv641
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv610
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

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