asn.dev

Observed topology

AS19422 Telefonica Moviles del Uruguay SA

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS19422: 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
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv62,431

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28000LACNIC - Latin American and Caribbean IP addressUnclassifiedIPv4 IPv6304
AS61442PASWER INTERNATIONAL S.A.UnclassifiedIPv4300
AS18667Web2mil S.AUnclassifiedIPv4180
AS274012TIME TOWER S.A.UnclassifiedIPv4 IPv6124
AS266886HOSTING EN LA WEB S.A.S.UnclassifiedIPv4 IPv692
AS273115PRAIAMAR SAUnclassifiedIPv4 IPv692
AS52366Lunamen S.A.UnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv63,583
AS28000LACNIC - Latin American and Caribbean IP addressUnclassifiedIPv4 IPv6304
AS61442PASWER INTERNATIONAL S.A.UnclassifiedIPv4300
AS18667Web2mil S.AUnclassifiedIPv4180
AS274012TIME TOWER S.A.UnclassifiedIPv4 IPv6124
AS266886HOSTING EN LA WEB S.A.S.UnclassifiedIPv4 IPv692
AS273115PRAIAMAR SAUnclassifiedIPv4 IPv692
AS52366Lunamen S.A.UnclassifiedIPv460

Provenance

Where this comes from

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