Observed topology
AS61553 AS61553 - CABASE Camara Arg de Base de Datos y Serv en Linea
Unclassified RIPE Non-Profit
Transit
Upstream networks
Networks observed carrying traffic for AS61553: 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 |
|---|---|---|---|---|
| AS52376 | CABASE Camara Arg de Base de Datos y Serv en Linea | Unclassified | IPv4 IPv6 | 93 |
Transit
Downstream networks
Networks for which AS61553 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS265823 | NETROPOLYS S.A. | Unclassified | IPv4 | 112 |
| AS63293 | Facebook, Inc. | Hosting | IPv4 IPv6 | 92 |
| AS267833 | CASELLES COSTA FACUNDO JAVIER (ONPOWER) | Unclassified | IPv4 | 89 |
| AS52371 | XF Comunicaciones S.A. | Unclassified | IPv4 | 69 |
| AS265865 | VEGA CESAR AUGUSTO (I-TIC) | Unclassified | IPv4 IPv6 | 30 |
| AS265676 | INTERSAT S.A. | Residential | IPv4 IPv6 | 29 |
| AS272046 | CATALA SERGIO TADEO (PUYUTA INTERNET & TECNOLOGIA) | Unclassified | IPv4 | 11 |
Adjacency
Adjacent networks
Every AS seen directly next to AS61553 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 405 |
| AS52376 | CABASE Camara Arg de Base de Datos y Serv en Linea | Unclassified | IPv4 IPv6 | 158 |
| AS265823 | NETROPOLYS S.A. | Unclassified | IPv4 | 150 |
| AS63293 | Facebook, Inc. | Hosting | IPv4 IPv6 | 92 |
| AS267833 | CASELLES COSTA FACUNDO JAVIER (ONPOWER) | Unclassified | IPv4 | 89 |
| AS52371 | XF Comunicaciones S.A. | Unclassified | IPv4 | 69 |
| AS265865 | VEGA CESAR AUGUSTO (I-TIC) | Unclassified | IPv4 IPv6 | 30 |
| AS265676 | INTERSAT S.A. | Residential | IPv4 IPv6 | 29 |
| AS272046 | CATALA SERGIO TADEO (PUYUTA INTERNET & TECNOLOGIA) | Unclassified | IPv4 | 11 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.