asn.dev

Observed topology

AS19889 AS19889 - Cooperativa Telefonica Del Viso

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS19889: 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 IPv64,173
AS6939Hurricane Electric LLCTransitIPv4 IPv62,246
AS16814NSS S.A.UnclassifiedIPv4 IPv61,391

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52491Cooperativa de Servicios Publicos de Fatima Ltda.UnclassifiedIPv4219
AS263768EUROSAT S.A.UnclassifiedIPv492
AS269881CAMARA DE COOPERATIVAS DE TELECOMUNICACIONES (CATEL)UnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv64,429
AS6939Hurricane Electric LLCTransitIPv4 IPv62,297
AS16814NSS S.A.UnclassifiedIPv4 IPv61,456
AS52491Cooperativa de Servicios Publicos de Fatima Ltda.UnclassifiedIPv4219
AS263768EUROSAT S.A.UnclassifiedIPv492
AS269881CAMARA DE COOPERATIVAS DE TELECOMUNICACIONES (CATEL)UnclassifiedIPv461

Provenance

Where this comes from

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