Packet Loss - Unable to play for more than 15 seconds!

I'm from Ontario Canada, I have been having massive packet loss to the point where my game pretty much freezes for 5-15 seconds than very quickly replays everything that happened while I was disconnected. This kind of lag is only happening for Path of Exile as I also play World of Warcraft and Counter Strike Global Offensive just fine with my connectivity up on both games 100% of the time just like Path of Exile. My connection to PoE is fine as well its just the random spikes of packet loss that i'm experiencing which is insanely frustrating; especially since I have most of my fun playing Hardcore!

Things I have tried thus far:
-reinstalling Path of Exile; both the steam client and the standalone.
-changing my connection to my phones data, changing to the 2.4ghz connection on my router
-changing my network settings giving Path of Exile high priority both as a process and in my network (port forward)
-changing my in game settings both video and network (predictive is a fake fix)
-running PoE as admin or in compatibility mode for all the windows options I have access to
-closing all application and processes besides Path of Exile to see if its conflicting with anything

Nothing seems to be work here is a WinMTR to the washington server that I did

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| Minions - 0 | 121 | 121 | 0 | 2 | 48 | 1 |

| 10.88.128.1 - 0 | 121 | 121 | 8 | 13 | 57 | 13 |

| 169-4-226-24.rev.cgocable.net - 0 | 121 | 121 | 14 | 19 | 64 | 16 |

| 10.0.18.9 - 0 | 121 | 121 | 15 | 21 | 65 | 20 |

| 10-6-226-24.rev.cgocable.net - 0 | 121 | 121 | 15 | 21 | 66 | 20 |

|xe.1.0.0.bbr01.cl01.tor02.networklayer.com - 0 | 121 | 121 | 15 | 20 | 65 | 19 |

| ae7.bbr02.cl01.tor02.networklayer.com - 0 | 121 | 121 | 16 | 21 | 69 | 23 |

| ae0.bbr01.cl01.mon02.networklayer.com - 0 | 121 | 121 | 22 | 26 | 69 | 23 |

| ae7.bbr02.cl01.mon02.networklayer.com - 0 | 121 | 121 | 22 | 27 | 73 | 23 |

| ae3.bbr01.tl01.nyc01.networklayer.com - 0 | 121 | 121 | 30 | 34 | 73 | 33 |

| ae5.cbs01.tl01.nyc01.networklayer.com - 0 | 121 | 121 | 30 | 37 | 79 | 33 |

| bc.12.2da9.ip4.static.sl-reverse.com - 0 | 121 | 121 | 36 | 41 | 87 | 42 |

| b8.12.2da9.ip4.static.sl-reverse.com - 70 | 33 | 10 | 38 | 42 | 48 | 42 |

| ae29.bbr02.eq01.wdc02.networklayer.com - 0 | 121 | 121 | 36 | 41 | 84 | 40 |

| ae1.dar01.wdc01.networklayer.com - 0 | 121 | 121 | 36 | 41 | 84 | 37 |

| po1.fcr06a.wdc01.networklayer.com - 0 | 121 | 121 | 36 | 41 | 85 | 40 |

| 6f.28.559e.ip4.static.sl-reverse.com - 0 | 121 | 121 | 36 | 40 | 82 | 41 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Me and my Friend (both from germany) have exact the same problem.


freezes everthing (classic packet loss) and after 5-10 seconds it repeats all realy fast.

completly unable to play.




Edit: everything works fine now - no more packet loss.

What packet loss? you sent 121 the server received 121, there is no lag like you claim (15 seconds) even if there was a large spike it would take you to 6000ms then DC you.

So, either you ran the test when you were not playing, you ran the test when you didn't get a spike or the problem you have is not latency related.

When you read an WinMTR trace, if a single line has high packet loss, and the following lines go back to zero, that is not a problem.

Some machines between you and the servers process diagnostic packets at low priority, and discard a proportion of them, simply because they are so very busy. (Typically you see these in the middle of of the path, because that is where you get to the "backbone" of the Internet, rather than a quieter path to or from a single network.)

Packet loss shows up as a line, and every following line, having the same - or almost the same - level of lost packets. (Because when a single link is losing packets, that applies to every packet that crosses it, right? So, you can't have a lower level of loss on anything past it.)

(technically, you can have that, because packet loss is not necessarily completely random, but it should be statistically zero. this is why long traces with lots of packets are asked for - it means that RNG doesn't mess up the trace nearly so much.)