Observed topology

AS269429 LUCIANA P. DA SILVA-INFORMATICA-ME

Unclassified LACNIC

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269429: 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
AS266129	LOCALLINK TELECOMUNICACOES LTDA - ME	Residential	IPv4 IPv6	213
AS266649	Netcity Tecnologia em Internet Ltda-ME	Residential	IPv4	119
AS266240	A2 TELECOM EIRELI - ME	Unclassified	IPv4 IPv6	39

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS266649	Netcity Tecnologia em Internet Ltda-ME	Residential	IPv4	60
AS268664	MEGA TOP MULTIMIDIA LTDA-ME	Unclassified	IPv4	60
AS262560	LONDRES & VELOSO INFORMATICA LTDA	Unclassified	IPv4	36

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS266129	LOCALLINK TELECOMUNICACOES LTDA - ME	Residential	IPv4 IPv6	249
AS266240	A2 TELECOM EIRELI - ME	Unclassified	IPv4 IPv6	219
AS266649	Netcity Tecnologia em Internet Ltda-ME	Residential	IPv4	179
AS268664	MEGA TOP MULTIMIDIA LTDA-ME	Unclassified	IPv4	120
AS262560	LONDRES & VELOSO INFORMATICA LTDA	Unclassified	IPv4	36

Provenance

Where this comes from

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