Observed topology

AS271794 AS271794 - UNITY NETWORK S.A.S.

Unclassified ARIN

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271794: 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
AS7049	Silica Networks Argentina S.A.	Unclassified	IPv4 IPv6	154

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS269872	GRUPO MKE SAS	Unclassified	IPv4 IPv6	214
AS270072	BOSTICO HORACIO HUGO (CONECTAR INTERNET)	Residential	IPv4 IPv6	104
AS52402	INTERCITY COMUNICACIONES S.A.	Unclassified	IPv4	59
AS28075	ARLINK S.A.	Residential	IPv4	58
AS265746	BVCOM INTERNET CONSULTORIA IT S.A.S.	Unclassified	IPv4	10

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS7049	Silica Networks Argentina S.A.	Unclassified	IPv4 IPv6	589
AS269872	GRUPO MKE SAS	Unclassified	IPv4 IPv6	214
AS270072	BOSTICO HORACIO HUGO (CONECTAR INTERNET)	Residential	IPv4 IPv6	104
AS52402	INTERCITY COMUNICACIONES S.A.	Unclassified	IPv4	59
AS28075	ARLINK S.A.	Residential	IPv4	58
AS64106	CABASE Camara Arg de Base de Datos y Serv en Linea	Unclassified	IPv4	10
AS265746	BVCOM INTERNET CONSULTORIA IT S.A.S.	Unclassified	IPv4	10

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.