Hang then DC

I've been having an issue for a while now where the game periodically stops receiving data from the server and then disconnects after ~3 - ~30 seconds (i.e., kicks me out to the login screen). This has been happening for months and it occurs several times per hour on average.

I am no expert, but I suspect that the issue occurs whenever a single packet is lost.

The curious part is that my client appears to be able to send data to the server. For example, if I open a portal after I am unable to user potions, damage monsters, etc. then that portal will be in the new location after I get disconnected and then log back in again. This suggests to me that it should be possible to recover from this state. For example, if the client can still talk to the server then would it be possible to implement a slash command (e.g., /resync) that causes the client to reestablish communication with the server? This would be a huge help because as it is now I effectively lose a map portal (when soloing) or get get kicked from the group (while grouping) whenever this issue occurs.

I don't have any major issues while playing any other online game which further suggests that this issue could be avoided. I have no issues while playing some online games while I notice brief lag spikes while playing other games.

I attached some WinMTR data. In each case I stopped WinMTR as soon as possible after the issue occurred.

Is there anything I can do to help prevent this issue from occurring (other than change ISPs)? If not, could GGG implement some way for the client and server to reestablish communication?

Thanks for any help!

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| XXX.XX.XXX.1 - 0 | 1772 | 1772 | 1 | 1 | 72 | 1 |
| XXXXXX.XXXXXX.org - 0 | 1772 | 1772 | 1 | 3 | 67 | 2 |
| XXX.wiscnet.net - 0 | 1772 | 1772 | 1 | 10 | 194 | 3 |
| XXX.wiscnet.net - 0 | 1772 | 1772 | 5 | 7 | 78 | 6 |
| r-equinix-isp-xe-3-1-0-2234.wiscnet.net - 0 | 1772 | 1772 | 23 | 26 | 96 | 34 |
| te1-7.bbr01.eq01.chi01.networklayer.com - 0 | 1772 | 1772 | 23 | 24 | 185 | 24 |
| ae20.bbr01.eq01.dal03.networklayer.com - 0 | 1772 | 1772 | 42 | 44 | 118 | 43 |
| ae0.dar02.sr01.dal01.networklayer.com - 0 | 1772 | 1772 | 42 | 44 | 120 | 43 |
| po2.fcr05.sr06.dal01.networklayer.com - 0 | 1772 | 1772 | 43 | 44 | 215 | 43 |
| patch105.pathofexile.com - 1 | 1768 | 1767 | 42 | 42 | 120 | 43 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| XXX.XX.XXX.1 - 0 | 807 | 807 | 1 | 2 | 83 | 1 |
| XXXXXX.XXXXXX.org - 0 | 807 | 807 | 1 | 2 | 79 | 1 |
| XXX.wiscnet.net - 0 | 807 | 807 | 1 | 2 | 70 | 2 |
| XXX.wiscnet.net - 0 | 807 | 807 | 5 | 7 | 73 | 5 |
| r-equinix-isp-xe-3-1-0-2234.wiscnet.net - 0 | 807 | 807 | 23 | 26 | 111 | 51 |
| te1-7.bbr01.eq01.chi01.networklayer.com - 0 | 807 | 807 | 23 | 24 | 103 | 23 |
| ae20.bbr01.eq01.dal03.networklayer.com - 1 | 803 | 802 | 42 | 44 | 134 | 43 |
| ae0.dar02.sr01.dal01.networklayer.com - 0 | 807 | 807 | 42 | 44 | 124 | 43 |
| po2.fcr05.sr06.dal01.networklayer.com - 0 | 807 | 807 | 43 | 45 | 213 | 43 |
| patch101.pathofexile.com - 0 | 807 | 807 | 42 | 43 | 122 | 42 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| XXX.XX.XXX.1 - 0 | 450 | 450 | 1 | 1 | 58 | 1 |
| XXXXXX.XXXXXX.org - 0 | 450 | 450 | 1 | 4 | 73 | 2 |
| XXX.wiscnet.net - 0 | 450 | 450 | 1 | 8 | 78 | 3 |
| XXX.wiscnet.net - 0 | 450 | 450 | 5 | 6 | 54 | 5 |
| r-equinix-isp-xe-3-0-0-3997.wiscnet.net - 0 | 450 | 450 | 23 | 26 | 106 | 23 |
| te1-7.bbr01.eq01.chi01.networklayer.com - 0 | 450 | 450 | 23 | 24 | 85 | 23 |
| ae20.bbr01.eq01.dal03.networklayer.com - 0 | 450 | 450 | 46 | 47 | 142 | 46 |
| ae0.dar01.sr01.dal01.networklayer.com - 1 | 446 | 445 | 46 | 47 | 118 | 46 |
| po1.fcr05.sr06.dal01.networklayer.com - 0 | 450 | 450 | 50 | 52 | 128 | 50 |
| patch104.pathofexile.com - 0 | 450 | 450 | 46 | 46 | 112 | 46 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| XXX.XX.XXX.1 - 0 | 292 | 292 | 1 | 3 | 198 | 1 |
| XXXXXX.XXXXXX.org - 0 | 292 | 292 | 1 | 3 | 199 | 2 |
| XXX.wiscnet.net - 0 | 292 | 292 | 1 | 4 | 198 | 2 |
| XXX.wiscnet.net - 0 | 292 | 292 | 5 | 8 | 203 | 6 |
| r-equinix-isp-xe-0-0-0-3946.wiscnet.net - 0 | 292 | 292 | 23 | 26 | 219 | 24 |
| te1-7.bbr01.eq01.chi01.networklayer.com - 0 | 292 | 292 | 23 | 25 | 218 | 40 |
| ae20.bbr01.eq01.dal03.networklayer.com - 0 | 292 | 292 | 44 | 47 | 239 | 45 |
| ae0.dar02.sr01.dal01.networklayer.com - 0 | 292 | 292 | 44 | 47 | 239 | 46 |
| po2.fcr05.sr06.dal01.networklayer.com - 0 | 284 | 282 | 48 | 52 | 248 | 49 |
| patch105.pathofexile.com - 1 | 284 | 282 | 44 | 46 | 503 | 44 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hey ljlevend,

