asn.dev

Observed topology

AS269475 AS269475 - E D Sousa telecomunicacoes

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269475: 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
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv6136
AS61659godnet telecomResidentialIPv4 IPv6107
AS6939Hurricane Electric LLCTransitIPv671
AS270586B2 NETWORKS MULTIMIDIA LTDAResidentialIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv69
AS3303Swisscom (Schweiz) AGResidentialIPv46
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS33891Core-Backbone GmbHHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270586B2 NETWORKS MULTIMIDIA LTDAResidentialIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv6136
AS61659godnet telecomResidentialIPv4 IPv6108
AS6939Hurricane Electric LLCTransitIPv671
AS270586B2 NETWORKS MULTIMIDIA LTDAResidentialIPv4 IPv616
AS24482SG.GSHostingIPv4 IPv69
AS3303Swisscom (Schweiz) AGResidentialIPv46
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS33891Core-Backbone GmbHHostingIPv43

Provenance

Where this comes from

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