asn.dev

Observed topology

AS52423 Data Miners S.A. Racknation.cr

Hosting LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52423: 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
AS13335Cloudflare, Inc.HostingIPv41,385
AS1299Arelion Sweden ABTransitIPv4 IPv6925
AS174Cogent Communications, LLCTransitIPv4 IPv6406
AS52468UFINET PANAMA S.A.UnclassifiedIPv6225
AS52263Telecable Economico S.A.UnclassifiedIPv4 IPv6148

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262252Servicios Technologicos Antares de Costa Rica, S.A.UnclassifiedIPv4 IPv6423
AS274239RING CENTRALES DE COSTA RICA SOCIEDAD ANONIMAUnclassifiedIPv4 IPv690
AS264820COREBASES S.AUnclassifiedIPv444

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv41,385
AS1299Arelion Sweden ABTransitIPv4 IPv61,349
AS262252Servicios Technologicos Antares de Costa Rica, S.A.UnclassifiedIPv4 IPv6423
AS174Cogent Communications, LLCTransitIPv4 IPv6406
AS52263Telecable Economico S.A.UnclassifiedIPv4 IPv6272
AS52468UFINET PANAMA S.A.UnclassifiedIPv6234
AS274239RING CENTRALES DE COSTA RICA SOCIEDAD ANONIMAUnclassifiedIPv4 IPv690
AS264820COREBASES S.AUnclassifiedIPv444

Provenance

Where this comes from

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