asn.dev

Observed topology

AS50017 fux fux eG

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50017: 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
AS50629LWLcom GmbHUnclassifiedIPv4 IPv644
AS12731IPHH Internet Port Hamburg GmbHUnclassifiedIPv4 IPv627
AS49009Freifunk Rheinland e.V.UnclassifiedIPv620
AS6939Hurricane Electric LLCTransitIPv46
AS24482SG.GSHostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209427Nycro UG (haftungsbeschraenkt)UnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12731IPHH Internet Port Hamburg GmbHUnclassifiedIPv4 IPv681
AS209427Nycro UG (haftungsbeschraenkt)UnclassifiedIPv462
AS50629LWLcom GmbHUnclassifiedIPv4 IPv644
AS49009Freifunk Rheinland e.V.UnclassifiedIPv620
AS6939Hurricane Electric LLCTransitIPv414
AS24482SG.GSHostingIPv4 IPv62

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.