Observed topology

AS264635 AS264635 - CONECTIVE S.A. DE C.V.

Unclassified LACNIC Cable/DSL/ISP

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264635: 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
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4 IPv6	258
AS27729	Globalnet.hn	Unclassified	IPv4	181
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4	80
AS273189	CA NETWORK S.A. DE C.V.	Unclassified	IPv4 IPv6	50

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS267860	UNIVERSIDAD DE ORIENTE	Unclassified	IPv4	236
AS265811	UNIVERSIDAD CAPITAN GENERAL GERARDO BARRIOS	Unclassified	IPv4 IPv6	150

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS273189	CA NETWORK S.A. DE C.V.	Unclassified	IPv4 IPv6	430
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4 IPv6	258
AS267860	UNIVERSIDAD DE ORIENTE	Unclassified	IPv4	236
AS27729	Globalnet.hn	Unclassified	IPv4	187
AS265811	UNIVERSIDAD CAPITAN GENERAL GERARDO BARRIOS	Unclassified	IPv4 IPv6	150
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4	80

Provenance

Where this comes from

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