Observed topology

AS269561 AS269561 - M.M. Brito da Silva - Multimidia

Unclassified LACNIC Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 2

Upstream graph Who carries AS269561, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS269561 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269561: 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.

AS	Network	Type	Families	Paths seen
AS272501	Cotia Fiber Telecomunicacoes e Servicos LTDA	Unclassified	IPv4 IPv6	94
AS272559	ULISSES DE OLIVEIRA SANTOS - ME	Unclassified	IPv4	92
AS270741	NossaNeT Fortaleza	Unclassified	IPv4	48
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	30
AS269375	SAIONARA FERNANDES DA SILVA	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS272501	Cotia Fiber Telecomunicacoes e Servicos LTDA	Unclassified	IPv4 IPv6	94
AS272559	ULISSES DE OLIVEIRA SANTOS - ME	Unclassified	IPv4	92
AS270741	NossaNeT Fortaleza	Unclassified	IPv4	48
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	30
AS269375	SAIONARA FERNANDES DA SILVA	Unclassified	IPv4	2

Provenance

Where this comes from

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