asn.dev

Observed topology

AS52626 NovaNet Provedor e Web Ltda

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52626: 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
AS4230CLARO S.A.ResidentialIPv4 IPv6511
AS267059NETVIP MTResidentialIPv4441
AS263650Clicfacil TelecomUnclassifiedIPv4 IPv6192

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267393ACCESS INTERNETUnclassifiedIPv4 IPv6358
AS267059NETVIP MTResidentialIPv4 IPv6115
AS268640M REGINA O DA SILVA LTDAUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv62,470
AS267059NETVIP MTResidentialIPv4 IPv61,841
AS267393ACCESS INTERNETUnclassifiedIPv4 IPv6358
AS266337MARLON LIMA GOMES MEUnclassifiedIPv4 IPv6244
AS263650Clicfacil TelecomUnclassifiedIPv4 IPv6192
AS268640M REGINA O DA SILVA LTDAUnclassifiedIPv461

Provenance

Where this comes from

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