asn.dev

Observed topology

AS269423 AS269423 - NETNOAR TELECOM

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269423: 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
AS269194ST1 INTERNETResidentialIPv4 IPv664
AS7738V talUnclassifiedIPv4 IPv631

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270756ILAILDO SILVA DO NASCIMENTOUnclassifiedIPv4 IPv6279
AS271175ARACAGYNET LTDAResidentialIPv4 IPv6190
AS271725T BRENO PEREIRA ASSUNCAOUnclassifiedIPv4 IPv6156
AS271685INTERNET D+.COM LTDAUnclassifiedIPv4 IPv688
AS270265VAVATEC TELECOMUNICACOESUnclassifiedIPv456
AS271612LOGO TelecomUnclassifiedIPv639
AS272191BNJ COMUNICACAO E SERVICOS LTDAUnclassifiedIPv633
AS271315Netfusion Internet LTDAUnclassifiedIPv430

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7738V talUnclassifiedIPv4 IPv6807
AS270756ILAILDO SILVA DO NASCIMENTOUnclassifiedIPv4 IPv6279
AS269194ST1 INTERNETResidentialIPv4 IPv6240
AS271175ARACAGYNET LTDAResidentialIPv4 IPv6190
AS271725T BRENO PEREIRA ASSUNCAOUnclassifiedIPv4 IPv6156
AS272191BNJ COMUNICACAO E SERVICOS LTDAUnclassifiedIPv4 IPv692
AS271685INTERNET D+.COM LTDAUnclassifiedIPv4 IPv688
AS271612LOGO TelecomUnclassifiedIPv4 IPv661
AS270265VAVATEC TELECOMUNICACOESUnclassifiedIPv456
AS271315Netfusion Internet LTDAUnclassifiedIPv430

Provenance

Where this comes from

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