asn.dev

Observed topology

AS61797 AS61797 - CHECK-UP NET TELECOM

Unclassified LACNIC

Upstreams 4 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 8
Upstream graph Who carries AS61797, and who carries them, drawn as a map up to the transit-free core. 4 exchanges Where AS61797 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61797: 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.

ASNetworkTypeFamiliesPaths seen
AS53181Avanca Telecom e Servicos LTDAUnclassifiedIPv4 IPv6533
AS268696Tuddo Telecom Ltda.UnclassifiedIPv4 IPv6114
AS35280F5 Networks SARLHostingIPv4 IPv618
AS262296Windx TelecomunicacoesUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270343MGT COMUNICACAOUnclassifiedIPv4 IPv6128
AS273775F5 COMPUTADORES LTDAUnclassifiedIPv694
AS61698WINQ ULTRANETResidentialIPv4 IPv673
AS262781RADIOBR INTERNET LTDAUnclassifiedIPv458
AS267654MAXBR COMERCIO E PRESTACAO DE SERVICOS LTDA - MEResidentialIPv4 IPv635

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53181Avanca Telecom e Servicos LTDAUnclassifiedIPv4 IPv6846
AS268696Tuddo Telecom Ltda.UnclassifiedIPv4 IPv6181
AS270343MGT COMUNICACAOUnclassifiedIPv4 IPv6128
AS273775F5 COMPUTADORES LTDAUnclassifiedIPv694
AS61698WINQ ULTRANETResidentialIPv4 IPv673
AS262781RADIOBR INTERNET LTDAUnclassifiedIPv458
AS267654MAXBR COMERCIO E PRESTACAO DE SERVICOS LTDA - MEResidentialIPv4 IPv635
AS35280F5 Networks SARLHostingIPv4 IPv622
AS262296Windx TelecomunicacoesUnclassifiedIPv65

Provenance

Where this comes from

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