asn.dev

Observed topology

AS61744 AS61744 - power net telecom eireli-me

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61744: 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
AS52974Henet Telecomunicacoes LtdaResidentialIPv4 IPv694
AS266094CONEXAO MB E TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv693
AS26863373s TelecomUnclassifiedIPv462
AS53180INFORTEL COMUNICACOES LTDAResidentialIPv459
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270999INFONET RIOUnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS266094CONEXAO MB E TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv6182
AS52974Henet Telecomunicacoes LtdaResidentialIPv4 IPv694
AS270999INFONET RIOUnclassifiedIPv4 IPv693
AS26863373s TelecomUnclassifiedIPv462
AS53180INFORTEL COMUNICACOES LTDAResidentialIPv459
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS35280F5 Networks SARLHostingIPv4 IPv64

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.