Observed topology
AS15694 ATMAN-ISP-AS Atman Sp. z o.o.
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS15694: 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 | 792 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 512 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 308 |
| AS24724 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 140 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 129 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 48 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 47 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 47 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 47 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 47 |
Transit
Downstream networks
Networks for which AS15694 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57367 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 2,436 |
| AS41079 | Cyber_Folks S.A. | Hosting | IPv4 | 978 |
| AS30851 | Sileman Sp. z o.o. | Unclassified | IPv4 | 544 |
| AS41745 | Ilia Baikov | Unclassified | IPv4 | 540 |
| AS49720 | Gigacloud LLC | Unclassified | IPv4 IPv6 | 400 |
| AS41959 | PLJ TELECOM sp. z o.o. | Residential | IPv4 | 325 |
| AS34342 | Atman Sp. z o.o. | Unclassified | IPv4 | 300 |
| AS197811 | PL.2012+ Sp. z o.o. | Unclassified | IPv4 | 205 |
| AS43862 | Towarowa Gielda Energii S.A | Unclassified | IPv4 IPv6 | 192 |
| AS24929 | IT arte Sp. z o.o. | Hosting | IPv4 | 188 |
Adjacency
Adjacent networks
Every AS seen directly next to AS15694 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 5,275 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,383 |
| AS57367 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 2,446 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,558 |
| AS41079 | Cyber_Folks S.A. | Hosting | IPv4 | 978 |
| AS24724 | Atman Sp. z o.o. | Hosting | IPv4 IPv6 | 957 |
| AS30851 | Sileman Sp. z o.o. | Unclassified | IPv4 | 821 |
| AS41745 | Ilia Baikov | Unclassified | IPv4 | 540 |
| AS49720 | Gigacloud LLC | Unclassified | IPv4 IPv6 | 464 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 391 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.