asn.dev

Observed topology

AS265662 TLINK SPA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265662: 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
AS263702ZGH SPAHostingIPv4 IPv671
AS174Cogent Communications, LLCTransitIPv4 IPv668
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269988NETWORKING DATA LIMITADAUnclassifiedIPv4312
AS64131SPAResidentialIPv4 IPv6127
AS267733SMARTNET LIMITADAUnclassifiedIPv458
AS266844TELECOMUNICACIONES SPAResidentialIPv453
AS266776CONSULTORES EN INFORMATICA VARGAS Y COMPANIA LIMITADAUnclassifiedIPv416

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263702ZGH SPAHostingIPv4 IPv6363
AS269988NETWORKING DATA LIMITADAUnclassifiedIPv4363
AS174Cogent Communications, LLCTransitIPv4 IPv6299
AS64131SPAResidentialIPv4 IPv6127
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv6106
AS267733SMARTNET LIMITADAUnclassifiedIPv458
AS266844TELECOMUNICACIONES SPAResidentialIPv453
AS266776CONSULTORES EN INFORMATICA VARGAS Y COMPANIA LIMITADAUnclassifiedIPv416

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.