Roskomnadzor begins the war against proxies and VPN

According to reports in Telegram channels and in the media , in particular on the ZaTelecom channel (led by Mikhail Klimarev, Executive Director of the Internet Protection Society), ILV begins a new round of struggle with the messenger: this time, proxies and VPN services located directly at the hosting are at stake providers.

The locking mechanism is supposedly as follows:

1. By the capabilities of Mail.ru (network 128.140.168.0/21 and in particular 128.140.175.98), the Internet is scanned for proxies and VPN services that allow you to access Telegram.
2. It is sent to Abuse to the hoster (some report a direct hit in the ILV ban)
3. Hoster terminates service

Or, some hosters, like on KDPV, for example, begin to proactively suspend their services.

Mail.ru itself denies the allegations and switches the arrows to a certain “client-tenant”.

A possible way to deal with this could be sending packets from 128.140.168.0/21 and not only to / dev / null.



Thus, in addition to the obvious AWS, DO, GCC, Hetzner, Hostland, GCoreLabs, Fozzy, FastVPS and, probably, many others are also at stake .