asn.dev

Observed topology

AS52545 BJ NET Provedor de Internet Ltda. - ME

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52545: 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
AS2914NTT America, Inc.TransitIPv4 IPv6336
AS6939Hurricane Electric LLCTransitIPv4 IPv6267
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6259
AS174Cogent Communications, LLCTransitIPv4 IPv6105
AS24482SG.GSHostingIPv4 IPv622
AS37721Virtual Technologies & SolutionsResidentialIPv610
AS35280F5 Networks SARLHostingIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270504Gera-Net Provedor de AcessoUnclassifiedIPv4 IPv6153
AS272220Prefeitura Municipal de BrusqueUnclassifiedIPv675
AS267353Porto Franco TIUnclassifiedIPv4 IPv651

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6422
AS6939Hurricane Electric LLCTransitIPv4 IPv6377
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6320
AS270504Gera-Net Provedor de AcessoUnclassifiedIPv4 IPv6153
AS174Cogent Communications, LLCTransitIPv4 IPv6105
AS272220Prefeitura Municipal de BrusqueUnclassifiedIPv675
AS267353Porto Franco TIUnclassifiedIPv4 IPv651
AS24482SG.GSHostingIPv4 IPv630
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv617
AS35280F5 Networks SARLHostingIPv4 IPv66

All 11 adjacent →

Provenance

Where this comes from

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