Observed topology

AS264719 INGENIERIA TELECOMUNICACIONES S.A de CV

Hosting LACNIC Network Services

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264719: 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
AS273189	CA NETWORK S.A. DE C.V.	Unclassified	IPv4	551
AS27932	Redes y Telecomunicaciones	Unclassified	IPv4	207
AS27696	LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADA	Unclassified	IPv4	113
AS6939	Hurricane Electric LLC	Transit	IPv6	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS264812	MASNET SA de CV	Unclassified	IPv4	37
AS52390	Administradora de Redes, S.A.	Unclassified	IPv6	31

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS273189	CA NETWORK S.A. DE C.V.	Unclassified	IPv4 IPv6	619
AS27932	Redes y Telecomunicaciones	Unclassified	IPv4	207
AS27696	LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADA	Unclassified	IPv4	113
AS264812	MASNET SA de CV	Unclassified	IPv4	37
AS6939	Hurricane Electric LLC	Transit	IPv6	32
AS52390	Administradora de Redes, S.A.	Unclassified	IPv6	31

Provenance

Where this comes from

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