Akamai routing ESO though Sydney, Australia

dmvab · December 2019

@ZOS_GinaBruno

I'm from Brazil.
Before maintenance, I had around 180 up to max 200 in non pvp maps.
After maintenance, I have constantly 400+++ ping in non pvp maps.
In Cyrodiil I can't even play since goes to 600+ up to 999+
Please, help us. ESO it's completely unplayable right now.

lordxyrax_ESO · December 2019

Northern New Jersey. 300+ ping here as well

Shantu · December 2019

Located in the USA, Illinois.

ArchangelIsraphel · December 2019

I'm located in Massachusetts, USA. We're getting about 400 ping here, it's insane, we usually have about 130 or lower. I play with two other people in my family, and we normally have no issues whatsoever.

Loralai_907 · December 2019

Well Gina, all of my friends and myself are all experiencing this increased ping issue, and we are located all over the US from the east coast to Alaska. I'll double check with my friends in Canada once they get on later today.

For myself, I have gone up over 200 for general things and sometimes getting spikes of 300-450 greater than normal. It is quite the issue and we of course are all rather concerned.

TPishek · December 2019

Northern Minnesota, ping staying consistently in the mid 300s on both PC/NA and on PTS. PC/EU is ~180.

LegacyDM · December 2019

I’m in Hawaii.

imbrifer · December 2019

CT USA

LucyferLightbringer · December 2019

200 extra ping on PCNA thanks to Akamai. Poland

Salvas_Aren · December 2019

Oh, sorry, did not know that the party who agreed on a contract is that helpless.

itsfatbass · December 2019

"Q4 2019: Update 24

Memory management overhaul and behind-the-scenes combat ability improvements phase 1
This is now live on the PC/Mac servers and coming to the PlayStation®4 and Xbox One on November 5 with Update 24.
We are monitoring for live feedback and fixing bugs. The next incremental patch on PC/Mac and XB1/PS4 will have additional stability fixes and improvements.
Complete rewrite of the Looking for Group system
This is now live on the PC/Mac, PlayStation®4, and Xbox One servers.
Since this went live, we’ve made some adjustments and fixed some performance-related problems on the live servers including some last week. We are still working on fixing bugs as we identify them. We have additional work in progress to further improve the system that should be completed before Update 25 launches."

Just wanted to show you that they have ALREADY implemented the first part of this performance improvement MONTHS ago now. Before you point fingers at others for not reading, I'd suggest you do some yourself. And they are correct, the performance improvements have done absolutely nothing so far. In fact, things are MORE broken then before.

DarkShadowFax · December 2019

Playing PC-NA from the Netherlands. A quick tracert showed me I was being routed through Sydney as well.

CaffeinatedMayhem · December 2019

Seattle, WA for PC/NA

No traceroute to post, but consistently over 300 ping. Normal is 120-150. Definitely not local ISP, other games do not have the issue.

Ashtaris · December 2019

An earlier post from someone in Eastern Washington indicated their ping rate was much higher but they were on a different network. We are both on Comcast and everything seems normal on our end. 100ms pings here. No rerouting being done from Akamai US to Australia at this point. Keeping my fingers crossed the Akamai virus doesn't spread

Tracing route to 198.20.198.110 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 10.0.0.1
2 11 ms 11 ms 8 ms x.x.x.x
3 13 ms 12 ms 9 ms po-301-1204-rur02.spokane.wa.seattle.comcast.net [68.85.145.189]
4 15 ms 19 ms 17 ms be-37-ar01.seattle.wa.seattle.comcast.net [68.86.96.5]
5 25 ms 23 ms 23 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
6 17 ms 16 ms 19 ms be-10846-pe01.seattle.wa.ibone.comcast.net [68.86.86.90]
7 17 ms 19 ms 16 ms 66.208.232.186
8 21 ms 20 ms 20 ms port-b1-link.telia.net [62.115.115.23]
9 35 ms 37 ms 35 ms palo-b22-link.telia.net [62.115.115.24]
10 38 ms 37 ms 38 ms sjo-b21-link.telia.net [62.115.125.1]
11 38 ms 37 ms 40 ms akamai-ic-317098-sjo-b21.c.telia.net [62.115.146.121]
12 37 ms 36 ms 37 ms po110.bs-a.sech-sjc.netarch.akamai.com [209.200.184.192]
13 * * * Request timed out.
14 49 ms 39 ms 40 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197]
15 67 ms 68 ms 69 ms a72-52-29-88.deploy.static.akamaitechnologies.com [72.52.29.88]
16 68 ms 68 ms 68 ms 198.20.192.4
17 71 ms 67 ms 68 ms 198.20.198.110

