asn.dev

Observed topology

AS201701 FFRL-AS

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS201701: 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 IPv6137
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6105
AS9002RETN LimitedUnclassifiedIPv4 IPv627
AS24961WIIT AGHostingIPv4 IPv623
AS9136Wobcom GmbHResidentialIPv4 IPv617
AS88811&1 Versatel GmbHResidentialIPv4 IPv615
AS5405Inter.link GmbHUnclassifiedIPv4 IPv613
AS3320Deutsche Telekom AGMobileIPv4 IPv612
AS24482SG.GSHostingIPv44
AS34019Hivane AssociationUnclassifiedIPv4 IPv64

All 23 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207871Freifunk Duesseldorf e.V.UnclassifiedIPv4 IPv696
AS213097roots at eifel e.V.UnclassifiedIPv460
AS49009Freifunk Rheinland e.V.UnclassifiedIPv41

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6186
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6152
AS207871Freifunk Duesseldorf e.V.UnclassifiedIPv4 IPv696
AS213097roots at eifel e.V.UnclassifiedIPv460
AS24961WIIT AGHostingIPv4 IPv649
AS9002RETN LimitedUnclassifiedIPv4 IPv639
AS9136Wobcom GmbHResidentialIPv4 IPv628
AS3320Deutsche Telekom AGMobileIPv4 IPv617
AS88811&1 Versatel GmbHResidentialIPv4 IPv615
AS5405Inter.link GmbHUnclassifiedIPv4 IPv613

All 26 adjacent →

Provenance

Where this comes from

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