Observed topology

AS61605 AS61605 - SELIGA TELECOMUNICACOES DO BRASIL EIRELI

Unclassified APNIC NSP

Upstreams 3 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61605: 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
AS28260	ALTA REDE CORPORATE NETWORK TELECOM LTDA - EPP	Unclassified	IPv4 IPv6	280
AS28173	Dinamica Telecomunicacoes Ltda	Unclassified	IPv4 IPv6	80
AS262676	Intervip Networks Ltda.	Residential	IPv6	46

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS267492	ROBSON CARLOS THOMES - ME	Unclassified	IPv4	180

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS28260	ALTA REDE CORPORATE NETWORK TELECOM LTDA - EPP	Unclassified	IPv4 IPv6	381
AS267492	ROBSON CARLOS THOMES - ME	Unclassified	IPv4	180
AS28173	Dinamica Telecomunicacoes Ltda	Unclassified	IPv4 IPv6	126
AS262676	Intervip Networks Ltda.	Residential	IPv4 IPv6	79

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.