asn.dev

Observed topology

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

Unclassified LACNIC Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52294: 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 AS52294 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS27751Neunet S.A.ResidentialIPv4 IPv6215
AS13335Cloudflare, Inc.HostingIPv4 IPv695
AS63293Facebook, Inc.HostingIPv4 IPv695
AS28009Davitel S.A.ResidentialIPv470
AS27744Tecoar SAUnclassifiedIPv459
AS264611FRONTERA DIGITAL S.A.ResidentialIPv428
AS52322TELCOCOMUnclassifiedIPv4 IPv625
AS52232Telefonia Publica y Privada S.A.UnclassifiedIPv411
AS27818CotesmaResidentialIPv49
AS267820NEUTICS S.A.P.E.M.UnclassifiedIPv47

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6385
AS52376CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv6284
AS27751Neunet S.A.ResidentialIPv4 IPv6215
AS27744Tecoar SAUnclassifiedIPv4118
AS13335Cloudflare, Inc.HostingIPv4 IPv695
AS63293Facebook, Inc.HostingIPv4 IPv695
AS28009Davitel S.A.ResidentialIPv470
AS52322TELCOCOMUnclassifiedIPv4 IPv645
AS264611FRONTERA DIGITAL S.A.ResidentialIPv428
AS52232Telefonia Publica y Privada S.A.UnclassifiedIPv411

All 12 adjacent →

Provenance

Where this comes from

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