High latency at akamai.com

Suddwrath

This still hasn't received an official response from ZOS?

Korax

Don't think you ever will... don't hold your breath.

jcm2606

Just a reminder that this is still an issue that is potentially crippling to those without a VPN, and it is in dire need of attention.

@ZOS_GinaBruno @ZOS_JessicaFolsom

mrpaxman

I came to the forums of the issues related to this thread i was seeing. Best and worst latency numbers with spikes every 1 to 5 minutes From Melbourne, Aus. Connection is also now being routed through Perth instead of Sydney for us also. These numbers are the only reason i haven't played for weeks since the games release. I come online and its like this again. Opposite of fun in every way. Combat is not exactly reasonable to do in this game. Even worse is that i have a new high end graphics card and 3 year old gaming PC. FPS is when standing still also. 130 FPS is about my normal in all other games. I have saved around $2000 on this game because of its issues in the pics for 2 years now. Unlike my first 2 years and refusing to pay more until things get fixed since back then. I wonder if ZoS has forgot of all the people paying for eso+ for so long when it gave nothing more then 10% exp gains and anyone doing that was doing it to support ZoS in making the game great.

I'd be wasting money if i bought the next expansion or any over priced crown stuff. About $50 real money for a Guar i don't even want from fake gambling, sticking my head in a clown crate. Or waaaaay more from entire other games or expansions costing the same. Not a tough choice. I legitimately still consider this game still in Beta. Wish it wasn't the case. Fun instead of constant frustration is hardly a game. Communication would have saved tons of it over the years also.

Korax

BETA would be an improvement, I still consider this ALPHA... did I say ALPHA? I meant CLOSED ALPHA since I cant access this game since September 2018.

kishrwb17_ESO

Hello folks,
I just found this thread today and I agree with the last post by Korax.
For me, the game has had unusable latency (999+) in crowded areas since about September 2018.
Prior to that latency had been usually ~300+, but still easily playable since 2014.
What happened?

AlwaysSeeingRed

gamer559 wrote: »

Same issue you are having & same results. The problem is with Akamai.

@ZOS_GinaBruno @ZOS_KaiSchober @ZOS_JessicaFolsom @ZOS_BillE @ZOS_GaryA This needs to be addressed!

I gotta say, I have had no latency issues thus far. Seems to me that if it really was just this Akamai service, EVERYONE would be affected. I do believe it is something local on your computers. Some sort of port not opened or maybe an antivirus/firewall is not liking Akamai. But if it really was that service, it would be likely EVERYONE would be affected which is not the case.

MrGarlic

AlwaysSeeingRed wrote: »

SNIP

I gotta say, I have had no latency issues thus far. Seems to me that if it really was just this Akamai service, EVERYONE would be affected. I do believe it is something local on your computers. Some sort of port not opened or maybe an antivirus/firewall is not liking Akamai. But if it really was that service, it would be likely EVERYONE would be affected which is not the case.

@AlwaysSeeingRed Do you live in Australia, New Zealand or South East Asia? If not then this isn't relevant to you. If so then what is your ping? If it is in the red, then you are affected by this, if not, then what is your ISP because I want to swap to that one.

Our problem is ROUTING, the direction our traffic takes via internet hubs, switches etc. In other words it has nothing to do with a service on our client PCs, PS or Xbox. All devices are all affected.

When the Los Angeles Akamai DDoS Prolexic Scrubber was the closest one for the Oceanic and South East Asian regions, our routing was direct across the Pacific. Since the Hong Kong Akamai Prolexic Scrubber came online, we are all directed to Hong Kong, which for many of us is the wrong direction and has added 30-50% extra ping, to an already high ping (220-250ms,) so it is considerable.

Not everyone in the world will be affected as Hong Kong is not the closest Akamai Prolexic DDoS scrubber for EVERYONE.

Routing is the problem, not our client host.

tsaescishoeshiner

It's not just people in Oceania and South East Asia. I live in California and had this problem (constant disconnects and endless error 200 & 108 messages) for over a month until it vanished as quickly as it began. It's been gone for a while now, but came back yesterday. Nothing has changed on my side, although I took all the steps recommended by support. I think it started with the Tuesday patch.

