asn.dev

Observed topology

AS22047 AS22047 - VTR BANDA ANCHA S.A.

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22047: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv66,989
AS27978Telmex Servicios Empresariales S.A.UnclassifiedIPv46,654
AS174Cogent Communications, LLCTransitIPv45,184
AS6939Hurricane Electric LLCTransitIPv4 IPv6168

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273019DIRECTV CHILE TELEVISION LIMITADAUnclassifiedIPv4177

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv615,741
AS27978Telmex Servicios Empresariales S.A.UnclassifiedIPv415,232
AS174Cogent Communications, LLCTransitIPv45,187
AS273019DIRECTV CHILE TELEVISION LIMITADAUnclassifiedIPv4177
AS6939Hurricane Electric LLCTransitIPv4 IPv6168

Provenance

Where this comes from

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