Extreme latency 999+ game unplayable

AngryFire

For the past 3 days starting around 5 pm or so and lasting until 1-3 am my latency goes from 100 to 999+ the entire evening. The game is unplayable and very frustrating. Tracert and Pathping below.


Tracing route to 198.20.198.110 over a maximum of 30 hops

1 <1 ms <1 ms 9 ms Linksys [192.168.1.1]
2 16 ms 9 ms 4 ms 192.168.0.1
3 116 ms 30 ms 19 ms d192-24-1-64.col.wideopenwest.com [24.192.64.1]
4 17 ms 18 ms 13 ms dynamic-76-73-172-253.knology.net [76.73.172.253]
5 18 ms 19 ms 29 ms 76-73-167-202.knology.net [76.73.167.202]
6 15 ms 15 ms 10 ms 76-73-166-126.knology.net [76.73.166.126]
7 24 ms 24 ms 26 ms user-69-73-2-4.knology.net [69.73.2.4]
8 60 ms 112 ms 40 ms dynamic-75-76-35-13.knology.net [75.76.35.13]
9 48 ms 27 ms 22 ms akamai.prolexic.com [206.126.236.219]
10 56 ms 59 ms 59 ms po110.bs-a.sech-iad.netarch.akamai.com [209.200.144.192]
11 43 ms 54 ms 50 ms ae120.access-a.sech-iad.netarch.akamai.com [209.200.144.197]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.



Tracing route to 198.20.198.110 over a maximum of 30 hops

0 DosPC.wowway.com [192.168.1.101]
1 Linksys [192.168.1.1]
2 192.168.0.1
3 d192-24-1-64.col.wideopenwest.com [24.192.64.1]
4 dynamic-76-73-172-253.knology.net [76.73.172.253]
5 76-73-167-202.knology.net [76.73.167.202]
6 76-73-166-126.knology.net [76.73.166.126]
7 user-69-73-2-4.knology.net [69.73.2.4]
8 dynamic-75-76-35-13.knology.net [75.76.35.13]
9 akamai.prolexic.com [206.126.236.219]
10 po110.bs-a.sech-iad.netarch.akamai.com [209.200.144.192]
11 ae120.access-a.sech-iad.netarch.akamai.com [209.200.144.197]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DosPC.wowway.com [192.168.1.101]
0/ 100 = 0% |
1 5ms 0/ 100 = 0% 0/ 100 = 0% Linksys [192.168.1.1]
0/ 100 = 0% |
2 16ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
3 21ms 0/ 100 = 0% 0/ 100 = 0% d192-24-1-64.col.wideopenwest.com [24.192.64.1]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% dynamic-76-73-172-253.knology.net [76.73.172.253]
0/ 100 = 0% |
5 23ms 0/ 100 = 0% 0/ 100 = 0% 76-73-167-202.knology.net [76.73.167.202]
0/ 100 = 0% |
6 23ms 0/ 100 = 0% 0/ 100 = 0% 76-73-166-126.knology.net [76.73.166.126]
0/ 100 = 0% |
7 33ms 0/ 100 = 0% 0/ 100 = 0% user-69-73-2-4.knology.net [69.73.2.4]
0/ 100 = 0% |
8 39ms 0/ 100 = 0% 0/ 100 = 0% dynamic-75-76-35-13.knology.net [75.76.35.13]
0/ 100 = 0% |
9 35ms 0/ 100 = 0% 0/ 100 = 0% akamai.prolexic.com [206.126.236.219]
100/ 100 =100% |
10 --- 100/ 100 =100% 0/ 100 = 0% po110.bs-a.sech-iad.netarch.akamai.com [209.200.144.192]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% ae120.access-a.sech-iad.netarch.akamai.com [209.200.144.197]

Trace complete.

Please advise

Justmee

Use Wireshark and sniff the packets and find out what the IP of the server
you are on you can capture the packets to see exactly what the IP
is of the server you are on. Then do a traceroute and a tcptraceroute
to that IP.

Doing just random traceroutes to other sites isn't going to help them diagnose
the problem.

See my ticket here this is the proper way to troubleshoot a high latenency
issue

https://forums.elderscrollsonline.com/en/discussion/436992/high-latency-at-akamai-com#latest

