ping spikes when taking any actions in maps

winmtr https://pastebin.com/fuw8biYw
started recently, constant spiking IN MAPS on any eu server i try, especially during combat/clicking boxes
no clue what else i can try
also no clue why my last attempt at this post was marked as spam and removed, i'm losing my mind
footage exmaple
https://streamable.com/7ylh00
https://streamable.com/x5vmd6

"

Melty32#9109 wrote:

winmtr https://pastebin.com/fuw8biYw

Thank you for providing a WinMTR log.

The log shows an issue creeping in on the third hop;

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---------------|------|------|------|------|------|------|
| NETBOX.HOME - 0 | 185 | 185 | 0 | 0 | 6 | 0 |
| 85-250-208-1.bb.netvision.net.il - 0 | 185 | 185 | 3 | 4 | 17 | 4 |
| 212.143.229.201 - 7 | 148 | 138 | 3 | 3 | 7 | 3 |

In order, we are looking at;

• The router in your home.
• The first router in your ISP's network.
• A router deeper within your ISP's network.

Neither your router nor the first hop in your ISP's network shows any packet loss. However, past that we see consistent packet loss from 0% - 7% throughout the rest of the log file. (The single line claiming 100% packet loss is inaccurate & can be ignored.)

The log file is quite short (185 pings sent; GGG request 300-500). If there is some apparent packet loss early in a log, but multiple consecutive hops report 0% packet loss despite a substantial number of pings being sent to them, we can typically ignore the packet loss as it's likely just routers throttling their responses to you, but forwarding your traffic (their actual job!) without issue.

Packet loss is inherently unstable and inconsistent, which is why relatively long tests are requested so we can more conclusively rule out issues. If, for example, your test only sent 5 pings to each hop but your internet connection had ~5% packet loss, then it would be relatively likely that the test could essentially "get lucky" and just not be affected.

The fact that your test is of short-to-medium length but always shows that packet loss - once introduced - never goes two consecutive hops without reappearing shows that we are, in fact, dealing with actual packet loss and it's not just individual routers throttling responses.

Because the issue appears to be with your ISP's network, the only likely solution is for you to reach out to their support team and show them the WinMTR log. Tier 1 support will very likely try pinging your router ~4 times - and if your router is online and responding at all, they'll say there doesn't appear to be any issue.

When tier 2 (or higher) support are actually investigating, it will help them tremendously to see where the packet loss begins so that they can begin isolating the issue to work out the root cause.

As the issue appears to be on the route, it's possible that using a VPN service would mitigate the problem - more through luck than judgement - by causing your internet traffic to take a different path; bypassing the problematic infrastructure in the process.

oh yeah i ended it too early huh
thank you for the huge reply imma try vpn
https://pastebin.com/3cyU1Ctslonger winmtr
vpn did not fix the problem, winmtr with vpn https://pastebin.com/Gsd8Vu3z