We have implemented an /oos command into Path of Exile that resyncs you should you temporarily disconnect, but it sounds like your latency issues may be more severe than this command would fix. Unfortunately the WinMTR reports you have provided are too long to truly identify the cause of your problem. Next time you run a WinMTR can you please capture your disconnection? I would recommend no more than 400 packets sent while you are experiencing this issue, and be sure to perform this trace to your preferred gateway (listed on the WinMTR link provided above).

Additionally, feel free to Verify your Game Files and run the GGPK Defragmenter tool if you use the Standalone Client.
Need Support? support@grindinggear.com.
"
Yeran_GGG wrote:
Hey ljlevend,

We have implemented an /oos command into Path of Exile that resyncs you should you temporarily disconnect, but it sounds like your latency issues may be more severe than this command would fix. Unfortunately the WinMTR reports you have provided are too long to truly identify the cause of your problem. Next time you run a WinMTR can you please capture your disconnection? I would recommend no more than 400 packets sent while you are experiencing this issue, and be sure to perform this trace to your preferred gateway (listed on the WinMTR link provided above).

Additionally, feel free to Verify your Game Files and run the GGPK Defragmenter tool if you use the Standalone Client.

Thank you for the feedback.

You mentioned that my latency "may be more severe", but the latency columns look very good to me. Average latencies are around 50 and there was only one instance where the worst latency got over 250.

To me the WinMTR data suggests that this is an issue with lost packets rather than latency. Like I said, I stopped all of the sample WinMTR acquisitions immediately after the disconnect occurred in an attempt to capture the issue. All of my WinMTR samples show a single "1" in the "Lost %" column, which I assume means that a packet was lost. I've only seen all 0's in the "Lost %" column if the issue hasn't occurred.

