Observed topology

AS52279 AS52279 - ETERNET S.R.L.

Residential LACNIC Cable/DSL/ISP

Upstreams 4 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

Upstream graph Who carries AS52279, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS52279 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52279: 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	972
AS263778	Coop. Serv. Pub. Limit. Tres Arroyos, CELTA	Unclassified	IPv4	246
AS22927	Telefonica de Argentina	Mobile	IPv4	147
AS7049	Silica Networks Argentina S.A.	Unclassified	IPv4	117

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS271980	MISION DIGITAL S.A.	Unclassified	IPv4	355
AS263818	JOSE GUILLERMO LACALLE	Unclassified	IPv4	117
AS269823	COOPERATIVA AGUA POTABLE, VIVIENDAS Y OTROS SERVICIOS PUBLICOS DE ORIENTE LTDA	Unclassified	IPv4	111

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	1,034
AS263778	Coop. Serv. Pub. Limit. Tres Arroyos, CELTA	Unclassified	IPv4	440
AS271980	MISION DIGITAL S.A.	Unclassified	IPv4	355
AS7049	Silica Networks Argentina S.A.	Unclassified	IPv4	318
AS22927	Telefonica de Argentina	Mobile	IPv4	273
AS263818	JOSE GUILLERMO LACALLE	Unclassified	IPv4	117
AS269823	COOPERATIVA AGUA POTABLE, VIVIENDAS Y OTROS SERVICIOS PUBLICOS DE ORIENTE LTDA	Unclassified	IPv4	111

Provenance

Where this comes from

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