asn.dev

Observed topology

AS2715 Fundacao Carlos Chagas Filho de Amparo a Pesquisa

Education RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2715: 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 IPv63,194
AS6939Hurricane Electric LLCTransitIPv4561

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS21612FUNDACAO INSTITUTO OSWALDO CRUZUnclassifiedIPv4868
AS262829Assoc do Inst Nac de Matematica Pura e AplicadaUnclassifiedIPv462
AS61585MINISTERIO DA SAUDE - INSTITUTO NACIONAL DE CANCERUnclassifiedIPv455

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1916Rede Nacional de Ensino e PesquisaUnclassifiedIPv4 IPv64,188
AS21612FUNDACAO INSTITUTO OSWALDO CRUZUnclassifiedIPv4868
AS6939Hurricane Electric LLCTransitIPv4571
AS262829Assoc do Inst Nac de Matematica Pura e AplicadaUnclassifiedIPv462
AS61585MINISTERIO DA SAUDE - INSTITUTO NACIONAL DE CANCERUnclassifiedIPv455
AS26162Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv419

Provenance

Where this comes from

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