Observed topology

AS61798 HIGH TECH TELECOM LTDA

Unclassified LACNIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61798: 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
AS263102	R A DIAS SANTOS PROVEDOR DE INTERNET	Unclassified	IPv4 IPv6	406
AS61665	ROMICROS BRASIL LTDA	Residential	IPv4 IPv6	46
AS268337	INTERLINK TELECOMUNICACOES	Unclassified	IPv4	37
AS274511	IPNETWORK TELECOMUNICACOES E SOLUCOES LTDA	Unclassified	IPv4	10

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS274511	IPNETWORK TELECOMUNICACOES E SOLUCOES LTDA	Unclassified	IPv6	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS263102	R A DIAS SANTOS PROVEDOR DE INTERNET	Unclassified	IPv4 IPv6	406
AS61665	ROMICROS BRASIL LTDA	Residential	IPv4 IPv6	46
AS268337	INTERLINK TELECOMUNICACOES	Unclassified	IPv4 IPv6	38
AS274511	IPNETWORK TELECOMUNICACOES E SOLUCOES LTDA	Unclassified	IPv4 IPv6	11

Provenance

Where this comes from

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