Has Rostelecom started filtering WireGuard for everyone?

Question

VPN

Dear subscribers of Rostelecom, in particular those who use its services in the Moscow region, hello! Have you noticed problems with establishing a WireGuard connection to any hosts?
Personally, 2 days ago I discovered for myself that WireGaurd stopped doing a handshake on the Rostelecom network - I can track the packet on my network, but I can’t watch it on the server I’m trying to connect to. With all this, through netcat, packets go to the same port perfectly. As a result, I conclude that for some reason, the DPI of the RT is configured in such a way that WG packets are filtered.
I have already tried to go to neighbors using the services of this provider - the same result.
In those. supporters shrug their hands, stating that:

• Services are provided in full
  
• They don't see problems in the connection
  
• They are not responsible for the correct operation of someone else's infrastructure
  

and the 3rd point is absolutely delusional. If I can’t reach the site via HTTPS on port 443, then RT can supposedly help, and if I can’t reach port 1337 via WireGuard, then RT is no longer in business.

In general, if someone has such a problem or someone can quickly check the possibility of WG working in the Rostelecom network, then I will be very grateful to hear feedback.

Answer 1

In general, as expected, the problem is massive. I had to quickly transfer all tunnels to ports a la 80, 443. The problem is also observed on other providers, for example, on Beeline.

Answer 2

because wireguard can be filtered, but a properly configured openVPN is not)
right now everything will be blocked for a little bit ...
I have a megaphone and an iota stopped letting pptp ....

Answer 3

WireGuard, Rostelecom, blocked.
After switching to port 443, the flight is normal