My monthslong back-and-forth ended with the (helpful as can be) support person agreeing a VPN might be something to try, and suggesting that it's not a problem they can say will be fixed soon. They seemed to know it's a broad problem, and possibly why, but are unable to speak on it.

I don't mind the ping so much as not being able to connect and stay connected to ESO. Especially with unpausable ESO+ time burning. It's not the product we're paying for : p

edit: forums turned emoticon into an emoji

DYSEQTA

I have not been able to play Elder Scrolls Online at all since moving to Tasmania, Australia. I get booted from the game within 4 minutes every time. I did some trace routes and low and behold akamai.com is where everything dies. My son pre-ordered the Elsewyr expansion (before we moved here) and has not been able to play it due to this issue. Short of logging in and trying to get research sorted before getting booted there is no game to be played...

traceroute to 198.20.198.110 (198.20.198.110), 30 hops max, 60 byte packets
1 _gateway (xxx.xxx.xxx.xxx) 29.555 ms 29.556 ms 29.502 ms
2 Bundle-Ether2-102.bdr01-ipt-67kenned-hba.au.superloop.com (27.122.116.3) 8.865 ms 8.256 ms 8.735 ms
3 Bundle-Ether1-161.bdr01-ipt-826lorim-mel.au.superloop.com (103.200.13.146) 145.544 ms 145.509 ms 145.480 ms
4 HundredGigE0-0-1-2.106.bdr01-ipt-47bourke-syd.au.superloop.com (103.200.13.112) 144.183 ms 144.146 ms 144.092 ms
5 Bundle-Ether1-104.bdr01-ipt-168yeung-hkg.hk.superloop.com (103.200.14.152) 145.242 ms Bundle-Ether1-102.bdr01-ipt-168yeung-hkg.hk.superloop.com (103.200.14.151) 143.942 ms 143.957 ms
6 prolexic1-lacp-10g.hkix.net (123.255.91.26) 146.829 ms 148.171 ms 146.565 ms
7 po110.bs-b.sech-hkg2.netarch.akamai.com (72.52.2.184) 147.820 ms po110.bs-a.sech-hkg2.netarch.akamai.com (72.52.2.176) 144.468 ms po110.bs-b.sech-hkg2.netarch.akamai.com (72.52.2.184) 147.601 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

traceroute to 198.20.198.110 (198.20.198.110), 30 hops max, 60 byte packets
1 _gateway (xxx.xxx.xxx.xxx) 5.140 ms 5.117 ms 5.059 ms
2 Bundle-Ether2-102.bdr01-ipt-67kenned-hba.au.superloop.com (27.122.116.3) 8.538 ms 8.529 ms 8.157 ms
3 Bundle-Ether1-162.bdr01-ipt-530colli-mel.au.superloop.com (103.200.13.182) 143.653 ms 143.620 ms 143.712 ms
4 HundredGigE0-0-1-2.106.bdr01-ipt-47bourke-syd.au.superloop.com (103.200.13.112) 143.693 ms HundredGigE0-0-1-2.104.bdr01-ipt-4edenpar-syd.au.superloop.com (103.200.13.110) 146.540 ms 146.490 ms
5 Bundle-Ether1-102.bdr01-ipt-168yeung-hkg.hk.superloop.com (103.200.14.151) 143.352 ms Bundle-Ether1-104.bdr01-ipt-168yeung-hkg.hk.superloop.com (103.200.14.152) 145.523 ms 145.055 ms
6 prolexic1-lacp-10g.hkix.net (123.255.91.26) 148.117 ms 147.484 ms 148.037 ms
7 po110.bs-a.sech-hkg2.netarch.akamai.com (72.52.2.176) 144.311 ms po110.bs-b.sech-hkg2.netarch.akamai.com (72.52.2.184) 147.758 ms 147.502 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

MrGarlic

@DYSEQTA

(I would recommend removing the IP address next to your gateway in the post above.)

I would also recommend to you to try a VPN such as Mudfish or Battleping to see if your routing is the problem. Both have a free trial. I use Mudfish.

