asn.dev

Observed topology

AS201709 HANDS

Hosting RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201709: 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
AS5405Inter.link GmbHUnclassifiedIPv4 IPv691
AS88811&1 Versatel GmbHResidentialIPv4 IPv660
AS199938Netzwerge GmbHUnclassifiedIPv4 IPv630
AS6939Hurricane Electric LLCTransitIPv421
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv64
AS6797GlobalConnect ABUnclassifiedIPv43
AS34800Securebit AGUnclassifiedIPv43
AS58057Securebit AGUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199938Netzwerge GmbHUnclassifiedIPv4 IPv68

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS88811&1 Versatel GmbHResidentialIPv4 IPv6166
AS199938Netzwerge GmbHUnclassifiedIPv4 IPv6136
AS5405Inter.link GmbHUnclassifiedIPv4 IPv691
AS6939Hurricane Electric LLCTransitIPv421
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv64
AS6797GlobalConnect ABUnclassifiedIPv43
AS34800Securebit AGUnclassifiedIPv43
AS58057Securebit AGUnclassifiedIPv61

Provenance

Where this comes from

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