asn.dev

Observed topology

AS61642 NEXNETT Brasil Telecom

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61642: 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
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv4 IPv6244
AS52468UFINET PANAMA S.A.UnclassifiedIPv4206
AS6939Hurricane Electric LLCTransitIPv4 IPv671
AS24482SG.GSHostingIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266577CRAVNET INFORMATICA LTDAUnclassifiedIPv4 IPv6357
AS28154AR TELECOM PROVEDOR DE INTERNET LTDAResidentialIPv4189
AS266625WCA TELECOMResidentialIPv436

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDAHostingIPv4 IPv6636
AS52468UFINET PANAMA S.A.UnclassifiedIPv4374
AS266577CRAVNET INFORMATICA LTDAUnclassifiedIPv4 IPv6357
AS28154AR TELECOM PROVEDOR DE INTERNET LTDAResidentialIPv4189
AS6939Hurricane Electric LLCTransitIPv4 IPv6113
AS266625WCA TELECOMResidentialIPv4 IPv655
AS24482SG.GSHostingIPv4 IPv616
AS53013UFINET BRASIL S.A.HostingIPv4 IPv611

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.