asn.dev

Observed topology

AS61934 AS61934 - Puma Internet Tecnologia de Comunicacao LTDA Me

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61934: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6170
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv627
AS6939Hurricane Electric LLCTransitIPv610
AS24482SG.GSHostingIPv4 IPv610
AS35280F5 Networks SARLHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS3303Swisscom (Schweiz) AGResidentialIPv43
AS33891Core-Backbone GmbHHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269188HUBTEL TECNOLOGIA DE COMUNICACAO EIRELIUnclassifiedIPv4 IPv6139

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6238
AS269188HUBTEL TECNOLOGIA DE COMUNICACAO EIRELIUnclassifiedIPv4 IPv6139
AS6939Hurricane Electric LLCTransitIPv656
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv636
AS24482SG.GSHostingIPv4 IPv616
AS35280F5 Networks SARLHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS3303Swisscom (Schweiz) AGResidentialIPv44
AS33891Core-Backbone GmbHHostingIPv44

Provenance

Where this comes from

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