asn.dev

Observed topology

AS52935 Infobarra Solucoes em Informatica Ltda

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52935: 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
AS52564Biazi TelecomResidentialIPv4 IPv6880
AS52573Une Telecom LtdaResidentialIPv4 IPv6572

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263371Intervia Solucoes LtdaUnclassifiedIPv4 IPv6330
AS270384OTILIA ANTONIA CELSOUnclassifiedIPv460
AS273379V. M. De Melo Informatica - MIDIA INFORMATICAUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52564Biazi TelecomResidentialIPv4 IPv61,078
AS52573Une Telecom LtdaResidentialIPv4 IPv6842
AS263371Intervia Solucoes LtdaUnclassifiedIPv4 IPv6391
AS270384OTILIA ANTONIA CELSOUnclassifiedIPv460
AS273379V. M. De Melo Informatica - MIDIA INFORMATICAUnclassifiedIPv41

Provenance

Where this comes from

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