asn.dev

Observed topology

AS269641 AS269641 - RURALNET BRASIL

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269641: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,187
AS263152MIGO TELECOMResidentialIPv4 IPv6451
AS262493AS262493UnclassifiedIPv673
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv460
AS24482SG.GSHostingIPv4 IPv642

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264911POWERNET TELECOMUnclassifiedIPv4 IPv6425
AS272281Workeng.Net TelecomUnclassifiedIPv4 IPv695

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,265
AS263152MIGO TELECOMResidentialIPv4 IPv6892
AS264911POWERNET TELECOMUnclassifiedIPv4 IPv6425
AS272281Workeng.Net TelecomUnclassifiedIPv4 IPv695
AS262493AS262493UnclassifiedIPv673
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv460
AS24482SG.GSHostingIPv4 IPv643

Provenance

Where this comes from

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