asn.dev

Observed topology

AS61495 CABASE Camara Arg de Base de Datos y Serv en Linea

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61495: 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
AS52376CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv694

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52314Universidad Nacional del Noroeste de Buenos Aires (UNNOBA)UnclassifiedIPv4 IPv626
AS52255Grupo Servicios Junin S.A.ResidentialIPv618
AS52349Young S.A.UnclassifiedIPv415
AS264695MUNICIPALIDAD DE JUNINUnclassifiedIPv411
AS263790RED POWER INTERNET SRLResidentialIPv49
AS267808Empresa de Servicios de TV por Cable SAUnclassifiedIPv49

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52376CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv4 IPv694
AS6939Hurricane Electric LLCTransitIPv4 IPv688
AS52314Universidad Nacional del Noroeste de Buenos Aires (UNNOBA)UnclassifiedIPv4 IPv626
AS52255Grupo Servicios Junin S.A.ResidentialIPv618
AS52349Young S.A.UnclassifiedIPv415
AS264695MUNICIPALIDAD DE JUNINUnclassifiedIPv411
AS263790RED POWER INTERNET SRLResidentialIPv49
AS267808Empresa de Servicios de TV por Cable SAUnclassifiedIPv49

Provenance

Where this comes from

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