Observed topology
AS205941 STEFAN
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS205941: 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 |
|---|---|---|---|---|
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 88 |
| AS11967 | Hop179 OU | Unclassified | IPv4 IPv6 | 81 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 74 |
| AS214762 | Sebastian Stefanek trading as MatHost.eu | Hosting | IPv6 | 72 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 IPv6 | 66 |
| AS49600 | NEAR IP, S.L. | Hosting | IPv4 IPv6 | 51 |
| AS215362 | Promo Plus SRL | Unclassified | IPv6 | 38 |
| AS60900 | Adrian Trifonov trading as Ssmidge Technologies | Unclassified | IPv6 | 34 |
| AS216456 | Dcent Investments BV | Unclassified | IPv4 IPv6 | 19 |
| AS215030 | Budankailu Namrata Patra trading as AspireHosting | Unclassified | IPv4 | 12 |
Transit
Downstream networks
Networks for which AS205941 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197806 | Andrei Rys | Unclassified | IPv4 IPv6 | 284 |
| AS204464 | NextServ LLC | Unclassified | IPv6 | 111 |
| AS208824 | Pau Cab | Unclassified | IPv4 IPv6 | 97 |
| AS213975 | Warwick Ward-Cox | Unclassified | IPv4 | 44 |
| AS203868 | Rifqi Arief Pamungkas | Unclassified | IPv6 | 41 |
| AS218569 | Viktor Nesmeianov | Unclassified | IPv4 IPv6 | 41 |
| AS17290 | AUSTIN-HADLEY | Unclassified | IPv4 | 39 |
| AS199518 | Gregory Shapiro | Unclassified | IPv6 | 38 |
| AS202934 | SINCITY HOSTING LLC | Hosting | IPv6 | 38 |
| AS205305 | Gabriel Peron | Unclassified | IPv6 | 38 |
Adjacency
Adjacent networks
Every AS seen directly next to AS205941 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 IPv6 | 395 |
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 322 |
| AS197806 | Andrei Rys | Unclassified | IPv4 IPv6 | 284 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 239 |
| AS210464 | ANDREW KRISTULI | Residential | IPv4 IPv6 | 200 |
| AS216456 | Dcent Investments BV | Unclassified | IPv4 IPv6 | 137 |
| AS214762 | Sebastian Stefanek trading as MatHost.eu | Hosting | IPv6 | 130 |
| AS204464 | NextServ LLC | Unclassified | IPv6 | 111 |
| AS215114 | Stevan Durand--L'Hours t/a SLBCLOUD | Unclassified | IPv4 IPv6 | 99 |
| AS208824 | Pau Cab | Unclassified | IPv4 IPv6 | 97 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.