asn.dev

Observed topology

AS11993 BANCO DO BRASIL S.A.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11993: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6683
AS4230CLARO S.A.ResidentialIPv4 IPv6566
AS10429TELEFONICA BRASIL S.AResidentialIPv4210
AS263558RD TELECOM LTDA -MEResidentialIPv4 IPv6203
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6112
AS14571Oi S.A. - Em Recuperacao JudicialHostingIPv4 IPv657
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv423

Transit

Downstream networks

inferred

Networks for which AS11993 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6683
AS4230CLARO S.A.ResidentialIPv4 IPv6566
AS10429TELEFONICA BRASIL S.AResidentialIPv4210
AS263558RD TELECOM LTDA -MEResidentialIPv4 IPv6203
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6112
AS14571Oi S.A. - Em Recuperacao JudicialHostingIPv4 IPv657
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv423

Provenance

Where this comes from

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