Observed topology

AS52436 Cable Televisora Color

Unclassified ARIN Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52436: 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	2,059
AS22927	Telefonica de Argentina	Mobile	IPv4	300
AS52361	ARSAT - Empresa Argentina de Soluciones Satelitales S.A.	Unclassified	IPv4 IPv6	198
AS7303	Telecom Argentina S.A.	Mobile	IPv4	188
AS52360	CABASE Camara Arg de Base de Datos y Serv en Linea	Unclassified	IPv4	36

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS52475	OFICINA PYME S.A.	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS7049	Silica Networks Argentina S.A.	Unclassified	IPv4	2,089
AS22927	Telefonica de Argentina	Mobile	IPv4	300
AS7303	Telecom Argentina S.A.	Mobile	IPv4	217
AS52361	ARSAT - Empresa Argentina de Soluciones Satelitales S.A.	Unclassified	IPv4 IPv6	198
AS52475	OFICINA PYME S.A.	Unclassified	IPv4	59
AS52360	CABASE Camara Arg de Base de Datos y Serv en Linea	Unclassified	IPv4	36

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.