Trace complete.

Number_51 · December 2019

Good job leaving out the part where they said "potential minor performance improvement". Although I'll call it even since they also said "greatly improved stability", and that was a complete fail.

Yngol · December 2019

Russia

KlaytonH · December 2019

My ping has gone from 90-110 to 290+. I live in NA and play on the NA server.

Contaminate · December 2019

My ping went from 70-80 to ~350, I live in Texas

Maxx7410 · December 2019

server is in texas you live in texas but you go to Australia to go to texas!!! so efficient system

Growlf · December 2019

Near St. Gallen, Switzerland. Up to last "maintenance" I had a ping of 170 to 200, now 380- 420.
Connection: Salt Fiber , 10 Gb/s glass fibre.

elvigy · December 2019

In Charlotte, NC using Google Fiber on the PC/NA server. Pings in game are hovering around 300 with spikes to 700 when attempting any action.

Speedtest result for my PC-

and tracert results

Tracing route to 198.20.198.110 over a maximum of 30 hops

1
2
3
4
5
6
7 32 ms 32 ms 32 ms 192.119.18.46
8 32 ms 32 ms 32 ms 23-255-224-194.mci.googlefiber.net [23.255.224.194]
9 32 ms 32 ms 32 ms 23-255-224-203.mci.googlefiber.net [23.255.224.203]
10 42 ms 42 ms 55 ms v211.core1.mci3.he.net [184.105.18.33]
11 52 ms 52 ms 52 ms 100ge12-1.core1.den1.he.net [184.105.64.49]
12 62 ms 62 ms 64 ms e0-36.core2.sjc2.he.net [184.104.192.214]
13 62 ms 62 ms 62 ms 100ge16-1.core1.sjc2.he.net [184.104.192.213]
14 62 ms 69 ms 70 ms 10ge4-4.core1.sjc1.he.net [72.52.92.117]
15 74 ms 74 ms 74 ms vocus.gigabitethernet2-13.core1.sjc1.he.net [64.71.184.46]
16 224 ms 228 ms 228 ms bundle-153.cor02.sjc01.ca.vocus.net [49.255.255.24]
17 224 ms 224 ms 224 ms 100g-0-0-0-0.cor01.sjc01.ca.vocus.net [49.255.255.4]
18 230 ms 229 ms 229 ms BE-200.cor02.syd04.nsw.VOCUS.net.au [49.255.255.11]
19 225 ms 224 ms 224 ms bundle-101.bdr01.syd11.nsw.vocus.net.au [114.31.192.83]
20 229 ms 229 ms 230 ms 49.255.93.14
21 228 ms 228 ms 228 ms po110.bs-b.sech-syd3.netarch.akamai.com [23.57.108.245]
22 * * * Request timed out.
23 229 ms 229 ms 229 ms ae121.access-a.sech-syd3.netarch.akamai.com [23.57.108.251]
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.

Zazariz · December 2019

South Carolina. Usually around 100 ms and now lucky if I am under 300

LegacyDM · December 2019

I wonder if the repeal to Net neutrality has anything to do with it. Probably not... It's just a routing error...

Although... Hypothetically, the service provider (in this case Akamai) can now throttle and charge Zos more for usage. If ZoS didn't agree to pay the increased prices, customers (us) could get throttled or rerouted to a slower cheaper route...

Orpheaus · December 2019

