asn.dev

Observed topology

AS28435 JAVIER TAMAYO GARCIA

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28435: 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
AS265586SA DE CVResidentialIPv4 IPv6378
AS3356Level 3 Parent, LLCTransitIPv4 IPv6376
AS28458S DE RL DE CVUnclassifiedIPv4 IPv6371
AS7195S.A.SUnclassifiedIPv432

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265583Y SOLUCIONES DE CAMPECHE SAS DE CVUnclassifiedIPv4 IPv6213
AS265599GARCIA RAMIREZUnclassifiedIPv4171
AS265580de Mexico, S.A. de C.V.UnclassifiedIPv4 IPv694
AS270207JE S. DE R.L. DE C.V.UnclassifiedIPv460
AS272339CONVERGENTE ARZOLAUnclassifiedIPv460
AS273308chable PalomequeUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6512
AS7195S.A.SUnclassifiedIPv4 IPv6488
AS28458S DE RL DE CVUnclassifiedIPv4 IPv6437
AS265586SA DE CVResidentialIPv4 IPv6378
AS265583Y SOLUCIONES DE CAMPECHE SAS DE CVUnclassifiedIPv4 IPv6213
AS265599GARCIA RAMIREZUnclassifiedIPv4171
AS265580de Mexico, S.A. de C.V.UnclassifiedIPv4 IPv694
AS270207JE S. DE R.L. DE C.V.UnclassifiedIPv460
AS272339CONVERGENTE ARZOLAUnclassifiedIPv460
AS273308chable PalomequeUnclassifiedIPv460

Provenance

Where this comes from

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