Observed topology

AS269050 JOAO ROGERIO LEONARDO EIRELIME

Unclassified APNIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269050: 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
AS273421	MAZA Telecom	Unclassified	IPv4	41
AS269371	J Z A Comunicacoes LTDA	Unclassified	IPv6	34
AS262761	Sinal Br Telecom Ltda	Unclassified	IPv4	16
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS269371	J Z A Comunicacoes LTDA	Unclassified	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS269371	J Z A Comunicacoes LTDA	Unclassified	IPv4 IPv6	94
AS273421	MAZA Telecom	Unclassified	IPv4	61
AS262761	Sinal Br Telecom Ltda	Unclassified	IPv4	32
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4	20
AS1031	PEER 1031 LLC	Unclassified	IPv4	5
AS24961	WIIT AG	Hosting	IPv4	1

Provenance

Where this comes from

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