yeah, ... it looks like you are right. Thank you, aaa25652

i contacted the provider (rostelecom). They said that everithing ok on their part. There are not blocking the connecting.

everything is very strange. I can use the site theMovieDB.org like user and to see the pages (on a dedicated optical line for the Internet), but API requests are not being processed. API key is not blocked.

ru(очень странно. Я могу зайти на сайт theMovieDB.org, но запросы не обрабатываются. API ключ активен )

I have the same =)

@7720@bk.ru said:

i contacted the provider (rostelecom). They said that everithing ok on their part. There are not blocking the connecting.

So, make traceroute to api.themoviedb.org, and You will see, where is trouble resides.

i did traceroute, ... but i don't understand these. If this is easy for you - please tell me where is the problem. Provider(Rostelecom sad that all ok on their part)

C:\Users\sam>tracert themoviedb.org

Trace route to themoviedb.org [13.32.143.22] with a maximum number of jumps of 30:

1 2 ms 1 ms <1 мс 192.168.0.1 2 8 ms 4 ms 39 ms 1.112.32.95.dsl-dynamic.vsi.ru [95.32.112.1] 3 5 ms 6 ms 4 ms 213.59.232.208 4 49 ms 29 ms 28 ms 188.254.25.75 5 * * * Timed out request 6 44 ms 43 ms 50 ms mskix2.amazon.com [195.208.209.119] 7 * * * Timed out request 8 * * * Timed out request 9 * * * Timed out request 10 * * * Timed out request 11 * * * Timed out request 12 * * * Timed out request 13 * * * Timed out request 14 54 ms 43 ms 48 ms server-13-32-143-22.hel50.r.cloudfront.net [13.3 2.143.22]

Trace completed.

C:\Users\sam>

Not to themoviedb.org! As I have mentionted abobe, www-site of TMDB is accessable fine. Api is hosted on different site. Try to make

tracert api.themoviedb.org

C:\Users\sam>tracert api.themoviedb.org

api.themoviedb.org [13.33.240.55]

1 1 ms 1 ms 2 ms 192.168.0.1 2 5 ms 28 ms 51 ms 1.112.32.95.dsl-dynamic.vsi.ru [95.32.112.1] 3 * * * Timed out request. 4 * * * Timed out request. .. 30 * * * Timed out request.

C:\Users\sam>

I went to the adress dsl-dynamic.vsi.ru__. The browser gave a message stating that there was malware on the site. I do't understand why trace request goes though this site. The other requests (to another sites) also go through dsl-dynamic.vsi.ru, but do and everything ok.

The 2nd hop (1.112.32.95.dsl-dynamic.vsi.ru) is Your's ISP access server. Then network packets must then travel through provider's internal net to upper-level provider, and , so on, to the destination. As we can see, traffic isn't ever leaves provider's Access Server. It's ISP definitely fault.

Thank you again, aaa25652. I contacted the provider again and again received an answer that they didn't set any restrictions and could not help. Russia -in one word.
Thank your for your time and help.... and for teaching me how to do tracing.

@7720@bk.ru said:
... Russia -in one word.

It is not only in Russia that it works like this.
In Brazil too.
And I believe in the whole world.
The first answer is always: It is not my fault.

are you saying that the provider's fault is not? Then why don't the data packets go further from this site? (1.112.32.95.dsl-dynamic.vsi.ru)

If the provider is to fault, then why does everything work with vpn?

I am going to ask my friends to check how API works in their town this evening.

To look for how it works in different location.