Observed topology
AS16024 GELSEN-NET Willy-Brandt-Allee 26
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS16024: 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 |
|---|---|---|---|---|
| AS15763 | DOKOM Gesellschaft fuer Telekommunikation mbH | Residential | IPv4 IPv6 | 362 |
| AS12329 | GLASFASER RUHR GmbH & Co. KG | Unclassified | IPv4 IPv6 | 226 |
| AS34309 | Link11 GmbH | Unclassified | IPv4 IPv6 | 191 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 168 |
| AS3209 | Vodafone GmbH | Residential | IPv4 IPv6 | 128 |
| AS55002 | F5, Inc. | Unclassified | IPv4 | 26 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 21 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 21 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 21 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 21 |
Transit
Downstream networks
Networks for which AS16024 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35227 | Hertener Stadtwerke GmbH | Unclassified | IPv4 | 99 |
| AS212587 | Gemeinsame Kommunale Datenzentrale Recklinghausen Zweckverband | Unclassified | IPv4 IPv6 | 98 |
| AS203593 | TeleMark Telekommunikationsgesellschaft Mark mbH | Unclassified | IPv4 | 36 |
| AS12329 | GLASFASER RUHR GmbH & Co. KG | Unclassified | IPv4 | 32 |
| AS15763 | DOKOM Gesellschaft fuer Telekommunikation mbH | Residential | IPv4 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16024 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3209 | Vodafone GmbH | Residential | IPv4 IPv6 | 504 |
| AS12329 | GLASFASER RUHR GmbH & Co. KG | Unclassified | IPv4 IPv6 | 473 |
| AS15763 | DOKOM Gesellschaft fuer Telekommunikation mbH | Residential | IPv4 IPv6 | 464 |
| AS34309 | Link11 GmbH | Unclassified | IPv4 IPv6 | 196 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 185 |
| AS35227 | Hertener Stadtwerke GmbH | Unclassified | IPv4 | 99 |
| AS212587 | Gemeinsame Kommunale Datenzentrale Recklinghausen Zweckverband | Unclassified | IPv4 IPv6 | 98 |
| AS203593 | TeleMark Telekommunikationsgesellschaft Mark mbH | Unclassified | IPv4 | 44 |
| AS55002 | F5, Inc. | Unclassified | IPv4 | 26 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 25 |
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.