Ping Packet Loss before patch 3.28 all was fine!

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| p3e9bf52a.dip0.t-ipconnect.de - 0 | 246 | 246 | 4 | 10 | 94 | 8 |
| p3e9bf52a.dip0.t-ipconnect.de - 0 | 246 | 246 | 4 | 10 | 94 | 7 |
| m-ef2-i.M.DE.NET.DTAG.DE - 0 | 246 | 246 | 10 | 15 | 73 | 13 |
| 80.150.168.185 - 0 | 246 | 246 | 10 | 14 | 75 | 11 |
| cloudflare-gw.cr0-muc1.ip4.gtt.net - 0 | 246 | 246 | 10 | 19 | 73 | 11 |
| 172.68.108.5 - 0 | 246 | 246 | 9 | 19 | 102 | 11 |
| 172.68.109.135 - 0 | 246 | 246 | 10 | 14 | 75 | 12 |
| 172.68.109.100 - 0 | 246 | 246 | 10 | 14 | 75 | 12 |
| 172.68.109.165 - 0 | 246 | 246 | 10 | 14 | 75 | 12 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| 149.6.129.223 - 21 | 134 | 106 | 26 | 31 | 92 | 31 |
| 213.196.19.69 - 26 | 122 | 91 | 26 | 30 | 80 | 28 |
| 173.233.133.193 - 26 | 122 | 91 | 25 | 28 | 66 | 27 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Thats the post from the Guide for testing MTR
Before the Patch 3.28 all was fine, now i struggle all day long and honestly playing a class cannon, is not funny if you slow mo, and afterwards rush without control into hundreds of enemies -.-

Additional Information Aquired

Lags getting even higher with higher Problem in Maps, out of map less (But in maps even by standing still not movin)

"

Darktemplers#4722 wrote:

| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| 149.6.129.223 - 21 | 134 | 106 | 26 | 31 |

Unfortunately it's difficult to parse the WinMTR log due to a number of routers on the route not participating - which is particularly unhelpful given that they exist exactly where the packet loss first emerges on your log. This means any reading of the log is strictly provisional.

The IP address 149.6.129.223 has been assigned to Cogent, and is believed to be used on a networking device that's located in-or-around the city of Amsterdam. It being assigned to Cogent does mean this is somewhat outside of GGG's ability to control.

Two things that might help are 1) changing gateway so that your traffic goes in a different direction, or, 2) running a VPN so that your traffic has the same destination, but takes a different route to get there. I typically recommend the free tier of ProtonVPN for such testing. But you'll likely have a smoother experience using a different gateway & no VPN.