asn.dev

Observed topology

AS47689 Pudu Pudu, LLC

Unclassified RIPE

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS47689: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6258
AS1299Arelion Sweden ABTransitIPv4 IPv665
AS395823doof.netUnclassifiedIPv457
AS34927iFog GmbHHostingIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv69
AS54148Dynamic Quantum NetworksUnclassifiedIPv4 IPv68
AS23033Wowrack.comHostingIPv46
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv64
AS213241TECHIT.BE SRLResidentialIPv4 IPv64
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv64

All 30 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 30

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6258
AS1299Arelion Sweden ABTransitIPv4 IPv665
AS395823doof.netUnclassifiedIPv457
AS34927iFog GmbHHostingIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv69
AS54148Dynamic Quantum NetworksUnclassifiedIPv4 IPv68
AS23033Wowrack.comHostingIPv46
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv64
AS213241TECHIT.BE SRLResidentialIPv4 IPv64
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv64

All 30 adjacent →

Provenance

Where this comes from

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