asn.dev

Observed topology

AS52510 AS52510 - MI INTERNET SPA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52510: 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
AS263237PowerHost Telecom SPAUnclassifiedIPv4 IPv6239
AS7049Silica Networks Argentina S.A.UnclassifiedIPv4 IPv6116

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265858NETDELSUR TELECOMUNICACIONES SPAUnclassifiedIPv4185
AS267745TELECOMUNICACIONES WIFIRED LIMITADAHostingIPv4 IPv6155

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263237PowerHost Telecom SPAUnclassifiedIPv4 IPv6697
AS265858NETDELSUR TELECOMUNICACIONES SPAUnclassifiedIPv4185
AS267745TELECOMUNICACIONES WIFIRED LIMITADAHostingIPv4 IPv6155
AS22309Kitsap Credit UnionUnclassifiedIPv4118
AS7049Silica Networks Argentina S.A.UnclassifiedIPv4 IPv6116

Provenance

Where this comes from

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