Observed topology

AS13591 Mexico Red de Telecomunicaciones, S. de R.L. de C.V.

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13591: 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
AS18734	Operbes, S.A. de C.V.	Unclassified	IPv4 IPv6	9,099
AS28525	Television Internacional, S.A. de C.V.	Unclassified	IPv4	295

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS14249	Internet Engine, S.A. de C.V.	Unclassified	IPv4	767
AS21603	Universidad La Salle, AC	Unclassified	IPv4	59
AS262927	ELARA COMUNICACIONES SAPI DE CV	Unclassified	IPv4	49
AS3073	Citigroup Inc.	Unclassified	IPv4	46
AS28454	CYBOLT MANAGED SERVICES S.A. de C.V.	Unclassified	IPv4	12

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS18734	Operbes, S.A. de C.V.	Unclassified	IPv4 IPv6	10,032
AS14249	Internet Engine, S.A. de C.V.	Unclassified	IPv4	767
AS28525	Television Internacional, S.A. de C.V.	Unclassified	IPv4	295
AS21603	Universidad La Salle, AC	Unclassified	IPv4	59
AS262927	ELARA COMUNICACIONES SAPI DE CV	Unclassified	IPv4	49
AS3073	Citigroup Inc.	Unclassified	IPv4	46
AS28454	CYBOLT MANAGED SERVICES S.A. de C.V.	Unclassified	IPv4	12

Provenance

Where this comes from

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