asn.dev

Observed topology

AS52500 CABASE Camara Arg de Base de Datos y Serv en Linea

Unclassified LACNIC Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52500: 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
AS52376CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv694

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63293Facebook, Inc.HostingIPv4 IPv694
AS263720SURPORAIRE SAResidentialIPv410
AS263726Red Uno SRLResidentialIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52376CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6155
AS63293Facebook, Inc.HostingIPv4 IPv694
AS264758ISP GROUP SRLUnclassifiedIPv433
AS6939Hurricane Electric LLCTransitIPv418
AS263720SURPORAIRE SAResidentialIPv410
AS263726Red Uno SRLResidentialIPv48

Provenance

Where this comes from

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