asn.dev

Observed topology

AS52843 AS52843 - Magnos A. Both e Cia Ltda

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52843: 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
AS28343UNIFIQUE TELECOMUNICACOES S/AUnclassifiedIPv4 IPv6924
AS61666GLOBOINFO LTDAResidentialIPv4 IPv615

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270667Omega Tech InternetUnclassifiedIPv4 IPv6447
AS270272ZIRR & HEIMERDINGER LTDAUnclassifiedIPv4 IPv6437
AS267257IdealNET TelecomUnclassifiedIPv4 IPv6211
AS61653Meta Servers Tecnologia e Telecomunicacaoes LtdaUnclassifiedIPv4 IPv6180

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28343UNIFIQUE TELECOMUNICACOES S/AUnclassifiedIPv4 IPv62,186
AS270667Omega Tech InternetUnclassifiedIPv4 IPv6447
AS270272ZIRR & HEIMERDINGER LTDAUnclassifiedIPv4 IPv6437
AS267257IdealNET TelecomUnclassifiedIPv4 IPv6211
AS61653Meta Servers Tecnologia e Telecomunicacaoes LtdaUnclassifiedIPv4 IPv6180
AS61666GLOBOINFO LTDAResidentialIPv4 IPv628

Provenance

Where this comes from

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