Lag, latency, and disconnects
|
In the middle of combat or running around in a hideout, my character will stop responding and my latency chart spikes, frequently (but not always) followed by a disconnect. The client doesn't crash, just kicks me to the login screen with "An unexpected disconnection occurred".
I was playing on the same computer with the same internet setup earlier (around 5 or 6 am east coast US) without trouble, then started having a lot of trouble around 7 or 8am. The internet is hardwired, not wifi. The issue is occurring on 2 different computers. I tried picking a different gateway from the drop menu, nothing changed. My default choice is Washington, D.C. As per the directions, I ran WinMTR, though I've never used it before and don't really know how to interpret the data. |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 345 | 345 | 0 | 0 | 6 | 0 | | 172.16.224.1 - 0 | 345 | 345 | 12 | 20 | 58 | 14 | | static-65-175-142-81.cpe.metrocast.net - 0 | 345 | 345 | 14 | 23 | 52 | 21 | | TBD-65-175-128-2.metrocast.net - 0 | 345 | 345 | 13 | 22 | 58 | 16 | |te0-7-0-7.ccr21.bos01.atlas.cogentco.com - 0 | 345 | 345 | 14 | 23 | 55 | 17 | | be2094.ccr41.jfk02.atlas.cogentco.com - 0 | 345 | 345 | 20 | 28 | 63 | 22 | | be2060.ccr21.jfk05.atlas.cogentco.com - 0 | 345 | 345 | 20 | 29 | 66 | 24 | | No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 | | 4.35.90.138 - 1 | 341 | 340 | 27 | 44 | 112 | 49 | | ae1.bbr01.eq01.wdc02.networklayer.com - 0 | 345 | 345 | 53 | 67 | 138 | 72 | | ae7.bbr02.eq01.wdc02.networklayer.com - 3 | 317 | 310 | 40 | 66 | 117 | 64 | | ae1.dar01.wdc01.networklayer.com - 0 | 345 | 345 | 49 | 68 | 130 | 70 | | po1.fcr06a.wdc01.networklayer.com - 1 | 341 | 340 | 52 | 68 | 126 | 72 | | 6f.28.559e.ip4.static.sl-reverse.com - 4 | 305 | 295 | 44 | 67 | 104 | 61 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Edit [11:25am]: Being unable to play, I've been spending some time on Google trying to educate myself on WinMTR interpretation. Looks like my problems start at 4.35.90.138, which turns up Path of Exile on Google and seems to be a shared point in the various WinMTR postings here in the forums... so am I correct in thinking this is GGG's IP? Last edited by Anathaema_Noctis#5398 on Aug 21, 2016, 11:30:33 AM Last bumped on Aug 22, 2016, 3:10:44 PM
|
|
" We've a node not responding and it's followed by one exhibiting minor packet loss. It's difficult to know where exactly the problem begins due to the lack of data, but I'd be suspicious of the mystery node as often a router will stop processing non-essential traffic if it becomes congested. While often you'll see a node configured not to process non-essential traffic all of the time, the following node having packet loss does suggest the issue begins one step prior. " The IP address 4.35.90.138 appears to be registered to Level 3 Communications. They're a tier 1 ISP. They own a lot of the backbone infrastructure in the US. Grinding Gear Games' partner is Network Layer, who doesn't show up in your WinMTR until an increase in latency and minor packet loss have already started appearing at a previous hop. GGG do not offer first-party Technical Support.
Free Technical Support guides are available here: https://www.poecommunity.help No ads, trackers, or other weird stuff. |
|
" Thanks very much for taking the time to explain this. |
|
|
No problem!
I posted quite late last night and was overly distracted by your edit, for which I apologize. Looking at your WinMTR again this morning with a coffee at hand I'm concerned by this; " I have to say that your ping reaching as high as 58 to the first hop of your ISP's network is a little alarming. Running a quick trace route to Google.ie I see pings of 17 ms, 13 ms and 14 ms. This is more in line with what I'd expect from something so close to my home. It's difficult to determine whether this is indicating an issue between your modem and your ISP, or whether it's simply your ISP saying "whelp, that's a lot of pings" and de-prioritizing ICMPs. Have you been playing any other online games? If other games are also affected then that would indicate the high pings at the start of your connection are relevant, whereas other online games not having any problems would suggest it's just traffic shaping. Internet providers often view the protocols used for diagnostics as being low priority when compared to, say, people playing online games which are very latency-sensitive. It's not uncommon for them to intentionally throttle such "non-essential traffic" so that it doesn't cause network congestion which would impact what they view as more legitimate use of their infrastructure. It doesn't help that some DDoS attacks have been performed using ICMP packets, though this is more of an excuse than a true reason for ISPs to discriminate against them. Really, as outsiders all we can do is poke your connection in a variety of ways, see how it responds and interpret such responses to the best of our ability. It can be tempting to leap to assumptions but the reality of the situation is that networking is quite complicated and trace routes, pathpings and WinMTRs can't detect every potential issue. GGG do not offer first-party Technical Support.
Free Technical Support guides are available here: https://www.poecommunity.help No ads, trackers, or other weird stuff. |
|
|
First, the good news: starting a few hours after my post edit, about an hour after the 48-hr race ended, I was able to play using the California realm without getting disconnects. Washington DC is still flaky, managed to get a disconnect this morning also, testing with a low lvl map to see if it would kick me. California is still working without disconnects, despite the ping on the login screen showing as much higher than Washington.
" Never underestimate the importance of coffee! :) " My router is as ancient as the Vaal ruins, if that explains anything. If it's an issue at or after the modem, though, nothing wrong with the hardware that I know of. " No. If I have time for gaming, it's pretty much always Path of Exile. (So hyped for Atlas...!) " Again, thanks so much for the time and effort. I appreciate how dedicated the knowledgable ppl on the forums are to assisting with the gameplay experience, and I've been able to learn a lot from this process. Hopefully in the future this knowledge can be used to keep things running more smoothly without taking up so much time from tech support. |
|
|
I was wondering if it would be okay if I added my input to the situation. I'm wondering if the problem might not be at the node previously thought. This is the hop that was bringing up some suspicion:
| 4.35.90.138 - 1 | 341 | 340 | 27 | 44 | 112 | 49 | And the previous hop, with no responses at all: | No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 | I'd agree they are suspicious, but they may not actually be the source of the problem. Check out a hop following those two: | ae1.bbr01.eq01.wdc02.networklayer.com - 0 | 345 | 345 | 53 | 67 | 138 | 72 | This following node shows the same number of packets sent / received as the initial node. So, I'd be inclined to think the previous two node are de-prioritizing/rejecting icmp traffic as a means of load mitigation. So we can probably say that the information being displayed from those two hops isn't useful. It could be a sign of load problems around that point of your route causing spikes/increased response times for latency, but it could be standard traffic mitigation. It's not accurate information ( since it is contradicted by the following hop ). A couple hops later, you still see no loss, though your latency is climbing to a point where you'd notice if using lock step in game: | ae1.dar01.wdc01.networklayer.com - 0 | 345 | 345 | 49 | 68 | 130 | 70 | Averaging 68ms with spikes up to 130ms may cause some stuttering, however, this is within the network layer hops, and there isn't much you can do about it. That is where ( I think ) problems start to become worrying. Here are the final two hops: | po1.fcr06a.wdc01.networklayer.com - 1 | 341 | 340 | 52 | 68 | 126 | 72 | | 6f.28.559e.ip4.static.sl-reverse.com - 4 | 305 | 295 | 44 | 67 | 104 | 61 | Now, it's hard to say if that is true packet loss, or just more traffic mitigation. At any rate, what we do know is that traffic is getting to the 3rd last hop. I'm wondering if this is a traffic or stability issue with the WDC gateway, rather than a problem with your route. I know you've gone through a lot of troubleshooting already, but would you mind running a WinMTR test to a known good location? I usually suggest the Google public DNS server located at 8.8.8.8 If you have solid routes with no loss there, I'm wondering if the problem might be the gateway. "I would have listened... I would have understood!" - Scion
Have you removed Asus ROG/GameFirst yet? |
|
" Speeds may look a little different today due to 2 people on the home network, instead of just me. Below is the Win MTR for 8.8.8.8 - |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 346 | 346 | 0 | 0 | 8 | 0 | | 172.16.224.1 - 0 | 346 | 346 | 10 | 24 | 142 | 19 | | static-65-175-142-81.cpe.metrocast.net - 0 | 346 | 346 | 11 | 27 | 151 | 25 | | TBD-65-175-128-2.metrocast.net - 1 | 343 | 342 | 14 | 27 | 149 | 21 | |te0-7-0-19.ccr21.bos01.atlas.cogentco.com - 0 | 346 | 346 | 14 | 27 | 150 | 25 | | be2094.ccr41.jfk02.atlas.cogentco.com - 21 | 190 | 151 | 20 | 105 | 404 | 335 | | be2060.ccr21.jfk05.atlas.cogentco.com - 1 | 343 | 342 | 19 | 32 | 155 | 24 | | tata.jfk05.atlas.cogentco.com - 0 | 346 | 346 | 20 | 33 | 153 | 31 | |if-ae-12-2.tcore1.N75-New-York.as6453.net - 0 | 346 | 346 | 19 | 34 | 155 | 36 | | 72.14.218.224 - 1 | 343 | 342 | 18 | 33 | 156 | 29 | | 216.239.63.95 - 0 | 346 | 346 | 20 | 34 | 152 | 33 | | 108.170.235.85 - 1 | 343 | 342 | 21 | 34 | 157 | 27 | | google-public-dns-a.google.com - 0 | 346 | 346 | 20 | 33 | 158 | 37 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Here is the WinMTR for the Washington realm, which gave me unexpected disconnects as recently as a few hours ago - |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 348 | 348 | 0 | 0 | 8 | 0 | | 172.16.224.1 - 0 | 348 | 348 | 10 | 24 | 155 | 17 | | static-65-175-142-81.cpe.metrocast.net - 0 | 348 | 348 | 12 | 27 | 159 | 20 | | TBD-65-175-128-2.metrocast.net - 0 | 348 | 348 | 12 | 28 | 164 | 19 | |te0-7-0-7.ccr21.bos01.atlas.cogentco.com - 0 | 348 | 348 | 12 | 27 | 163 | 18 | | be2094.ccr41.jfk02.atlas.cogentco.com - 1 | 344 | 343 | 19 | 33 | 183 | 21 | | be2060.ccr21.jfk05.atlas.cogentco.com - 1 | 344 | 343 | 18 | 34 | 185 | 25 | | No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 | | 4.35.90.138 - 0 | 348 | 348 | 18 | 33 | 168 | 28 | | ae1.bbr01.eq01.wdc02.networklayer.com - 0 | 348 | 348 | 41 | 55 | 186 | 46 | | ae7.bbr02.eq01.wdc02.networklayer.com - 0 | 348 | 348 | 38 | 52 | 185 | 46 | | ae1.dar01.wdc01.networklayer.com - 1 | 340 | 338 | 41 | 56 | 186 | 49 | | po1.fcr06a.wdc01.networklayer.com - 1 | 340 | 338 | 42 | 56 | 188 | 49 | | 6f.28.559e.ip4.static.sl-reverse.com - 1 | 344 | 343 | 41 | 56 | 201 | 45 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Here is the WinMTR for the California realm, which has NOT been causing disconnections - |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 347 | 347 | 0 | 0 | 7 | 0 | | 172.16.224.1 - 0 | 347 | 347 | 10 | 23 | 136 | 20 | | static-65-175-142-98.cpe.metrocast.net - 0 | 347 | 347 | 10 | 26 | 139 | 27 | | TBD-65-175-128-2.metrocast.net - 0 | 347 | 347 | 13 | 26 | 141 | 25 | | multi-use.cogentco.com - 0 | 347 | 347 | 13 | 26 | 141 | 25 | | be2299.ccr21.alb02.atlas.cogentco.com - 0 | 347 | 347 | 18 | 30 | 141 | 26 | | be2878.ccr21.cle04.atlas.cogentco.com - 1 | 343 | 342 | 27 | 40 | 159 | 37 | | be2717.ccr41.ord01.atlas.cogentco.com - 1 | 343 | 342 | 35 | 48 | 166 | 43 | | be2831.ccr21.mci01.atlas.cogentco.com - 1 | 343 | 342 | 47 | 59 | 175 | 51 | | be3035.ccr21.den01.atlas.cogentco.com - 1 | 339 | 337 | 59 | 70 | 193 | 69 | | be3037.ccr21.slc01.atlas.cogentco.com - 1 | 343 | 342 | 68 | 81 | 197 | 78 | | be2087.ccr22.sfo01.atlas.cogentco.com - 0 | 347 | 347 | 85 | 97 | 214 | 92 | | be2165.ccr22.sjc01.atlas.cogentco.com - 1 | 343 | 342 | 85 | 99 | 205 | 94 | |be2661.rcr11.b023785-1.sjc01.atlas.cogentco.com - 0 | 347 | 347 | 86 | 100 | 233 | 93 | | 38.104.134.70 - 1 | 343 | 342 | 87 | 99 | 200 | 96 | | border5.pc2.bbnet2.sje011.pnap.net - 8 | 269 | 250 | 86 | 102 | 293 | 102 | | inapvoxcust-3.border3.sje011.pnap.net - 1 | 343 | 342 | 85 | 101 | 209 | 105 | | 216.52.30.71 - 0 | 347 | 347 | 86 | 99 | 233 | 88 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider I don't mind a little bit of lag or stutter - we have 2 computers but only one good video card, lol, so a bit of stutter feels normal. It's the freeze-and-disconnect that was killing my ability to play. |
|
|
Your results to 8.8.8.8 look fine. You do have spikes showing up at every hop after your router. It's not serious from the looks of it, and maybe a quick power cycle of your local networking gear will get rid of that.
Your results to the WDC realm still shows stable until you get to the last couple hops of the route. The California gateway results look better: | 216.52.30.71 - 0 | 347 | 347 | 86 | 99 | 233 | 88 | You are getting now packet loss. However, your average latency is higher. Likely because the number of hops / distance you are away from the CA gateway. I think there is a bit of an issue with the WDC gateway atm. At least coming from your route. Is Texas any better? Maybe it would be a good compromise between average latency and stability. "I would have listened... I would have understood!" - Scion
Have you removed Asus ROG/GameFirst yet? |
|
