asn.dev

Observed topology

AS28509 Cablemas Telecomunicaciones SA de CV

Unclassified ARIN

Upstreams 5 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 5
Upstream graph Who carries AS28509, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS28509 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28509: 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.

ASNetworkTypeFamiliesPaths seen
AS18734Operbes, S.A. de C.V.UnclassifiedIPv4 IPv612,997
AS174Cogent Communications, LLCTransitIPv4 IPv65,784
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv62,681
AS32098Transtelco IncUnclassifiedIPv4 IPv62,473
AS28545Cablemas Telecomunicaciones SA de CVUnclassifiedIPv4 IPv61,357

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11888Television Internacional, S.A. de C.V.ResidentialIPv4115

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS18734Operbes, S.A. de C.V.UnclassifiedIPv4 IPv612,997
AS174Cogent Communications, LLCTransitIPv4 IPv65,819
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv62,697
AS32098Transtelco IncUnclassifiedIPv4 IPv62,539
AS28545Cablemas Telecomunicaciones SA de CVUnclassifiedIPv4 IPv61,357
AS11888Television Internacional, S.A. de C.V.ResidentialIPv4115

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.