asn.dev

Observed topology

AS263779 AS263779 - Academia Nacional de Ciencias

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263779: 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
AS52228Cable TicaUnclassifiedIPv4 IPv6214
AS262197MILLICOM CABLE COSTA RICA S.A.UnclassifiedIPv4 IPv6129
AS52263Telecable Economico S.A.UnclassifiedIPv4 IPv623

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS54994Meteverse Limited.UnclassifiedIPv4120
AS266717Academia Nacional de CienciasUnclassifiedIPv4 IPv694
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv691
AS20940Akamai International B.V.HostingIPv4 IPv691
AS63293Facebook, Inc.HostingIPv4 IPv691
AS139341ACEHostingIPv4 IPv690

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52228Cable TicaUnclassifiedIPv4 IPv6697
AS262197MILLICOM CABLE COSTA RICA S.A.UnclassifiedIPv4 IPv6205
AS54994Meteverse Limited.UnclassifiedIPv4120
AS266717Academia Nacional de CienciasUnclassifiedIPv4 IPv694
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv691
AS20940Akamai International B.V.HostingIPv4 IPv691
AS63293Facebook, Inc.HostingIPv4 IPv691
AS139341ACEHostingIPv4 IPv690
AS52263Telecable Economico S.A.UnclassifiedIPv4 IPv641

Provenance

Where this comes from

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