Roskomnadzor starts a 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), the RKN is launching a new round of struggle with the messenger: this time, the proxies and VPN services located directly at the hosting end up providers.

The blocking mechanism is presumably:
')

1. Mail.ru's powers (network 128.140.168.0/21 and in particular 128.140.175.98) scans the Internet for proxies and VPN services that allow access to Telegram.
2. Abuse is sent to the hoster (some report a direct hit on the RKN ban)
3. Hoster terminates the service

Or, some hosters, like at KDPV, for example, are beginning to preemptively suspend their services.

Mail.ru itself denies the charges and transfers the arrows to a certain "tenant-client"

A possible way to deal with this is to send 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 under the gun.