Network problems - Troubleshooting

So I log in to PoE, play for 30 sec- 1m, sometimes a few minutes or perhaps until I change to a different zone and my ping goes from a stable 60 to 1.8k-1.9k lag spike that flatlines and forces me to drop it to the log in screeen. After that I try to play again and the same thing happens. This has been happening ever since the ascendancy launched. Note that I have been playing the game for years and never had ANY latency issues and havent changed my isp provider in at least 5 years. Obviously the problem is on my side, right?

I then proceed to test things on world of tanks, wow, league of legends, hs, HoTs and random stuff on the internet and guess what, ZERO latency issues. I get no lag, no stuttering, no spikes and I can play fine for hours. Now will someone please acknowledge that there IS a problem and that it could be on YOUR side? I have been paying attention to the latency issues thread where people are complaining daily, it has reached almost over 53 pages and not ONE GGG response to it. Clearly the problem is on their end, packet loss, bad isp provider, fairy dust clogging the cables and ofc the magical router reset ritual people failed to do.

I apologize for sounding rude here, the person who made this thread clearly did it in order to help people who do have some of these problems and I am sure it will help some of them. But dear God you cant expect me to believe that it is somehow my problem that only YOUR game is completely unplayable due to lag spikes.

I hope this gets sorted out otherwise it will piss people off and they will move onto other games despite the fact that they really wanted to play this one.

"

Now will someone please acknowledge that there IS a problem and that it could be on YOUR side? I have been paying attention to the latency issues thread where people are complaining daily, it has reached almost over 53 pages and not ONE GGG response to it. Clearly the problem is on their end, packet loss, bad isp provider, fairy dust clogging the cables and ofc the magical router reset ritual people failed to do.

All of this is true. But they still keep avoid problems, dodge all complains and answer "not our side" at any server/stability problem, for like almost 1 year.

The last Chris Wilson speach from reddit was epic, he has zero clue on how improve his servers stability, he even asked on reddit how to do, thats pure epicness, i just hope he read the answer from trackpete. Because yes, the top 1 from ggg need to go to reddit to know how to improve his own game.

And yes they will never admit that their EU ISP is total garbage too. Better say that this is the customer's ISP even if they got like a lot of different ones (even if that could mean that problem is not on customer's side xD).

I will keep post about that until things will change or i get banned because i guess they will be angry to read that people are aware on how they manage to dodge/ignore every EU server issues from this forum section ...

They could be working on this as we speak. I dont doubt that they wish to have stable servers for their own game and that they did not desire any of this. Problems arise and they have to be dealt with.

What bothers me is that they avoid the problem and fail to acknowledge it. It insults ones intellect if they truly think that an explanation like " well, it could be on your end and you should contact your isp provider " is sufficient and if they believe people should just accept it. Especially if people thoroughly tested the issue on other games and found zero latency issues.

I dont believe we are being unreasonable here. We are just asking for answers and hoping you are going to provide some.

I was going step by step with this, and when I did the "netstat"

There we go, much more than 3-5 lines?I dont have anything open, except Avast Antivirus.
My current main problem is that every time I go into any group my latency,
goes form 25-40 to 200-800 (Connected to London server)

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Robert>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:49547 Lightdark:65001 ESTABLISHED
TCP 127.0.0.1:58898 Lightdark:58899 ESTABLISHED
TCP 127.0.0.1:58899 Lightdark:58898 ESTABLISHED
TCP 127.0.0.1:58901 Lightdark:58902 ESTABLISHED
TCP 127.0.0.1:58902 Lightdark:58901 ESTABLISHED
TCP 127.0.0.1:65001 Lightdark:49547 ESTABLISHED
TCP 192.168.0.2:58622 msnbot-191-232-139-62:https ESTABLISHED
TCP 192.168.0.2:59244 lon16:http ESTABLISHED
TCP 192.168.0.2:64474 wk-in-f100:https TIME_WAIT
TCP 192.168.0.2:64480 wk-in-f139:https TIME_WAIT
TCP 192.168.0.2:64481 wk-in-f139:https TIME_WAIT
TCP 192.168.0.2:64504 wk-in-f97:https TIME_WAIT
TCP 192.168.0.2:64513 7c:https TIME_WAIT
TCP 192.168.0.2:64522 ams10-009:https TIME_WAIT
TCP 192.168.0.2:64527 r-175-58-45-5:http TIME_WAIT
TCP 192.168.0.2:64528 191.232.139.253:https ESTABLISHED
TCP 192.168.0.2:64529 65.55.44.109:https ESTABLISHED
TCP [::1]:27275 Lightdark:64524 TIME_WAIT
TCP [::1]:27275 Lightdark:64525 TIME_WAIT
TCP [::1]:27275 Lightdark:64526 TIME_WAIT

