asn.dev

Observed topology

AS52612 AS52612 - Alt Informatica Ltda

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52612: 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
AS28202MASTER S/AUnclassifiedIPv4 IPv6174
AS262476PROVEDOR BRCENTRAL.NET LTDAResidentialIPv4 IPv6159
AS271328RL QUEIROZ DA SILVA PROVEDOR DE INTERNETResidentialIPv4 IPv692
AS52531G6 InternetUnclassifiedIPv477
AS270538MEGA CONNECT SERVICOS ESPECIAIS LTDA.UnclassifiedIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269018FIBER NET LTDA - MEUnclassifiedIPv451
AS264557Vale & Vale Telecomunicacoes Ltda - MEUnclassifiedIPv4 IPv633
AS274469CONNECTBR TELECOMUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28202MASTER S/AUnclassifiedIPv4 IPv6201
AS262476PROVEDOR BRCENTRAL.NET LTDAResidentialIPv4 IPv6159
AS52531G6 InternetUnclassifiedIPv4 IPv6135
AS271328RL QUEIROZ DA SILVA PROVEDOR DE INTERNETResidentialIPv4 IPv692
AS270538MEGA CONNECT SERVICOS ESPECIAIS LTDA.UnclassifiedIPv460
AS269018FIBER NET LTDA - MEUnclassifiedIPv451
AS264557Vale & Vale Telecomunicacoes Ltda - MEUnclassifiedIPv4 IPv633
AS274469CONNECTBR TELECOMUnclassifiedIPv41

Provenance

Where this comes from

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