asn.dev

Observed topology

AS61732 AS61732 - PRECISA INTERNET E COMUNICACAO LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61732: 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
AS61622VIA MS SOLUCOES DIGITAISUnclassifiedIPv4 IPv684
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv665
AS24482SG.GSHostingIPv4 IPv69
AS35280F5 Networks SARLHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262873VETT - VIA EXPRESS TECNOLOGIA E TELECOMUNICACOESUnclassifiedIPv4 IPv6406
AS265887R W TELECOMUNICACOES LTDA MEUnclassifiedIPv4 IPv6288
AS275858VAAVI135UnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262873VETT - VIA EXPRESS TECNOLOGIA E TELECOMUNICACOESUnclassifiedIPv4 IPv6532
AS61622VIA MS SOLUCOES DIGITAISUnclassifiedIPv4 IPv6498
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6464
AS265887R W TELECOMUNICACOES LTDA MEUnclassifiedIPv4 IPv6288
AS1031PEER 1031 LLCUnclassifiedIPv432
AS275858VAAVI135UnclassifiedIPv632
AS24482SG.GSHostingIPv4 IPv616
AS35280F5 Networks SARLHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66

Provenance

Where this comes from

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