Observed topology

AS52560 AS52560 - ATK Telecomunicacoes Ltda.

Unclassified LACNIC

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52560: 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
AS262355	VSX Networks	Unclassified	IPv4 IPv6	521
AS267613	ELETRONET S.A.	Unclassified	IPv4 IPv6	39
AS24482	SG.GS	Hosting	IPv6	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS269564	H. MASSAO SAKUMA	Unclassified	IPv4	59
AS274611	G-9 TELECOM SERVICOS DE INTERNET LTDA	Unclassified	IPv6	32

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS262355	VSX Networks	Unclassified	IPv4 IPv6	670
AS267613	ELETRONET S.A.	Unclassified	IPv4 IPv6	96
AS274611	G-9 TELECOM SERVICOS DE INTERNET LTDA	Unclassified	IPv4 IPv6	90
AS269278	LINK NORTE RONDONOPOLIS LTDA	Unclassified	IPv4	60
AS269564	H. MASSAO SAKUMA	Unclassified	IPv4	59
AS14868	Ligga Telecomunicacoes S.A.	Unclassified	IPv4	2
AS24482	SG.GS	Hosting	IPv6	2

Provenance

Where this comes from

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