asn.dev

Observed topology

AS49009 FFHH Freifunk Rheinland e.V.

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS49009: 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
AS9211Nawork Internet Informationssysteme GmbHHostingIPv426
AS6939Hurricane Electric LLCTransitIPv624
AS50629LWLcom GmbHUnclassifiedIPv4 IPv622
AS9002RETN LimitedUnclassifiedIPv4 IPv612
AS199938Netzwerge GmbHUnclassifiedIPv43
AS24482SG.GSHostingIPv4 IPv62
AS212024Marc SchmittUnclassifiedIPv4 IPv62
AS8551Bezeq International Ltd.UnclassifiedIPv41
AS8893Artfiles New Media GmbHHostingIPv41
AS12731IPHH Internet Port Hamburg GmbHUnclassifiedIPv41

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201173Chaotikum e.V.UnclassifiedIPv634
AS50017fux eGUnclassifiedIPv619
AS31451Thomas KingUnclassifiedIPv61

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv673
AS201173Chaotikum e.V.UnclassifiedIPv634
AS9211Nawork Internet Informationssysteme GmbHHostingIPv426
AS50629LWLcom GmbHUnclassifiedIPv4 IPv622
AS50017fux eGUnclassifiedIPv619
AS9002RETN LimitedUnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv63
AS199938Netzwerge GmbHUnclassifiedIPv43
AS212024Marc SchmittUnclassifiedIPv4 IPv63
AS17639Converge ICT Solutions Inc.UnclassifiedIPv62

All 20 adjacent →

Provenance

Where this comes from

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