Observed topology
AS214915 PawHost Jan Smyrek
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS214915: 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 |
|---|---|---|---|---|
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 499 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 320 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 17 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 17 |
| AS206499 | LOCIX LIMITED | Unclassified | IPv4 | 9 |
| AS58057 | Securebit AG | Unclassified | IPv6 | 8 |
| AS199854 | Jens Thies | Unclassified | IPv6 | 8 |
Transit
Downstream networks
Networks for which AS214915 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS215147 | Schleyer-EDV UG | Unclassified | IPv4 IPv6 | 124 |
| AS218591 | Aaron Janssen | Unclassified | IPv4 IPv6 | 99 |
| AS201445 | Zerval Network LLC | Unclassified | IPv4 IPv6 | 69 |
| AS209857 | WGC-Systems UG (haftungsbeschraenkt) | Unclassified | IPv4 IPv6 | 67 |
| AS219362 | Fynn Huppke | Unclassified | IPv4 | 60 |
| AS207530 | Timo Schaffert | Unclassified | IPv4 IPv6 | 50 |
| AS197260 | Philipp Lohnes | Unclassified | IPv6 | 44 |
| AS213422 | Peter Lehmann | Unclassified | IPv6 | 40 |
| AS212044 | Sven Heim | Unclassified | IPv6 | 39 |
| AS219348 | Patrick Lederle trading as XION-Group | Unclassified | IPv6 | 39 |
Adjacency
Adjacent networks
Every AS seen directly next to AS214915 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 851 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 528 |
| AS215147 | Schleyer-EDV UG | Unclassified | IPv4 IPv6 | 167 |
| AS218591 | Aaron Janssen | Unclassified | IPv4 IPv6 | 99 |
| AS201445 | Zerval Network LLC | Unclassified | IPv4 IPv6 | 69 |
| AS209857 | WGC-Systems UG (haftungsbeschraenkt) | Unclassified | IPv4 IPv6 | 67 |
| AS219362 | Fynn Huppke | Unclassified | IPv4 | 60 |
| AS24961 | WIIT AG | Hosting | IPv4 IPv6 | 50 |
| AS207530 | Timo Schaffert | Unclassified | IPv4 IPv6 | 50 |
| AS197260 | Philipp Lohnes | Unclassified | IPv6 | 44 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.