asn.dev

Observed topology

AS61944 AS61944 - FFA SOLUCOES TECNOLOGICAS LTDA - ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61944: 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
AS265311Bezerra Speed InternetResidentialIPv4 IPv6395
AS6939Hurricane Electric LLCTransitIPv66
AS262642NETCELL TELECOMResidentialIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269021J.R.DA SILVA TELECOM -MEUnclassifiedIPv4 IPv6324
AS267021Bruno Luiz de Moura - MEUnclassifiedIPv4 IPv6272
AS267108ROTA SERVICOS EM TELECOMUNICACOESUnclassifiedIPv6132
AS268112JAIRO ALMEIDA DA SILVA MEUnclassifiedIPv648

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265311Bezerra Speed InternetResidentialIPv4 IPv6667
AS262642NETCELL TELECOMResidentialIPv4 IPv6376
AS269021J.R.DA SILVA TELECOM -MEUnclassifiedIPv4 IPv6324
AS267021Bruno Luiz de Moura - MEUnclassifiedIPv4 IPv6272
AS268112JAIRO ALMEIDA DA SILVA MEUnclassifiedIPv6180
AS267108ROTA SERVICOS EM TELECOMUNICACOESUnclassifiedIPv6132
AS6939Hurricane Electric LLCTransitIPv66

Provenance

Where this comes from

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