asn.dev

Observed topology

AS28075 ARLINK S.A.

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28075: 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
AS22927Telefonica de ArgentinaMobileIPv4 IPv66,706
AS3356Level 3 Parent, LLCTransitIPv4 IPv65,375
AS7303Telecom Argentina S.A.MobileIPv4 IPv6580
AS7049Silica Networks Argentina S.A.UnclassifiedIPv4 IPv6198
AS11664Techtel LMDS Comunicaciones Interactivas S.A.ResidentialIPv464
AS271794UNITY NETWORK S.A.S.UnclassifiedIPv458
AS52361ARSAT - Empresa Argentina de Soluciones Satelitales S.A.UnclassifiedIPv633

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS22927Telefonica de ArgentinaMobileIPv4 IPv66,706
AS3356Level 3 Parent, LLCTransitIPv4 IPv65,375
AS7303Telecom Argentina S.A.MobileIPv4 IPv6580
AS7049Silica Networks Argentina S.A.UnclassifiedIPv4 IPv6198
AS11664Techtel LMDS Comunicaciones Interactivas S.A.ResidentialIPv464
AS271794UNITY NETWORK S.A.S.UnclassifiedIPv458
AS52361ARSAT - Empresa Argentina de Soluciones Satelitales S.A.UnclassifiedIPv633

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.