asn.dev

Observed topology

AS52532 Speednet Telecomunicacoes Ltda ME

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52532: 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
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6248
AS21574Century Telecom LtdaUnclassifiedIPv6174
AS269096N&K TECNOLOGIA LTDAUnclassifiedIPv4 IPv691
AS24482SG.GSHostingIPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26615TIM S/AMobileIPv4177
AS269227P. R. DOS SANTOS SERVICOS DE COM MULT SCMUnclassifiedIPv4 IPv673
AS271072ULTRAFIBRA NET REPRESENTACOES TELECOM EIRELIUnclassifiedIPv616
AS265014GNA TELECOM LTDA - MEUnclassifiedIPv4 IPv65
AS271262COMETAFIBER SERVICOS DE INTERNET LTDAResidentialIPv45

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6454
AS21574Century Telecom LtdaUnclassifiedIPv4 IPv6177
AS26615TIM S/AMobileIPv4177
AS269096N&K TECNOLOGIA LTDAUnclassifiedIPv4 IPv6112
AS269227P. R. DOS SANTOS SERVICOS DE COM MULT SCMUnclassifiedIPv4 IPv673
AS6939Hurricane Electric LLCTransitIPv642
AS271072ULTRAFIBRA NET REPRESENTACOES TELECOM EIRELIUnclassifiedIPv617
AS24482SG.GSHostingIPv4 IPv69
AS265014GNA TELECOM LTDA - MEUnclassifiedIPv4 IPv65
AS271262COMETAFIBER SERVICOS DE INTERNET LTDAResidentialIPv45

All 11 adjacent →

Provenance

Where this comes from

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