asn.dev

Observed topology

AS52913 PLANALTO NET

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52913: 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
AS3356Level 3 Parent, LLCTransitIPv41,900
AS266302RENOVENET TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv6745
AS6939Hurricane Electric LLCTransitIPv4 IPv6591
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6416
AS24482SG.GSHostingIPv4 IPv662
AS37721Virtual Technologies & SolutionsResidentialIPv431
AS35280F5 Networks SARLHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52819Placido e Andrade LTDAUnclassifiedIPv4112

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv41,900
AS266302RENOVENET TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv6819
AS6939Hurricane Electric LLCTransitIPv4 IPv6591
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6454
AS52819Placido e Andrade LTDAUnclassifiedIPv4112
AS24482SG.GSHostingIPv4 IPv662
AS37721Virtual Technologies & SolutionsResidentialIPv431
AS35280F5 Networks SARLHostingIPv44

Provenance

Where this comes from

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