asn.dev

Observed topology

AS14522 SERVICIOS DE TELECOMUNICACIONES SETEL S.A. XTRIM EC

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14522: 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
AS1299Arelion Sweden ABTransitIPv4 IPv67,827
AS3356Level 3 Parent, LLCTransitIPv4 IPv64,877
AS22724PUNTONET S.A.MobileIPv4 IPv62,159
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv61,060
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv61,003
AS174Cogent Communications, LLCTransitIPv4 IPv6421
AS3549Level 3 Parent, LLCTransitIPv4169

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52458WISP INTERNET ECUADORResidentialIPv4 IPv6910
AS22724PUNTONET S.A.MobileIPv4452
AS272022ZAPPING SPAHostingIPv4118
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv690

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv68,608
AS3356Level 3 Parent, LLCTransitIPv4 IPv64,877
AS22724PUNTONET S.A.MobileIPv4 IPv62,894
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv61,076
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv61,060
AS174Cogent Communications, LLCTransitIPv4 IPv6950
AS52458WISP INTERNET ECUADORResidentialIPv4 IPv6910
AS3549Level 3 Parent, LLCTransitIPv4169
AS272022ZAPPING SPAHostingIPv4118
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv690

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.