Observed topology
AS215147 SCHLEYER-EDV Schleyer-EDV
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS215147: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 140 |
| AS214915 | Jan Smyrek | Unclassified | IPv4 IPv6 | 112 |
| AS215375 | Luca Nowak | Unclassified | IPv4 IPv6 | 97 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv4 IPv6 | 8 |
| AS58057 | Securebit AG | Unclassified | IPv6 | 8 |
| AS49134 | 10VPN Research Network LTD | Unclassified | IPv4 | 2 |
| AS212508 | Lowhosting services of Davide Gennari | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS215147 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS215147 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 340 |
| AS214915 | Jan Smyrek | Unclassified | IPv4 IPv6 | 146 |
| AS215375 | Luca Nowak | Unclassified | IPv4 IPv6 | 134 |
| AS210796 | Bjoern Schleyer | Unclassified | IPv6 | 113 |
| AS202358 | MVNET-SOLUTIONS UG | Unclassified | IPv6 | 74 |
| AS219418 | Jan Hill | Unclassified | IPv4 IPv6 | 34 |
| AS219110 | Yanis Ramge | Unclassified | IPv6 | 28 |
| AS215828 | Tizian Maxime Weigt trading as "TMW Global Networks" | Hosting | IPv4 IPv6 | 27 |
| AS58057 | Securebit AG | Unclassified | IPv6 | 22 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv4 IPv6 | 18 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.