asn.dev

Observed topology

AS270207 JOSE DE JESUS VAZQUEZ PONCE

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270207: 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
AS13999Mega Cable, S.A. de C.V.UnclassifiedIPv4351
AS174Cogent Communications, LLCTransitIPv4 IPv6264
AS32098Transtelco IncUnclassifiedIPv4 IPv696
AS11172Alestra, S. de R.L. de C.V.UnclassifiedIPv4 IPv690
AS18734Operbes, S.A. de C.V.UnclassifiedIPv459
AS28458IENTC S DE RL DE CVUnclassifiedIPv459
AS265605VELOCOM SA DE CVHostingIPv459
AS28435JAVIER TAMAYO GARCIAUnclassifiedIPv458
AS52468UFINET PANAMA S.A.UnclassifiedIPv458

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13999Mega Cable, S.A. de C.V.UnclassifiedIPv4351
AS174Cogent Communications, LLCTransitIPv4 IPv6264
AS32098Transtelco IncUnclassifiedIPv4 IPv696
AS11172Alestra, S. de R.L. de C.V.UnclassifiedIPv4 IPv690
AS18734Operbes, S.A. de C.V.UnclassifiedIPv459
AS28458IENTC S DE RL DE CVUnclassifiedIPv459
AS265605VELOCOM SA DE CVHostingIPv459
AS28435JAVIER TAMAYO GARCIAUnclassifiedIPv458
AS52468UFINET PANAMA S.A.UnclassifiedIPv458

Provenance

Where this comes from

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