Observed topology

AS266092 AS266092 - R. COSTA DO NASCIMENTO

Unclassified LACNIC

Upstreams 5 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266092: 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
AS53087	TELY Ltda.	Residential	IPv4 IPv6	97
AS266181	GOLDEN LINK	Residential	IPv4	63
AS263629	ALLREDE TELECOM MT / BRASIL TECPAR	Unclassified	IPv4	61
AS274464	NEXUSLINK DATACENTER LTDA	Unclassified	IPv4	60
AS262818	g j pereira	Unclassified	IPv4	30

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS271493	SPEED NET PEDRA	Unclassified	IPv4	61
AS266015	ALL FAST NETWORK LTDA	Unclassified	IPv6	32

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS266181	GOLDEN LINK	Residential	IPv4 IPv6	156
AS53087	TELY Ltda.	Residential	IPv4 IPv6	97
AS263629	ALLREDE TELECOM MT / BRASIL TECPAR	Unclassified	IPv4	61
AS271493	SPEED NET PEDRA	Unclassified	IPv4	61
AS274464	NEXUSLINK DATACENTER LTDA	Unclassified	IPv4	60
AS266015	ALL FAST NETWORK LTDA	Unclassified	IPv6	32
AS262818	g j pereira	Unclassified	IPv4	30

Provenance

Where this comes from

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