Observed topology

AS262539 AS262539 - DUNET LTDA

Residential LACNIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262539: 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
AS53062	GGNET TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	1,815
AS22381	SAMM TECNOLOGIA E TELECOMUNICACOES S.A	Unclassified	IPv4	226
AS6939	Hurricane Electric LLC	Transit	IPv4	140
AS24482	SG.GS	Hosting	IPv4 IPv6	51

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS266510	TORRES INTERNET LTDA	Unclassified	IPv4 IPv6	130

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS53062	GGNET TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	1,899
AS22381	SAMM TECNOLOGIA E TELECOMUNICACOES S.A	Unclassified	IPv4	239
AS6939	Hurricane Electric LLC	Transit	IPv4	166
AS266510	TORRES INTERNET LTDA	Unclassified	IPv4 IPv6	130
AS24482	SG.GS	Hosting	IPv4 IPv6	54
AS35280	F5 Networks SARL	Hosting	IPv4	2
AS37721	Virtual Technologies & Solutions	Residential	IPv4	2

Provenance

Where this comes from

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