So how did you determine that you are connected to the server at 198.20.198.110
did you already capture the packets or did you just look at another
post? Are you sure that is the server YOU are connecting to did you use wireshark
or a simular program to capture the packets first to make sure?

You can get Wireshark to capture the packets and see what server you are on
when you are in game at https://wireshark.org/

For tcptraceroute follow the instructions here it
gives you the download link too
https://namecheap.com/support/knowledgebase/article.aspx/9777/2194/how-to-use-tcp-traceroute

Some reason this URL is not linking properly on the forums

https://www.namecheap.com/support/knowledgebase/article.aspx/9777/2194/how-to-use-tcp-traceroute


If you are on Windows you also need the winpcap as well for the tcptraceroute which
can be downloaded at
https://winpcap.org/install/default.htm

Tracetcp is located at the link bellow
https://github.com/SimulatedSimian/tracetcp/releases

Because to be quite honest your times when you did the tracert to 198.20.198.110
look good actually.. see in mine I am seeing it bottle neck at one hop all the time..
your times are actually good!

Tracing route to 198.20.198.110 over a maximum of 30 hops

1 <1 ms <1 ms 9 ms Linksys [192.168.1.1]
2 16 ms 9 ms 4 ms 192.168.0.1
3 116 ms 30 ms 19 ms d192-24-1-64.col.wideopenwest.com [24.192.64.1]
4 17 ms 18 ms 13 ms dynamic-76-73-172-253.knology.net [76.73.172.253]
5 18 ms 19 ms 29 ms 76-73-167-202.knology.net [76.73.167.202]
6 15 ms 15 ms 10 ms 76-73-166-126.knology.net [76.73.166.126]
7 24 ms 24 ms 26 ms user-69-73-2-4.knology.net [69.73.2.4]
8 60 ms 112 ms 40 ms dynamic-75-76-35-13.knology.net [75.76.35.13]
9 48 ms 27 ms 22 ms akamai.prolexic.com [206.126.236.219]
10 56 ms 59 ms 59 ms po110.bs-a.sech-iad.netarch.akamai.com [209.200.144.192]
11 43 ms 54 ms 50 ms ae120.access-a.sech-iad.netarch.akamai.com [209.200.144.197]

That is the traceroute I am talking about that you did. Also when you get * or time out
that just means that the device has been setup to not answer ICMP requests and that
is why you get a timeout and a * that is normal so don't panic about that.

But I mean your times are actually really good highest looking to be about 112 ms
and most in the 40 - 60 ms range. in mine I am getting times at one
hop of over 200 ms at one hop constantly I don't see any issues here they are
going to need more info to trouble shoot this try doing what I said above..

AngryFire

Thanks for responding and I will take your advice.

Where did I get that IP, from the ESO website

https://help.elderscrollsonline.com/app/answers/detail/a_id/30903/~/how-do-i-do-a-pathping-and-tracert-to-the-servers-to-test-my-connection?

and yes I understand they are blocking pings, what is off is the EU server does not.

Thanks

AngryFire

The IP 198.20.198.110 appears to be the login server. Once the ESO client is connected and a character loaded there are two persistent connections to:

198.20.200.23
198.20.200.158

I am assuming 198.20.200.158 is the actual server connection however both show the exact same latency issues. I ran PingPlotter Pro on the server IP for about an hour (721 pings). Please take a look at the attached photo:



The latency issue starts after akamai.prolexic.com so the issue appears to be with the ddos/security provided by prolexic/akamai.

I am able to connect through VPN originating from a few cities and get my ping down to 400 or so, which is still unplayable. But I should not have to do so.

I have spent several days with support (ticket 180928-003649) doing exactly as they instructed all of which was focused on my network, my isp, my computer and my settings. I understand that, I have been working on the web on the technical side for 30 years now, but this issue is not on my end, I am not the only one having these types of connection issues.

This latency issue starts 12-2pm weekends and approx 4-5pm weekdays EST and settles down around 2-3am. My normal latency has always been 80-150ms and has been for the most part since ESO launched on steam. I am an ESO plus member, so this is extremely frustrating that the only hours I can play I can not because of latency beyond my control. I certainly hope ZOS is willing to credit for time lost as this is going on a week thus far.

Thank you

DUTCH_REAPER

Don’t worry though...we are getting music boxes for houses.......

AngryFire

So,



Ping is now normal as the traffic slows, exactly as it has been the past week. Support, they give canned responses and when all is said and done they tell you this:

