Observed topology
AS272988 AS272988 - Hydra Soluciones Empresariales Ingenieria SAS
Unclassified APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS272988: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS262589 | SAMM TECNOLOGIA E TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 113 |
| AS3549 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 69 |
| AS262186 | TV AZTECA SUCURSAL COLOMBIA | Residential | IPv4 | 61 |
| AS3816 | COLOMBIA TELECOMUNICACIONES S.A. ESP BIC | Residential | IPv4 | 59 |
| AS18678 | INTERNEXA S.A. E.S.P | Unclassified | IPv4 IPv6 | 18 |
| AS267708 | SP SISTEMAS PALACIOS LTDA | Unclassified | IPv4 IPv6 | 11 |
Transit
Downstream networks
Networks for which AS272988 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS273020 | IN QUALITY TELECOMUNICATIONS S.A.S. ZOMAC BIC | Unclassified | IPv4 | 64 |
Adjacency
Adjacent networks
Every AS seen directly next to AS272988 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3549 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 132 |
| AS262589 | SAMM TECNOLOGIA E TELECOMUNICACOES S.A | Unclassified | IPv4 IPv6 | 113 |
| AS273020 | IN QUALITY TELECOMUNICATIONS S.A.S. ZOMAC BIC | Unclassified | IPv4 | 64 |
| AS262186 | TV AZTECA SUCURSAL COLOMBIA | Residential | IPv4 | 61 |
| AS3816 | COLOMBIA TELECOMUNICACIONES S.A. ESP BIC | Residential | IPv4 | 60 |
| AS18678 | INTERNEXA S.A. E.S.P | Unclassified | IPv4 IPv6 | 18 |
| AS267708 | SP SISTEMAS PALACIOS LTDA | Unclassified | IPv4 IPv6 | 11 |
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.