asn.dev

Observed topology

AS262199 LIBERTY NETWORKS EL SALVADOR SOCIEDAD ANONIMA DE CAPITAL VARIABLE

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262199: 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
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv61,076

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262179TELENETWORK DE EL SALVADOR , S.A. DE C.V.UnclassifiedIPv4 IPv6454
AS266893MULTIMEDIA NETWORK, S.A. DE C.V.UnclassifiedIPv4 IPv6214

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv61,744
AS262179TELENETWORK DE EL SALVADOR , S.A. DE C.V.UnclassifiedIPv4 IPv6454
AS266893MULTIMEDIA NETWORK, S.A. DE C.V.UnclassifiedIPv4 IPv6214

Provenance

Where this comes from

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