Observed topology
AS50917 DIEDERIK-AS Diederik Focko de Zee
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS50917: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16276 | OVH SAS | Hosting | IPv4 | 62 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 48 |
| AS216265 | ARISTO NETWORKS LTD | Unclassified | IPv4 IPv6 | 38 |
| AS35133 | Eranium B.V. | Hosting | IPv6 | 36 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 20 |
| AS20495 | We Dare B.V. | Unclassified | IPv4 | 18 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 8 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 4 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 4 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS50917 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200566 | ANARCHY LAB S.R.L. | Unclassified | IPv4 IPv6 | 9,432 |
| AS214481 | Wojciech Czapkowicz | Hosting | IPv4 IPv6 | 588 |
| AS216078 | Liam Kremer | Hosting | IPv4 IPv6 | 340 |
| AS208258 | Access2.IT Group B.V. | Hosting | IPv4 IPv6 | 198 |
| AS14054 | Purple Computer North America, Inc. | Hosting | IPv4 IPv6 | 156 |
| AS209094 | Technoberg Beheer B.V. | Unclassified | IPv4 IPv6 | 97 |
| AS215318 | Josha Prior trading as Netralex | Unclassified | IPv4 IPv6 | 97 |
| AS212591 | N1 Solutions B.V. trading as PLTFRMS | Unclassified | IPv4 IPv6 | 78 |
| AS214677 | Matteo Martelloni trading as DELUXHOST | Hosting | IPv4 IPv6 | 64 |
| AS219180 | InterLIR GmbH | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50917 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200566 | ANARCHY LAB S.R.L. | Unclassified | IPv4 IPv6 | 9,432 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,402 |
| AS216265 | ARISTO NETWORKS LTD | Unclassified | IPv4 IPv6 | 3,575 |
| AS20495 | We Dare B.V. | Unclassified | IPv4 | 1,901 |
| AS208258 | Access2.IT Group B.V. | Hosting | IPv4 IPv6 | 1,441 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,370 |
| AS214481 | Wojciech Czapkowicz | Hosting | IPv4 IPv6 | 1,177 |
| AS216078 | Liam Kremer | Hosting | IPv4 IPv6 | 1,039 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 781 |
| AS35133 | Eranium B.V. | Hosting | IPv4 IPv6 | 645 |
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.