Short answer is: Big Meta Queries are incredibly bad and can quickly lead to the MySQL-Server not responding anymore. You should try to rework the meta_query to not have so many clauses.
Long Answer:
Wordpress Post Metadata is stored incredibly inefficient when it comes to querying. Best advise would be to never ever EVER store data that you would need to query for into post_meta, but that is mostly not possible.
What happens when you use a big meta query is this: the created SQL LEFT JOINs the post_meta database table for every clause there is to the posts table. That means in your case you have a minimum of 10 LEFT JOINS. The MySQL Server probably is stuck in the calculation phase where it tries to find the best way to JOIN all this data into one view.
What should you do now?
As Jacob Peattie said, you should first and foremost rework “featured” and “claimed” into a taxonomy of sorts.
Next Thing you can try is to Speed up the Postmeta Table like written here: (only do this if you know your way around MySQL Databases) http://mysql.rjweb.org/doc.php/index_cookbook_mysql#speeding_up_wp_postmeta
This should take some stress off the MySQL Server.
However, you should really consider changing the type of query you want to make. Maybe you can rework the ‘_min_kapali_davet_alani’ and ‘_max_kapali_davet_alani’ into one single meta key? So that you could use a “BETWEEN” Meta query condition? I’m not quite sure what your site does, so it’s a bit hard to find good changes.
If nothing helps, you can try to make direct database queries using $wpdb to get results for the single queries (like “between 100 and 200”, “between 200 and 300” etc) and then compare the results and give the posts, that you end up wanting to query directly into the “post__in” parameter.
Happy Coding!