asn.dev

Observed topology

AS263159 BRASTURBO TELECOMUNICACOES LTDA ME

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263159: 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
AS262509AS262509UnclassifiedIPv4 IPv6397
AS6939Hurricane Electric LLCTransitIPv6192
AS28294GIGA MAIS FIBRA TELECOMUNICACOES S.A.UnclassifiedIPv4176
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv6128
AS24482SG.GSHostingIPv4 IPv619

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267430CBR TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6480
AS264574Elite Internet e Servicos LtdaResidentialIPv4 IPv6127
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262509AS262509UnclassifiedIPv4 IPv6854
AS267430CBR TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6480
AS28294GIGA MAIS FIBRA TELECOMUNICACOES S.A.UnclassifiedIPv4 IPv6420
AS264574Elite Internet e Servicos LtdaResidentialIPv4 IPv6267
AS6939Hurricane Electric LLCTransitIPv4 IPv6236
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv6128
AS24482SG.GSHostingIPv4 IPv622
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv41

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.