Also, the main thread for Akamai problems in OCEANIA is this one.
https://forums.elderscrollsonline.com/en/discussion/439549/oceanic-lag-now-300-400-ms-even-with-a-vpn-was-250-300#latest

Best of luck.

DYSEQTA

@MrGarlic thanks.

I have found my VPN can get around the problem. However, I should not be required to make use of a third party service with a cost of it's own to use a service I have already paid for.

MrGarlic

DYSEQTA wrote: »

@MrGarlic thanks.

I have found my VPN can get around the problem. However, I should not be required to make use of a third party service with a cost of it's own to use a service I have already paid for.

I totally agree. It is an extra, albeit small expense, that shouldn't be required.

It never used to be a problem until last September when we started to be routed through Akamai's Hong Kong DDoS scrubber, which went online then. Previously we were routed directly to the USA where the nearest Akamai scrubber was.

However if you want better ping times from your location, it may be necessary. I used to live in Tasmania so I am aware of the problems the extra distance can cause so I am on your side.

BTW, Zos does not care but I would recommend submitting a ticket anyway. They will tell you it's your ISP, which it isn't. It's their choice of anti-DDoS protection causing the problems for our region.

Good luck.

Idinuse

AlwaysSeeingRed wrote: »

gamer559 wrote: »

Same issue you are having & same results. The problem is with Akamai.

@ZOS_GinaBruno @ZOS_KaiSchober @ZOS_JessicaFolsom @ZOS_BillE @ZOS_GaryA This needs to be addressed!

I gotta say, I have had no latency issues thus far. Seems to me that if it really was just this Akamai service, EVERYONE would be affected. I do believe it is something local on your computers. Some sort of port not opened or maybe an antivirus/firewall is not liking Akamai. But if it really was that service, it would be likely EVERYONE would be affected which is not the case.

Wow. You are actually looking at a screen shot that shows a 224 ping at an Akamai server while all other pings are 17-30ms and still pull the "it's on your end" card? O.O Just because on your end you have no problem? Did you do a traceroute yourself? What did it show?

JJBoomer

As well as super high ping, my fps also plummeted after the patch. Sitting at 20 fps... Seriously?

TheFM

I am on the EU server, but have been having a similar issue for years now, maybe itll get some attention now. This is my tracert, it clearly shows the connection gets worse the second it hits the zos servers. Not on my end at all.

mfcostacampos

@ZOS_GinaBruno @ZOS_GaryA @ZOS_KaiSchober @ZOS_BillE @ZOS_JessicaFolsom

You realise that every day that goes by without you people sharing a response to this is a day that you cost your employers more money with people cancelling their subs, right?

technohic

I started looking at this and from Ohio; I get a cleaner connection to the EU server it seems. The US gets to the same location as I see 198.20.198.110 at but it just bounces around in that area until it hits the max hops


Tracing route to 198.20.198.110 over a maximum of 30 hops


3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 40 ms 34 ms 34 ms ce-0-6-0-1.r01.nycmny17.us.bb.gin.ntt.net [157.238.179.117]
8 * * * Request timed out.
9 41 ms 43 ms * ae-3.r22.asbnva02.us.bb.gin.ntt.net [129.250.6.116]
10 38 ms 41 ms 40 ms ae-1.r05.asbnva02.us.bb.gin.ntt.net [129.250.2.20]
11 43 ms 37 ms 39 ms ae-0.a02.asbnva02.us.bb.gin.ntt.net [129.250.5.190]
12 44 ms 33 ms 37 ms 165.254.191.122
13 34 ms 34 ms 35 ms po111.bs-b.sech-iad.netarch.akamai.com [209.200.144.202]
14 34 ms 34 ms 32 ms a72-52-1-189.deploy.static.akamaitechnologies.com [72.52.1.189]
15 39 ms 34 ms 34 ms ae121.access-a.sech-iad.netarch.akamai.com [209.200.144.205]
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.

C:\WINDOWS\system32>tracert 195.122.154.1

Tracing route to 195.122.154.1 over a maximum of 30 hops


