asn.dev

Observed topology

AS27790 AS27790 - Universidad Nacional de Cordoba

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27790: 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
AS52444Pogliotti & Pogliotti Construcciones S.A.ResidentialIPv4 IPv6971
AS52361ARSAT - Empresa Argentina de Soluciones Satelitales S.A.UnclassifiedIPv4 IPv655
AS52374CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv639
AS4270Red de Interconexion UniversitariaEducationIPv415

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264607ASOCIACION CIVIL ALTERMUNDIUnclassifiedIPv4 IPv6213

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52444Pogliotti & Pogliotti Construcciones S.A.ResidentialIPv4 IPv6971
AS52361ARSAT - Empresa Argentina de Soluciones Satelitales S.A.UnclassifiedIPv4 IPv6268
AS264607ASOCIACION CIVIL ALTERMUNDIUnclassifiedIPv4 IPv6213
AS52374CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv639
AS4270Red de Interconexion UniversitariaEducationIPv415

Provenance

Where this comes from

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