C:\Users\Robert>

TCP 127.0.0.1:49699 DESKTOP-FA2OTJ4:49700 ESTABLISHED
TCP 127.0.0.1:49700 DESKTOP-FA2OTJ4:49699 ESTABLISHED
TCP 127.0.0.1:49702 DESKTOP-FA2OTJ4:49703 ESTABLISHED
TCP 127.0.0.1:49703 DESKTOP-FA2OTJ4:49702 ESTABLISHED
TCP 127.0.0.1:65001 DESKTOP-FA2OTJ4:65338 ESTABLISHED
TCP 127.0.0.1:65338 DESKTOP-FA2OTJ4:65001 ESTABLISHED
TCP 192.168.1.88:52979 a23-32-11-44:http ESTABLISHED
TCP 192.168.1.88:60076 msnbot-191-232-139-86:https ESTABLISHED
TCP 192.168.1.88:60083 fra02-006:http ESTABLISHED
TCP 192.168.1.88:60119 msnbot-191-232-139-58:https ESTABLISHED
TCP [2001:b07:644f:4573:3d3a:c8e6:a979:7776]:51726 [2a02:26f0:4:192::10]:https ESTABLISHED
TCP [2001:b07:644f:4573:3d3a:c8e6:a979:7776]:52855 [2001:41a8:26:19a::7b]:https ESTABLISHED
TCP [2001:b07:644f:4573:3d3a:c8e6:a979:7776]:52951 [2001:b00:1:2::2e4:2e73]:http TIME_WAIT

this is my netstat... i've all closed except avast... from few times i get dc from the game... but what i don't understand is that after the dc also normal internet don't work for some seconds... but it start just when i'm playing poe, not normally staying in browser... any idea?

Rather than necroing an old thread, can you make your own. Take a look at the stickies, find the connection primer, DL and run winMTR for 300-500 seconds for us. Need to see what your trace looks like.

Sorry to bother but i'm kinda desperate, i dont have much knowledge about internet, connections and stuff like that i just want to play the game.



Thanks for the help.

Not often but sometime i take a freeze on game and i see that my latency go from 75ms to 1000 for a short period then back to 75.....

i try to do a netstat but i don't know why it seem to connect to the server then take dc.....

Connessioni attive

Proto Indirizzo locale Indirizzo esterno Stato
TCP 192.168.1.100:49444 mil04s03-in-f2:http CLOSE_WAIT
TCP 192.168.1.100:49445 mil04s03-in-f2:http CLOSE_WAIT
TCP 192.168.1.100:49447 mil04s03-in-f2:https TIME_WAIT
TCP 192.168.1.100:49462 mil04s03-in-f2:http CLOSE_WAIT
TCP 192.168.1.100:49468 mil04s03-in-f2:http CLOSE_WAIT
TCP 192.168.1.100:49474 mil04s04-in-f8:http CLOSE_WAIT
TCP 192.168.1.100:49481 mil04s03-in-f6:http CLOSE_WAIT
TCP 192.168.1.100:49482 mil02s05-in-f66:https TIME_WAIT
TCP 192.168.1.100:49487 62.67.193.75:http ESTABLISHED
TCP 192.168.1.100:49488 2.18.240.144:http ESTABLISHED
TCP 192.168.1.100:49492 a104-83-96-246:http ESTABLISHED
TCP 192.168.1.100:49493 65:http CLOSE_WAIT
TCP 192.168.1.100:49497 mil04s03-in-f6:https TIME_WAIT
TCP 192.168.1.100:49498 199.38.164.165:http ESTABLISHED
TCP 192.168.1.100:49504 a104-83-83-24:https ESTABLISHED
TCP 192.168.1.100:49507 a92-123-180-187:http ESTABLISHED
TCP 192.168.1.100:49514 a92-123-180-187:http ESTABLISHED
TCP 192.168.1.100:49523 mil02s05-in-f66:http CLOSE_WAIT
TCP 192.168.1.100:49565 7c:https CLOSE_WAIT
TCP 192.168.1.100:49566 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:49567 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:49568 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:49569 ec2-52-41-109-104:https CLOSE_WAIT
TCP 192.168.1.100:49585 mil04s03-in-f14:https ESTABLISHED
TCP 192.168.1.100:49586 mil04s04-in-f6:https ESTABLISHED
TCP 192.168.1.100:49587 fra15s16-in-f14:https ESTABLISHED
TCP 192.168.1.100:49588 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:49589 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:49590 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:49591 ed:6112 ESTABLISHED
TCP 192.168.1.100:49592 ec2-52-41-109-104:https CLOSE_WAIT
TCP 192.168.1.100:49593 ec2-52-41-109-104:https CLOSE_WAIT
TCP 192.168.1.100:49594 ec2-52-41-109-104:https CLOSE_WAIT
TCP 192.168.1.100:49604 fra15s09-in-f46:https ESTABLISHED
TCP 192.168.1.100:49611 40.77.226.249:https TIME_WAIT
TCP 192.168.1.100:49612 151.101.36.193:http ESTABLISHED
TCP 192.168.1.100:49613 ec2-52-32-193-108:https CLOSE_WAIT
TCP 192.168.1.100:49620 a23-223-64-185:http TIME_WAIT
TCP 192.168.1.100:49627 fra07s30-in-f14:https ESTABLISHED
TCP 192.168.1.100:49628 mil04s23-in-f110:https ESTABLISHED
TCP 192.168.1.100:65445 db5sch101101024:https ESTABLISHED
TCP 192.168.1.100:65446 db5sch101101629:https ESTABLISHED
TCP 192.168.1.100:65455 wm-in-f188:https ESTABLISHED

