asn.dev

Observed topology

AS52947 PARAOPEBANET PROVEDOR LTDA

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52947: 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
AS269096N&K TECNOLOGIA LTDAUnclassifiedIPv4 IPv6368
AS6939Hurricane Electric LLCTransitIPv4 IPv6167
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6163
AS21574Century Telecom LtdaUnclassifiedIPv4108
AS24482SG.GSHostingIPv4 IPv615
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61707SYSVOIP TELECOMUNICACOES LTDA - MEUnclassifiedIPv478

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269096N&K TECNOLOGIA LTDAUnclassifiedIPv4 IPv6368
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6226
AS6939Hurricane Electric LLCTransitIPv4 IPv6167
AS21574Century Telecom LtdaUnclassifiedIPv4108
AS61707SYSVOIP TELECOMUNICACOES LTDA - MEUnclassifiedIPv478
AS24482SG.GSHostingIPv4 IPv615
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv415
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.