3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 36 ms 32 ms 33 ms ce-0-6-0-1.r01.nycmny17.us.bb.gin.ntt.net [157.238.179.117]
9 * * * Request timed out.
10 189 ms 137 ms 41 ms ae-1.a01.nycmny13.us.bb.gin.ntt.net [129.250.6.90]
11 36 ms 36 ms 35 ms 62.159.61.217
12 127 ms 154 ms 132 ms 194.25.6.2
13 127 ms 127 ms 129 ms 195.122.154.1

Trace complete.


This makes me think they have a routing issue from Akami to their servers. Shouldnt need 15 more hops from there.

EDIT: Set max hops to 200 and it just keeps going. Never completes until max hop count reached

MrGarlic

Once the tracert enters the Akamai network, it hits a system that just doesn't respond to ping requests, therefore it will always time out.

It is designed that way.

The ESO server is also configured to ignore ping requests so 'pinging' the servers will also time out.

MrGarlic

Interestingly, my own tracert from NZ to the ESO servers in Europe do not appear to go through Akamai. (Still getting 320 ping though, but that's to be expected.)

technohic

MrGarlic wrote: »

Once the tracert enters the Akamai network, it hits a system that just doesn't respond to ping requests, therefore it will always time out.

It is designed that way.

The ESO server is also configured to ignore ping requests so 'pinging' the servers will also time out.

Yeah Traceroutes will run UTP and not everything will respond with the information, especially secure devices, but I think the connection should complete and not have infinite hops.

aslahnftw

Dont really know why this thread is not being updated (if the problem went away for others or not) but here the problem remains (Brazil).


Rastreando a rota para 198.20.198.110 com no m ximo 30 saltos

1 <1 ms <1 ms <1 ms RT-AC68U-2B30 [192.168.1.1]
2 1 ms <1 ms <1 ms 192.168.15.1
3 * * * Esgotado o tempo limite do pedido.
4 4 ms 4 ms 4 ms 152-255-152-244.user.vivozap.com.br [152.255.152.244]
5 4 ms 3 ms 4 ms 152-255-156-185.user.vivozap.com.br [152.255.156.185]
6 6 ms 6 ms 6 ms 187-100-83-2.dsl.telesp.net.br [187.100.83.2]
7 21 ms 21 ms 21 ms 84.16.10.30
8 127 ms 129 ms 126 ms 5.53.3.147
9 137 ms * 137 ms 213.140.36.89
10 126 ms 125 ms 125 ms ix-ae-16-0.tcore2.mln-miami.as6453.net [66.110.72.30]
11 140 ms 140 ms 138 ms if-ae-1-2.tcore1.mln-miami.as6453.net [63.243.152.61]
12 137 ms 137 ms 137 ms if-ae-7-2.tcore1.aeq-ashburn.as6453.net [66.198.154.177]
13 155 ms 154 ms 155 ms 66.198.154.66
14 678 ms 853 ms 773 ms po111.bs-b.sech-iad.netarch.akamai.com [209.200.144.202]
15 698 ms 733 ms 706 ms a72-52-1-149.deploy.static.akamaitechnologies.com [72.52.1.149]
16 349 ms * 406 ms ae121.access-a.sech-iad.netarch.akamai.com [209.200.144.205]
17 144 ms 144 ms 144 ms a72-52-63-35.deploy.static.akamaitechnologies.com [72.52.63.35]
18 * * * Esgotado o tempo limite do pedido.
19 * * * Esgotado o tempo limite do pedido.
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido.
22 * * * Esgotado o tempo limite do pedido.
23 * * * Esgotado o tempo limite do pedido.
24 * * * Esgotado o tempo limite do pedido.
25 * * * Esgotado o tempo limite do pedido.
26 * * * Esgotado o tempo limite do pedido.
27 * * * Esgotado o tempo limite do pedido.
28 * * * Esgotado o tempo limite do pedido.
29 * * * Esgotado o tempo limite do pedido.
30 * * * Esgotado o tempo limite do pedido.

Rastreamento conclu¡do.

Any oficial answer on this problem?

Tammany

aslahnftw wrote: »

Any oficial answer on this problem?

Reset your router.
Oh, you don't have a router ?
Well, buy one and try to reset it.

BornDownUnder

aslahnftw wrote: »

Dont really know why this thread is not being updated (if the problem went away for others or not) but here the problem remains (Brazil).

--- snip ---
13 155 ms 154 ms 155 ms 66.198.154.66
14 678 ms 853 ms 773 ms po111.bs-b.sech-iad.netarch.akamai.com [209.200.144.202]
15 698 ms 733 ms 706 ms a72-52-1-149.deploy.static.akamaitechnologies.com [72.52.1.149]
16 349 ms * 406 ms ae121.access-a.sech-iad.netarch.akamai.com [209.200.144.205]
17 144 ms 144 ms 144 ms a72-52-63-35.deploy.static.akamaitechnologies.com [72.52.63.35]
--- snip ---

Any oficial answer on this problem?

Whilst not official, your latency issues originate either somewhere between the routing from:

Herndon, VA 20171, USA (66.198.154.66)
to
Cambridge, MA 02142, USA (209.200.144.202)

OR

It is the server that Akamai Technologies uses, which is:
209.200.144.202
Which is most likely a location check (IP location, blacklist check)

After it gets through Akamai routing servers, your latency returns a normal ping of 144ms, the timeouts after are as a result of traceroute request denials, which is normal for game server routing.

MrGarlic

Akamai routing is still a major problem, especially for those of us in New Zealand where our ping-times have had an increase of 30-50% due to being routed to Akamai's Prolexic (anti-DDoS) scrubbers in Sydney, Australia.

We were previously being routed through Hong Kong so it is an improvement, but still far from optimal.

Many of us have stopped playing.

Korax

The problem didn't go away.. the players caring for this stopped caring and likely uninstalled and moved on. Like me.
Since Sept 2018 I'm unable to enjoy this game.. I tried a few months to play, but since given up.. obviously stopping buying the DLCs etc since then.

Now I just check this forum in the hopes that I start not seeing any more login/dc related topics to encourage me to try... but nope, not gonna download 60+ GB of game just to get ticked-off and not enjoy the game.

My life the past almost 2 years is basically checking this forum and subbing WoW.
What else can I really do?

I got better things to do than try over and over to try play this broken game.

starkerealm

Korax wrote: »

The problem didn't go away.. the players caring for this stopped caring and likely uninstalled and moved on. Like me.
Since Sept 2018 I'm unable to enjoy this game.. I tried a few months to play, but since given up.. obviously stopping buying the DLCs etc since then.

Now I just check this forum in the hopes that I start not seeing any more login/dc related topics to encourage me to try... but nope, not gonna download 60+ GB of game just to get ticked-off and not enjoy the game.

My life the past almost 2 years is basically checking this forum and subbing WoW.
What else can I really do?

I got better things to do than try over and over to try play this broken game.

They might be VPNing into The States. That's anther possibility, though I get why that's not an appealing option.

Monocerotis

Saturday 04/07/2020 and the problem remains unchanged.

An event in Cyrodiil and the situation is horrible. 999+ ping frequently and disconnects.

Congratulations, ZOS.

ShawnLaRock

Is this still a potential cause for the current state of the game / something that needs to be addressed in it’s own week of testing?

S.

Gardarik

ShawnLaRock wrote: »

Is this still a potential cause for the current state of the game / something that needs to be addressed in it’s own week of testing?

S.

It is still quite an issue. Not to dub the results of the tracert and pathping again, will leave a link to it. Akamai is still bottlenecking the traffic resulting in packet losses during internal to Akamai network data transfer. Unlike some more fortunate US users, for me the packets are lost upon reaching akamai network with the notice "Request timed out" indicating a high ping. Just for the information, I live in Japan.

So people have the issue with akamai from the US, Australia, NZ, East Asia - it is quite geographically broad. The fact that the issue persists for at least 2 years and that ZOS did not care even to provide an answer to it is frustrating. Damn, ZOS haven't even submitted anything to Akamai apparently, hoping that users will either leave the game or roll with it. This corporate policy is garbage.