Observed topology

AS61795 Arion Servicos de Telecomunicacoes LTDA

Unclassified AFRINIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61795: 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
AS10429	TELEFONICA BRASIL S.A	Residential	IPv4 IPv6	276
AS4230	CLARO S.A.	Residential	IPv4 IPv6	155
AS25933	Vogel Solucoes em Telecom e Informatica S/A	Unclassified	IPv4 IPv6	109
AS23106	AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LT	Unclassified	IPv4 IPv6	92

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS28618	Linktel Telecom do Brasil Ltda	Unclassified	IPv4	177

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS10429	TELEFONICA BRASIL S.A	Residential	IPv4 IPv6	396
AS28618	Linktel Telecom do Brasil Ltda	Unclassified	IPv4	177
AS25933	Vogel Solucoes em Telecom e Informatica S/A	Unclassified	IPv4 IPv6	166
AS4230	CLARO S.A.	Residential	IPv4 IPv6	155
AS23106	AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LT	Unclassified	IPv4 IPv6	92

Provenance

Where this comes from

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