Observed topology

AS7438 PEGASO PCS

Residential LACNIC

Upstreams 3 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7438: 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
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4 IPv6	5,782
AS32098	Transtelco Inc	Unclassified	IPv4 IPv6	1,786
AS8151	UNINET	Mobile	IPv4	12

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS265605	VELOCOM SA DE CV	Hosting	IPv4 IPv6	839
AS28409	ENI NETWORKS SAPI de CV	Unclassified	IPv4	191
AS136907	HUAWEI CLOUDS	Hosting	IPv4	138
AS265535	Wibo SA de CV	Unclassified	IPv4	59
AS265607	CONECTARED SA DE CV	Unclassified	IPv4	59
AS265592	KBLEX SA DE CV	Unclassified	IPv4 IPv6	55
AS262926	BRADESCARD MEXICO S DE RL	Unclassified	IPv4	11

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4 IPv6	7,009
AS32098	Transtelco Inc	Unclassified	IPv4 IPv6	1,911
AS265605	VELOCOM SA DE CV	Hosting	IPv4 IPv6	839
AS28409	ENI NETWORKS SAPI de CV	Unclassified	IPv4	191
AS136907	HUAWEI CLOUDS	Hosting	IPv4	138
AS265535	Wibo SA de CV	Unclassified	IPv4	59
AS265607	CONECTARED SA DE CV	Unclassified	IPv4	59
AS265592	KBLEX SA DE CV	Unclassified	IPv4 IPv6	55
AS8151	UNINET	Mobile	IPv4	12
AS262926	BRADESCARD MEXICO S DE RL	Unclassified	IPv4	11

Provenance

Where this comes from

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