Western Colorado. Has been nearly unplayable since patch.

Shantu · December 2019

Located in USA, Illinois. Normally 70-80 ms. After 12/18 maintenance 300-700 ms

Tracing route to 198.20.198.110 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms local
2 6 ms 17 ms 10 ms local
3 25 ms 14 ms 28 ms local
4 17 ms 14 ms 19 ms 68-66-73-70.client.mchsi.com [68.66.73.70] <---Chicago, IL
5 17 ms 15 ms 19 ms po10.chgil001er1.mchsi.com [68.66.73.122] <---Chicago, IL
6 15 ms 14 ms 15 ms ae10.cr9-chi1.ip4.gtt.net [69.174.18.237] <---Chicago, IL
7 20 ms 24 ms 24 ms chi-b21-link.telia.net [213.248.88.102] <---Chicago, IL
8 16 ms 18 ms 16 ms akamai-ic-326536-chi-b21.c.telia.net [213.248.74.223] <---Chicago, IL
9 15 ms 17 ms 15 ms po110.bs-a.sech-ord.netarch.akamai.com [23.57.98.243] <---The Netherlands
10 18 ms 17 ms 15 ms a72-52-1-177.deploy.static.akamaitechnologies.com [72.52.1.177] <---Cambridge, MA
11 18 ms 19 ms 19 ms ae120.access-a.sech-ord.netarch.akamai.com [23.57.98.249] <---The Netherlands
12 40 ms 28 ms 30 ms 93.191.173.229 <---United Kingdom (Cambridge, England)
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
Request timed out continues through 30 hops

MinuitPro · December 2019

Similar situation in Wisconsin as well. Noticed 300 ping last night.

Tracing route to 198.20.198.110 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms [local]
2 * * * Request timed out.
3 8 ms 9 ms 9 ms 96-34-7-69.static.unas.mt.charter.com [96.34.7.69]
4 9 ms 11 ms 10 ms crr01stptwi-bue-100.stpt.wi.charter.com [96.34.30.236]
5 12 ms 12 ms 12 ms crr02euclwi-bue-400.eucl.wi.charter.com [96.34.24.83]
6 12 ms 12 ms 12 ms crr01euclwi-bue-300.eucl.wi.charter.com [96.34.24.136]
7 19 ms 14 ms 22 ms bbr01euclwi-bue-100.eucl.wi.charter.com [96.34.2.153]
8 19 ms 14 ms 22 ms bbr02euclwi-bue-5.eucl.wi.charter.com [96.34.0.7]
9 33 ms 39 ms 31 ms bbr01chcgil-bue-1.chcg.il.charter.com [96.34.0.9]
10 34 ms 30 ms 29 ms prr01chcgil-bue-2.chcg.il.charter.com [96.34.3.9]
11 70 ms 70 ms 75 ms eqix-ch1.vocusconnect.com [208.115.136.142]
12 220 ms 219 ms 220 ms bundle-153.cor02.lax01.ca.vocus.net [49.255.255.14] [Melborne!]
13 216 ms 216 ms 216 ms 100g-0-0-0-0.cor02.sjc01.ca.vocus.net [49.255.255.3]
14 225 ms 235 ms 225 ms 100g-0-0-0-0.cor01.sjc01.ca.vocus.net [49.255.255.4]
15 224 ms 225 ms 224 ms 100g-0-0-0-0.cor01.lax01.ca.vocus.net [49.255.255.1]
16 225 ms 225 ms 226 ms bundle-200.cor01.alb01.akl.vocus.net.nz [114.31.202.44]
17 225 ms 226 ms 225 ms BE-201.cor01.syd11.nsw.VOCUS.net.au [114.31.202.53]
18 220 ms 221 ms 222 ms BE-1.cor02.syd04.nsw.VOCUS.net.au [114.31.192.41]
19 222 ms 222 ms 221 ms bundle-101.bdr01.syd11.nsw.vocus.net.au [114.31.192.83]
20 226 ms 225 ms 227 ms 49.255.93.14
21 226 ms 225 ms 226 ms po110.bs-a.sech-syd3.netarch.akamai.com [23.57.108.243]
22 * * * Request timed out.
23 227 ms 226 ms 226 ms ae120.access-a.sech-syd3.netarch.akamai.com [23.57.108.249]
24-30 * * * Request timed out.

