asn.dev

Observed topology

AS52376 AS52376 - CABASE Camara Arg de Base de Datos y Serv en Linea

Unclassified ARIN Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52376: 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
AS263194Advantun SRLResidentialIPv4 IPv6258
AS16814NSS S.A.UnclassifiedIPv4 IPv6170
AS6939Hurricane Electric LLCTransitIPv4 IPv679
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS52374CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6107
AS52332CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693
AS52370CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693
AS52403CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693
AS52500CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693
AS52509CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693
AS61495CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693
AS61504CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693
AS61521CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693
AS61553CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv693

All 20 downstreams →

Adjacency

Adjacent networks

All 29

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

ASNetworkTypeFamiliesPaths seen
AS263194Advantun SRLResidentialIPv4 IPv61,547
AS16814NSS S.A.UnclassifiedIPv4 IPv61,351
AS52294CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6278
AS52374CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6261
AS52324CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6209
AS61521CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6165
AS52509CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6163
AS61553CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6158
AS52500CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6153
AS52404CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6149

All 29 adjacent →

Provenance

Where this comes from

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