asn.dev

Observed topology

AS52507 Pampacom S.R.L.

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52507: 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
AS52444Pogliotti & Pogliotti Construcciones S.A.ResidentialIPv4 IPv6390

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264643Enredes S.A.UnclassifiedIPv4590
AS264776Omar Anselmo Ripoll (TDC NET)UnclassifiedIPv4 IPv6345
AS272039COOPERATIVA DE OBRAS Y SERVICIOS PUBLICOS Y VIVIENDAS DE BIGAND LTDAUnclassifiedIPv4118
AS267731COOPERATIVA DE ELECTRICIDAD SERVICIOS PUBLICOS VIVIENDA Y CREDITO DE V CANAS LTDUnclassifiedIPv4 IPv6117
AS271914SEMPRINI EMILIANO EFRENUnclassifiedIPv4 IPv660

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52444Pogliotti & Pogliotti Construcciones S.A.ResidentialIPv4 IPv61,620
AS264643Enredes S.A.UnclassifiedIPv4590
AS264776Omar Anselmo Ripoll (TDC NET)UnclassifiedIPv4 IPv6345
AS272039COOPERATIVA DE OBRAS Y SERVICIOS PUBLICOS Y VIVIENDAS DE BIGAND LTDAUnclassifiedIPv4118
AS267731COOPERATIVA DE ELECTRICIDAD SERVICIOS PUBLICOS VIVIENDA Y CREDITO DE V CANAS LTDUnclassifiedIPv4 IPv6117
AS271914SEMPRINI EMILIANO EFRENUnclassifiedIPv4 IPv660

Provenance

Where this comes from

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