Observed topology
AS56382 VSERVERLTD vServer.site
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS56382: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 217 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 158 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 156 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 124 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 99 |
| AS24961 | WIIT AG | Hosting | IPv4 | 42 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 40 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 22 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 22 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 22 |
Transit
Downstream networks
Networks for which AS56382 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS206313 | Freifunk Nordwest e. V. | Unclassified | IPv4 IPv6 | 182 |
| AS208236 | Adrian Reyer | Unclassified | IPv4 IPv6 | 121 |
| AS212085 | Alexander Bruegmann | Unclassified | IPv6 | 91 |
| AS205094 | Tivon Haeberlein | Unclassified | IPv4 IPv6 | 61 |
| AS39083 | David Froehlich | Residential | IPv4 IPv6 | 55 |
| AS208976 | FS IT-Systeme GmbH | Unclassified | IPv4 IPv6 | 12 |
| AS202729 | Jennifer Graul | Unclassified | IPv6 | 7 |
| AS211275 | Thomas Rogdakis | Unclassified | IPv6 | 7 |
Adjacency
Adjacent networks
Every AS seen directly next to AS56382 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 455 |
| AS202265 | InterWebs Ltd. | Unclassified | IPv4 IPv6 | 306 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 278 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 244 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 220 |
| AS39083 | David Froehlich | Residential | IPv4 IPv6 | 185 |
| AS206313 | Freifunk Nordwest e. V. | Unclassified | IPv4 IPv6 | 182 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 170 |
| AS24961 | WIIT AG | Hosting | IPv4 IPv6 | 141 |
| AS208236 | Adrian Reyer | Unclassified | IPv4 IPv6 | 121 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.