asn.dev

Observed topology

AS264758 ISP GROUP SRL

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264758: 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
AS22927Telefonica de ArgentinaMobileIPv4 IPv61,559
AS7049Silica Networks Argentina S.A.UnclassifiedIPv4174
AS27951Media Commerce Partners S.AResidentialIPv458

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263726Red Uno SRLResidentialIPv4 IPv6418
AS265673LISANDRO POZZO ARDIZZIUnclassifiedIPv4177
AS272843Rio Colorado Television S.A.UnclassifiedIPv4119
AS264697LEWTEL SRLResidentialIPv480
AS270053VILLEGAS BRAIAN JOEL (MADRYNET)UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS22927Telefonica de ArgentinaMobileIPv4 IPv62,444
AS263726Red Uno SRLResidentialIPv4 IPv6418
AS265673LISANDRO POZZO ARDIZZIUnclassifiedIPv4177
AS7049Silica Networks Argentina S.A.UnclassifiedIPv4174
AS272843Rio Colorado Television S.A.UnclassifiedIPv4119
AS264697LEWTEL SRLResidentialIPv480
AS270053VILLEGAS BRAIAN JOEL (MADRYNET)UnclassifiedIPv459
AS27951Media Commerce Partners S.AResidentialIPv458
AS52500CABASE Camara Arg de Base de Datos y Serv en LineaUnclassifiedIPv432

Provenance

Where this comes from

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