asn.dev

Observed topology

AS61939 AS61939 - MICRORCIM PRO NET DO BRASIL INFORMATICA LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61939: 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
AS263903INFORBARRA TELECOMUnclassifiedIPv4450
AS7738V talUnclassifiedIPv4 IPv6283
AS26615TIM S/AMobileIPv4 IPv634

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273311PAULO FERREIRA DE SOUZAUnclassifiedIPv4 IPv694
AS264093Inet Pro Distribuicao de Dados LtdaUnclassifiedIPv4 IPv692
AS265984ZAVAZ INTERNET JANAUBA LTDAUnclassifiedIPv4 IPv653

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263903INFORBARRA TELECOMUnclassifiedIPv4 IPv6529
AS7738V talUnclassifiedIPv4 IPv6344
AS26615TIM S/AMobileIPv4 IPv6133
AS273311PAULO FERREIRA DE SOUZAUnclassifiedIPv4 IPv694
AS264093Inet Pro Distribuicao de Dados LtdaUnclassifiedIPv4 IPv692
AS265984ZAVAZ INTERNET JANAUBA LTDAUnclassifiedIPv4 IPv653

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.