You requested a WinMTR capture with less than 400 packets, but the last WinMTR capture in my original post only has 292 packets sent. Is there a reason why that capture is inadequate? I can capture more, but I just want to make sure that I get you the information that you need.

Also, you are right that /oos does not work. It would be great to have the ability to manually reestablish communication since my client is able to talk to the server after the issue occurs. But, /oos doesn't seem to perform that function. Would it be possible for GGG to implement a slash command for this purpose?

Thanks again for your help.
There is no real packet loss going on in any of your traces as far as I can tell.

In most of the traces, the Sent/Received from your first hop matches those on the last (or second to last) hop.

In the cases where it doesn't, it is either on the very last hop (which makes it harder to diagnose) or is inconsistent. Any packet loss % appearing in the "loss %" column is not real packet loss unless the loss of packets continues through all hops afterward... only then was the packet potentially really loss.... otherwise what you're seeing is likely congestion and dropping ICMP packets (low priority) addressed to itself... failing to reply to an ICMP request does not mean that packets are being dropped... just that the node isn't responding to them for some reason. It's not necessarily an issue.
"
Drakier wrote:
There is no real packet loss going on in any of your traces as far as I can tell.

In most of the traces, the Sent/Received from your first hop matches those on the last (or second to last) hop.

In the cases where it doesn't, it is either on the very last hop (which makes it harder to diagnose) or is inconsistent. Any packet loss % appearing in the "loss %" column is not real packet loss unless the loss of packets continues through all hops afterward... only then was the packet potentially really loss.... otherwise what you're seeing is likely congestion and dropping ICMP packets (low priority) addressed to itself... failing to reply to an ICMP request does not mean that packets are being dropped... just that the node isn't responding to them for some reason. It's not necessarily an issue.

Thank you. That makes sense and is good to know.

Is there any way to use this information in order to help avoid the issue from occurring or to help reestablish communication after the issue occurs?

I don't have any major issues while playing other online games so it should be possible to improve PoE's handling of what you described. I can't change ISPs so I'm not sure if there is anything I can do on my end, although I'm willing to try if somebody has an idea.

Thanks.
I had this same problem, died 3 times on beyond :/ /oos doesnt work , dunno whats dat.
I was doing some testing by playing two different characters on two different clients that were running at the same time on the same computer.

For simplicity lets call them Character A on Client A, and Character B on Client B.

During this testing Client A stopped receiving data from the server, but Client B appeared to be fine. At the time this occurred Character A was in an instance and Character B was in town, but they both were in the same group. So, I opened Character A's inventory and right-clicked on a portal scroll. The portal did not appear on Client A, but it did appear on Client B. I was able to enter the portal with Character B and kill monsters, user potions, etc. with Character B. Furthermore, if I moved Character A then I could see Character A moving in Client B. But, Character B never showed up in Client A.

After a while Client A was disconnected.

Doesn't this confirm that PoE should be able to recover from this issue? It seems to me that all you would need is a slash command (and/or an automated system) that tells the server to reestablish communication. Keep in mind that I have no major issues with any other online game.

GGG, you there? Any plans to address this issue? Do you need more information? Should I just accept it and let this thread die?
i'm having this same issue. I notice if I ping the website the problem is the same. Sounds to me like a routing problem.

What ISP are you guys on, and what region?
My Shop: http://www.pathofexile.com/forum/view-thread/1338089
"
conall88 wrote:
i'm having this same issue...

Good to know I'm not alone.

IMO the fundamental issue is that the game doesn't seem to make any attempt to recover communication between the client and the server. Minor communication issues will occur regardless of your region or ISP. Every other online game that I've tried seems to understand this and has mechanics built in to deal with it. But with PoE it feels like your connection will be lost if a single electron starts spinning in the wrong direction.

Report Forum Post

Report Account:

Report Type

Additional Info