asn.dev

Observed topology

AS61859 AS61859 - Luup Telecomunicacoes LTDA - ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61859: 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
AS262300SUPER CONNECT TELECOM LTDAResidentialIPv4249
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6140
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv457
AS53202Acesso10 TelecomResidentialIPv4 IPv627
AS1031PEER 1031 LLCUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52543ATL Comercio e Servicos de Informatica LtdaUnclassifiedIPv440

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262300SUPER CONNECT TELECOM LTDAResidentialIPv4249
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6180
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv457
AS52543ATL Comercio e Servicos de Informatica LtdaUnclassifiedIPv440
AS53202Acesso10 TelecomResidentialIPv4 IPv627
AS1031PEER 1031 LLCUnclassifiedIPv44

Provenance

Where this comes from

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