Observed topology
AS211588 XYPHEN
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS211588: 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 |
|---|---|---|---|---|
| AS35133 | Eranium B.V. | Hosting | IPv4 IPv6 | 95 |
| AS49981 | WorldStream B.V. | Hosting | IPv4 IPv6 | 21 |
| AS20562 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 19 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 18 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 16 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 10 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 6 |
| AS57866 | Fusix Networks B.V. | Unclassified | IPv4 | 6 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 5 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 5 |
Transit
Downstream networks
Networks for which AS211588 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS215481 | Bram de Graaf trading as FlexyNode | Hosting | IPv4 IPv6 | 154 |
| AS209990 | Diyaaeldin Moustafa trading as Karmuz | Unclassified | IPv4 IPv6 | 120 |
| AS215577 | Lucas van Beek | Unclassified | IPv6 | 87 |
| AS200223 | Lars Jannick Volkers trading as Etheron Hosting | Unclassified | IPv4 IPv6 | 67 |
| AS203256 | Budget Phone Company BV | Unclassified | IPv4 | 58 |
| AS401146 | TURNEL | Unclassified | IPv4 | 58 |
| AS216107 | Noah van der Aa trading as Frumentum Media | Hosting | IPv4 IPv6 | 46 |
| AS209626 | Enflow B.V. | Unclassified | IPv4 IPv6 | 40 |
Adjacency
Adjacent networks
Every AS seen directly next to AS211588 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35133 | Eranium B.V. | Hosting | IPv4 IPv6 | 402 |
| AS215481 | Bram de Graaf trading as FlexyNode | Hosting | IPv4 IPv6 | 154 |
| AS209990 | Diyaaeldin Moustafa trading as Karmuz | Unclassified | IPv4 IPv6 | 124 |
| AS215577 | Lucas van Beek | Unclassified | IPv6 | 120 |
| AS24785 | Broadband Hosting B.V. | Hosting | IPv4 IPv6 | 71 |
| AS200223 | Lars Jannick Volkers trading as Etheron Hosting | Unclassified | IPv4 IPv6 | 67 |
| AS216107 | Noah van der Aa trading as Frumentum Media | Hosting | IPv4 IPv6 | 62 |
| AS49981 | WorldStream B.V. | Hosting | IPv4 IPv6 | 58 |
| AS203256 | Budget Phone Company BV | Unclassified | IPv4 | 58 |
| AS401146 | TURNEL | Unclassified | IPv4 | 58 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.