It’s not a filtering. At least with regard to Russia it’s a great packet loss from “Telia network” 184.108.40.206 (nyk-b2-link.telia.net) to Packet 220.127.116.11 (packethost-ic-345229-nyk-b2.c.telia.net).
I have udp trace lost here(last hop - telia, packet does not reply). We have ping/icmp traceroute lost here. Even http/tcp lost and sometimes we cannot open https://www.ntppool.org/scores/ page.
When packets of multiple protocols are lost, this is not a filter. It’s a bad connectivity - channel overload (but usually, when overloaded, packets alternately disappear or not. In our case, ping disappears completely for 20-120 seconds, this is not very typical for overload), channel/interface/route/routing protocol flapping, or DDoS. The problem is between Telia and Packet (or in Telia). Looking at the trace from RU to pool servers this problem is clear as day. Reverse route and trace go through he.net without telia and does not snow trouble (and yes, we have assymetric route there)
At 22 dec I was wrote to Packet and open ticket [XHCD-6557-HDBQ] with ping/trace details. Since you are Packet client, you can join and rush them to resolve this issue ASAP.