asn.dev

Observed topology

AS52888 UNIVERSIDADE FEDERAL DE SAO CARLOS

Education LACNIC Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52888: 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
AS1916Rede Nacional de Ensino e PesquisaUnclassifiedIPv4 IPv61,054
AS1251FUNDACAO DE AMPARO A PESQUISA DO ESTADO SAO PAULOUnclassifiedIPv4 IPv6113
AS6939Hurricane Electric LLCTransitIPv4 IPv6106
AS24482SG.GSHostingIPv4 IPv625
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv624
AS35280F5 Networks SARLHostingIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11097EMPRESA BRASILEIRA DE PESQUISA AGROPECUARIAUnclassifiedIPv4 IPv6187

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1916Rede Nacional de Ensino e PesquisaUnclassifiedIPv4 IPv61,236
AS11097EMPRESA BRASILEIRA DE PESQUISA AGROPECUARIAUnclassifiedIPv4 IPv6187
AS1251FUNDACAO DE AMPARO A PESQUISA DO ESTADO SAO PAULOUnclassifiedIPv4 IPv6113
AS6939Hurricane Electric LLCTransitIPv4 IPv6106
AS24482SG.GSHostingIPv4 IPv628
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv626
AS35280F5 Networks SARLHostingIPv4 IPv612

Provenance

Where this comes from

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