Observed topology

AS269715 AS269715 - INFINITYGO TELECOM LTDA

Residential LACNIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269715: 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
AS266409	SECW TELECOM	Unclassified	IPv4	296
AS263558	RD TELECOM LTDA -ME	Residential	IPv4 IPv6	76
AS273446	DBR TELECOMUNICACOES LTDA	Unclassified	IPv4	61
AS52573	Une Telecom Ltda	Residential	IPv4	54

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS269585	TOPLINK INTERNET E SERVICOS DE INFORMATICA LTDA	Unclassified	IPv6	16

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS266409	SECW TELECOM	Unclassified	IPv4	296
AS263558	RD TELECOM LTDA -ME	Residential	IPv4 IPv6	92
AS273446	DBR TELECOMUNICACOES LTDA	Unclassified	IPv4	61
AS52573	Une Telecom Ltda	Residential	IPv4	54
AS269585	TOPLINK INTERNET E SERVICOS DE INFORMATICA LTDA	Unclassified	IPv6	16

Provenance

Where this comes from

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