asn.dev

Observed topology

AS52544 AS52544 - Ivatel Redes e Internet LTDA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52544: 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
AS262355VSX NetworksUnclassifiedIPv4 IPv6803
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6206
AS53115ISPX Solucoes em Telecomunicacoes SPE LtdaUnclassifiedIPv433

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270626DOMINION UAULL NET TEC DE CON INTELIGENTES LTDAUnclassifiedIPv4130
AS264909BRConnect Telecomunicacoes LTDAUnclassifiedIPv4 IPv639
AS268443GUILHERME ZANINELO MULTIMIDIAUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262355VSX NetworksUnclassifiedIPv4 IPv6924
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6255
AS270626DOMINION UAULL NET TEC DE CON INTELIGENTES LTDAUnclassifiedIPv4130
AS264909BRConnect Telecomunicacoes LTDAUnclassifiedIPv4 IPv649
AS53115ISPX Solucoes em Telecomunicacoes SPE LtdaUnclassifiedIPv443
AS268443GUILHERME ZANINELO MULTIMIDIAUnclassifiedIPv41

Provenance

Where this comes from

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