C:\Users\user>


any advice?

C:\Users\user>netstat

Connessioni attive

Proto Indirizzo locale Indirizzo esterno Stato
TCP 192.168.1.100:55242 db5sch101110626:https ESTABLISHED
TCP 192.168.1.100:55243 db5sch101101001:https ESTABLISHED
TCP 192.168.1.100:55264 wa-in-f188:5228 ESTABLISHED
TCP 192.168.1.100:55338 195.216.249.66:http ESTABLISHED
TCP 192.168.1.100:55420 151.101.36.166:http CLOSE_WAIT
TCP 192.168.1.100:55428 185.86.138.32:http ESTABLISHED
TCP 192.168.1.100:55437 62.67.193.75:http ESTABLISHED
TCP 192.168.1.100:55495 151.101.36.134:http CLOSE_WAIT
TCP 192.168.1.100:55496 151.101.36.134:http CLOSE_WAIT
TCP 192.168.1.100:55505 104.156.81.134:http CLOSE_WAIT
TCP 192.168.1.100:55508 104.244.42.136:https ESTABLISHED
TCP 192.168.1.100:55510 151.101.36.249:https CLOSE_WAIT
TCP 192.168.1.100:55511 104.156.81.134:https CLOSE_WAIT
TCP 192.168.1.100:55512 151.101.36.249:http CLOSE_WAIT
TCP 192.168.1.100:55513 151.101.36.64:https CLOSE_WAIT
TCP 192.168.1.100:55514 151.101.36.249:http CLOSE_WAIT
TCP 192.168.1.100:55515 151.101.36.249:http ESTABLISHED
TCP 192.168.1.100:55516 151.101.36.249:http CLOSE_WAIT
TCP 192.168.1.100:55517 151.101.36.134:https ESTABLISHED
TCP 192.168.1.100:55617 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:55618 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:55619 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:55620 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:55621 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:55628 a23-50-147-58:https ESTABLISHED
TCP 192.168.1.100:55663 f2:6112 ESTABLISHED

C:\Users\user>


And this is the actual situation.....

Posting 'raw' netstat output isn't really going to provide any useful insight about your system. Looking at entries that have TIME_WAIT or CLOSE_WAIT are only showing connections that are in the process of being closed (TCP connections don't close instantly).

If you really want to see the current ESTABLISHED connections use something like:

netstat -o | findstr ESTABLISHED

The number in the right-most column is the PID, so you could use:

tasklist | findstr /c:"PID"

to find the process name.

Or:

netstat -ab

to show the process associated with the connection.

If you want to make like easier, just task manager/resource monitor or something like TCPView/CurrPorts

That said, realistically, looking at this information in isolation is not going to tell you very much.