anadandy · December 2019

East Coast, United States. Ping has been redlining all day - 300+, spiked to 999+ in hubs. Usually 90 tops unless I'm in Cyrodiil.

Dagoth_Rac · December 2019

New Jersey. ISP = Optimum Online. Pings went from 100 to 300. Per tracert, routing to akamai goes through Australia. In particular, there is a significant delay between cogentco.com (Washington D.C. based) and vocus.net (Australia based) before hitting akamai Australia.

>tracert 198.20.198.110

Tracing route to 198.20.198.110 over a maximum of 30 hops

  1     2 ms    <1 ms     1 ms  192.168.1.1
  2     9 ms    11 ms     9 ms  10.240.163.157
  3     9 ms    11 ms    11 ms  67.59.231.0
  4    16 ms    11 ms    11 ms  ool-4353f91e.dyn.optonline.net [67.83.249.30]
  5    14 ms    14 ms    14 ms  67.59.251.78
  6    13 ms    15 ms    12 ms  64.15.3.112
  7    13 ms    12 ms    26 ms  be3033.rcr21.ewr02.atlas.cogentco.com [154.54.11
.77]
  8    15 ms    12 ms    12 ms  be2601.rcr24.jfk01.atlas.cogentco.com [154.54.40
.49]
  9    14 ms    12 ms    13 ms  be2897.ccr42.jfk02.atlas.cogentco.com [154.54.84
.213]
 10    33 ms    34 ms    36 ms  be2890.ccr22.cle04.atlas.cogentco.com [154.54.82
.245]
 11    36 ms    36 ms    36 ms  be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.
129]
 12    47 ms    48 ms    50 ms  be2832.ccr22.mci01.atlas.cogentco.com [154.54.44
.169]
 13    58 ms    59 ms    58 ms  be3036.ccr22.den01.atlas.cogentco.com [154.54.31
.89]
 14    71 ms    68 ms    68 ms  be3038.ccr32.slc01.atlas.cogentco.com [154.54.42
.97]
 15    81 ms    81 ms    81 ms  be3110.ccr22.sfo01.atlas.cogentco.com [154.54.44
.141]
 16    86 ms    85 ms    86 ms  be3179.ccr22.sjc01.atlas.cogentco.com [154.54.43
.150]
 17    85 ms    85 ms    85 ms  be2095.rcr21.b001848-1.sjc01.atlas.cogentco.com
[154.54.3.138]
 18    85 ms    85 ms    85 ms  38.122.92.2
 19   238 ms   237 ms   237 ms  bundle-150.cor01.sjc01.ca.vocus.net [49.255.255.
18]
 20   238 ms   239 ms   238 ms  BE-200.cor02.syd04.nsw.VOCUS.net.au [49.255.255.
11]
 21   238 ms   238 ms   239 ms  bundle-101.bdr01.syd11.nsw.vocus.net.au [114.31.
192.83]
 22   235 ms   234 ms   235 ms  49.255.93.14
 23   238 ms   238 ms   238 ms  po110.bs-b.sech-syd3.netarch.akamai.com [23.57.1
08.245]
 24     *        *        *     Request timed out.
 25   239 ms   238 ms   241 ms  ae121.access-a.sech-syd3.netarch.akamai.com [23.
57.108.251]
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *

TheFM · December 2019

Lol this is the exact same thing that happens to me, live next door to the server, and instead of going straight there it goes to Switzerland and around Germany, to Holland and back to Frankfurt, lol.

elvigy · December 2019

Oddly, just a minute ago it dropped back to the 70-90 range that is normal for me. This is the first time since the patch went live yesterday that it has been in that range. Let's see if it lasts.