asn.dev

Observed topology

AS269087 AS269087 - netcabo servicos de comunicacao

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269087: 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
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4117
AS264221ONLINE NORTE TELECOM LTDAUnclassifiedIPv4 IPv6107
AS26615TIM S/AMobileIPv4 IPv639
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv48
AS28368unnamedResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262887RAPIX INTERNETResidentialIPv4342

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262887RAPIX INTERNETResidentialIPv4342
AS264221ONLINE NORTE TELECOM LTDAUnclassifiedIPv4 IPv6323
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4134
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4117
AS26615TIM S/AMobileIPv4 IPv639
AS28368unnamedResidentialIPv42

Provenance

Where this comes from

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