Observed topology
AS265816 AS265816 - DELCO IMAGEN S.A.
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS265816: 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 |
|---|---|---|---|---|
| AS7049 | Silica Networks Argentina S.A. | Unclassified | IPv4 | 679 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 582 |
| AS7303 | Telecom Argentina S.A. | Mobile | IPv4 | 300 |
| AS20207 | Gigared S.A. | Residential | IPv4 | 121 |
| AS22927 | Telefonica de Argentina | Mobile | IPv4 | 59 |
| AS52361 | ARSAT - Empresa Argentina de Soluciones Satelitales S.A. | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS265816 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS27983 | Red Intercable Digital S.A. | Unclassified | IPv4 | 1,633 |
Adjacency
Adjacent networks
Every AS seen directly next to AS265816 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 2,215 |
| AS27983 | Red Intercable Digital S.A. | Unclassified | IPv4 | 1,633 |
| AS7049 | Silica Networks Argentina S.A. | Unclassified | IPv4 | 679 |
| AS7303 | Telecom Argentina S.A. | Mobile | IPv4 | 300 |
| AS20207 | Gigared S.A. | Residential | IPv4 | 121 |
| AS22927 | Telefonica de Argentina | Mobile | IPv4 | 59 |
| AS52361 | ARSAT - Empresa Argentina de Soluciones Satelitales S.A. | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.36M 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.