"Hello,

We appreciate this screen shot and letting us know the previous steps have now been attempted.

Due to all the steps you've now taken, from here we would advise for you to contact your ISP about your current connection.

Thank you for your continued interest and support!

Kind Regards,
xxxxxxx
The Elder Scrolls Online Team"

If this continues I will request either a credit of missed days, a refund of my recently renewed ESO Plus membership or if I have to dispute it and go back to BDO.

I get it, traffic will go down in a week or two due to the additional load from the summer fall event and you do not wish to waste any more money to fix a problem that will go away on its own with time. But to blame my isp when the obvious problem is staring you in the face is downright lazy.

AngryFire

It appears akamai.prolexic.com machine changed from 206.126.236.219 to a new ip/machine at 208.115.136.35 at around 3.45PM EST this afternoon. po110 and ae120 also changed IP's as well. There is also a new machine sitting before the ESO server.

To whomever at ESO that took the time to look into and fix this, I thank you.

taraza11

I am having this issue now as of the last 3-4 days.. my ISP is Spectrum and I have called them repeatedly trying to get a fix. They says I need to speak with ESO customer support as my modem's signal is strong on their end.

My latency is typically between 500-10000, and is especially high when I'm grouped. I even get disconnected around every 30 minutes. The game has become unplayable.

Tracing route to 198.20.200.23 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 16 ms 12 ms 15 ms cpe-142-105-32-1.nj.res.rr.com [142.105.32.1]
3 17 ms 10 ms 14 ms be63.plpknj4602h.nyc.rr.com [68.173.202.226]
4 19 ms 6 ms 19 ms agg132.nyquny9101r.nyc.rr.com [68.173.198.82]
5 18 ms 22 ms 15 ms bu-ether25.nycmny837aw-bcr00.tbone.rr.com [107.14.19.22]
6 21 ms 15 ms 17 ms 0.ae1.pr1.nyc20.tbone.rr.com [107.14.17.218]
7 18 ms 14 ms 15 ms 66.109.7.42
8 18 ms 17 ms 9 ms ae16.cs2.lga5.us.zip.zayo.com [64.125.29.222]
9 14 ms 18 ms 20 ms ae17.er3.lga5.us.zip.zayo.com [64.125.27.47]
10 15 ms 16 ms 18 ms 208.184.23.222.IPYX-143212-001-ZYO.zip.zayo.com [208.184.23.222]
11 14 ms 13 ms 19 ms po110.bs-a.sech-lga.netarch.akamai.com [23.57.97.243]
12 12 ms 10 ms 15 ms ae120.access-a.sech-lga.netarch.akamai.com [23.57.97.249]
13 25 ms 20 ms 23 ms 93.191.173.122
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Tracing route to 198.20.200.158 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 10 ms 18 ms 9 ms cpe-142-105-32-1.nj.res.rr.com [142.105.32.1]
3 13 ms 28 ms 10 ms be63.plpknj4601h.nyc.rr.com [68.173.202.224]
4 14 ms 14 ms 13 ms agg132.nyclnyrg01r.nyc.rr.com [68.173.198.80]
5 19 ms 23 ms 14 ms bu-ether19.nwrknjmd67w-bcr00.tbone.rr.com [66.109.6.78]
6 23 ms 23 ms 26 ms bu-ether12.nycmny837aw-bcr00.tbone.rr.com [66.109.6.27]
7 15 ms 14 ms 10 ms 0.ae1.pr1.nyc20.tbone.rr.com [107.14.17.218]
8 17 ms 13 ms 11 ms 66.109.7.42
9 17 ms 14 ms 16 ms ae16.cs2.lga5.us.zip.zayo.com [64.125.29.222]
10 15 ms 10 ms 15 ms ae17.er3.lga5.us.zip.zayo.com [64.125.27.47]
11 16 ms 14 ms 12 ms 208.184.23.222.IPYX-143212-001-ZYO.zip.zayo.com [208.184.23.222]
12 19 ms 19 ms 13 ms po110.bs-a.sech-lga.netarch.akamai.com [23.57.97.243]
13 14 ms 15 ms 14 ms ae120.access-a.sech-lga.netarch.akamai.com [23.57.97.249]
14 23 ms 18 ms 21 ms 93.191.173.122
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 *

wouldn't even complete