Observed topology

AS265535 AS265535 - Wibo SA de CV

Unclassified ARIN

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265535: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	155
AS32098	Transtelco Inc	Unclassified	IPv4 IPv6	123
AS11172	Alestra, S. de R.L. de C.V.	Unclassified	IPv4	118
AS7438	PEGASO PCS	Residential	IPv4	60

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS270139	KIUBIX, SA de CV	Unclassified	IPv4	120
AS273289	FRARED SOLUCIONES DIGITALES	Unclassified	IPv6	32

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS32098	Transtelco Inc	Unclassified	IPv4 IPv6	246
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	184
AS270139	KIUBIX, SA de CV	Unclassified	IPv4	120
AS11172	Alestra, S. de R.L. de C.V.	Unclassified	IPv4	118
AS7438	PEGASO PCS	Residential	IPv4	60
AS273289	FRARED SOLUCIONES DIGITALES	Unclassified	IPv6	32

Provenance

Where this comes from

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