asn.dev

Observed topology

AS52931 AS52931 - Netvip Telecomunicacoes Ltda

Unclassified LACNIC

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS52931: 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
AS52838WN TELECOM LTDA - MEUnclassifiedIPv4 IPv6633
AS269182PLUGAR TELECOMUnclassifiedIPv499
AS28173Dinamica Telecomunicacoes LtdaUnclassifiedIPv4 IPv694
AS269194ST1 INTERNETResidentialIPv4 IPv694
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv683
AS14840BR.Digital TelecomUnclassifiedIPv455
AS265482NET EXPRESS BRASIL LTDA - MEResidentialIPv632
AS271612LOGO TelecomUnclassifiedIPv632
AS262839Yawl Telecomunicacao e Rep. de Informatica Ltda.ResidentialIPv422
AS6939Hurricane Electric LLCTransitIPv410

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS52838WN TELECOM LTDA - MEUnclassifiedIPv4 IPv6633
AS269182PLUGAR TELECOMUnclassifiedIPv499
AS28173Dinamica Telecomunicacoes LtdaUnclassifiedIPv4 IPv694
AS269194ST1 INTERNETResidentialIPv4 IPv694
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv683
AS14840BR.Digital TelecomUnclassifiedIPv455
AS265482NET EXPRESS BRASIL LTDA - MEResidentialIPv632
AS271612LOGO TelecomUnclassifiedIPv632
AS262839Yawl Telecomunicacao e Rep. de Informatica Ltda.ResidentialIPv422
AS6939Hurricane Electric LLCTransitIPv410

Provenance

Where this comes from

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