Akamai routing ESO though Sydney, Australia

phwaap

Colorado. Totally unplayable overnight.

Maxx7410

Rosario argentina 200+ extra ping

Jem_Kindheart

Geographically I'm near the Eastern coast, USA. I spoke at length with players in game who were having problems, while a select few seem to be exempt from the latency increase. Mine did not go up, and hangs around the usual 120-130 with small blips to 300ish.

Almost all players I spoke with had double to triple latency from before yesterday's maintenance. (Yes yes, we're all aware that Oceanic players are used to this. Their data does have to travel half the globe after all. That doesn't make it normal for US data to have to go halfway around the globe AND still come back to Texas lol.)

Ming ping traces show the same routing through Aus as others.

From my satcom conx, it's obviously going to be horrid, this is on my ISP end since it goes to space and back. I use a diff conx for raids:


From my 4G/5G conx with no VPN Tunnel, what I usually game on, not bad timings tbh:


From my 4G/5G conx with VPN Tunnel nearby my side, only adds about 10-20ms in game:


As a point of reference, I ran a speedtest from me to Dallas, it's ofc modern speeds and a great ping.

AntonShan

ZOS_GinaBruno wrote: »

Hey all, can could you please let us know where you are located geographically? That will help us as we continue to look into a few potential solutions.

Russian Federation. Playing on PC/NA.

mrbum1234b16_ESO

Toanis wrote: »

When you look up the IP's you're routed from Opal Telecom UK to Hurricane Electric UK. Within their network you're then routed to New York (80ms), San Jose (140ms) then Sidney (295ms) and finally given over to Akamai AU that route you back to the US.

WTF indeed.

dont forget the last ip is in amsterdam before it starts timing out....literally goes around the world lol

Bagatur

ZOS_GinaBruno wrote: »

Hey all, can could you please let us know where you are located geographically? That will help us as we continue to look into a few potential solutions.

Bulgaria. Both NA and EU server affected, doubled or higher ping. I tried different ISP, my cell phone operator(different than land line fiber optic, my main connection), same doubled. Meanwhile I have 30-50 ms to any server in Frankfurt, included in speedtest.net list, except the Vodafone one, where my ping was 120 ms.

Bagatur

Just to add, it was same issue yesterday after maintenance, but settled withing an hour. It was OK until I went to bed, around 2:00 UTC.

Kiwigal

well obviously I'm in New Zealand & my in game latency had jumped from low 200s to over 300 when I was crafting earlier & I was thinking why has it got so bad as the event hasn't even started. So I went off & played Path of Exile. I sure hope they can get this fixed before the event starts in approx 1 hour.

Roztlin45

East USA , NA server 300+ping after maintenance, 90-100 ping before.

Jem_Kindheart

That's the weirdest thing, is that it even increased Ocanic players' ping lol

Bagatur

Well, it went to almost normal now, 80 ms.

apophis999

ZOS_GinaBruno wrote: »

Hey all, can could you please let us know where you are located geographically? That will help us as we continue to look into a few potential solutions.

Seattle, Washington. ~90ms ping normally, >300ms now. gigabit fiber. Observed and still an issue at time of posting.

Elandryn

PC/NA playing from Brazil having ping issues since yesterday, went from around 180ms to over 400ms, still had problems this morning.

code65536

@ZOS_GinaBruno

I'm located in the US, in North Carolina using Google Fiber. Right now, my ping to PC/NA is almost twice that of my ping to PC/EU. And when I look at the route that I'm taking, I'm passing through Sydney, Australia on my way to the PC/NA server.

PC/NA:

Tracing route to 198.20.200.23 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  harbinger [172.16.64.1]
  2     2 ms     2 ms     2 ms  10.26.1.219
  3     3 ms     2 ms     2 ms  23-255-225-139.mci.googlefiber.net [23.255.225.139]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    37 ms    36 ms    35 ms  192.119.18.46
  7    36 ms    36 ms    36 ms  23-255-224-194.mci.googlefiber.net [23.255.224.194]
  8    37 ms    37 ms    35 ms  23-255-224-203.mci.googlefiber.net [23.255.224.203]
  9    58 ms    46 ms    54 ms  v211.core1.mci3.he.net [184.105.18.33]
 10    58 ms    67 ms    58 ms  100ge12-1.core1.den1.he.net [184.105.64.49]
 11    67 ms    68 ms    67 ms  e0-36.core2.sjc2.he.net [184.104.192.214]
 12    67 ms    68 ms    67 ms  100ge16-1.core1.sjc2.he.net [184.104.192.213]
 13    66 ms    73 ms    86 ms  100ge13-2.core1.sjc1.he.net [184.105.65.113]
 14    68 ms    67 ms    67 ms  vocus.gigabitethernet2-13.core1.sjc1.he.net [64.71.184.46]
 15   222 ms   219 ms   222 ms  bundle-153.cor02.sjc01.ca.vocus.net [49.255.255.24]
 16   222 ms   222 ms   222 ms  BE-201.cor02.syd04.nsw.VOCUS.net.au [49.255.255.13]
 17   219 ms   218 ms   218 ms  bundle-101.bdr01.syd11.nsw.vocus.net.au [114.31.192.83]
 18   223 ms   222 ms   222 ms  49.255.93.14
 19   222 ms   222 ms   222 ms  po110.bs-b.sech-syd3.netarch.akamai.com [23.57.108.245]
 20     *        *        *     Request timed out.
 21   223 ms   223 ms   223 ms  ae121.access-a.sech-syd3.netarch.akamai.com [23.57.108.251]

PC/EU:

Tracing route to 159.100.232.160 over a maximum of 30 hops

  1     2 ms    <1 ms    <1 ms  harbinger [172.16.64.1]
  2     2 ms     2 ms     2 ms  10.26.1.219
  3     2 ms     2 ms     2 ms  23-255-225-139.mci.googlefiber.net [23.255.225.139]
  4     *        *        *     Request timed out.
  5    12 ms    12 ms    13 ms  192.119.18.105
  6    31 ms    12 ms    17 ms  ix-ae-60-0.tcore1.a56-atlanta.as6453.net [64.86.113.186]
  7    13 ms    13 ms    12 ms  64.86.113.14
  8     *        *        *     Request timed out.
  9   111 ms   118 ms   110 ms  212.162.9.150
 10   111 ms   112 ms   112 ms  195.122.154.3
 11   111 ms   112 ms   110 ms  159.100.232.160

It seems that Akamai is used only for PC/NA, not for PC/EU, since I don't see them in my EU traceroute, and I don't recall seeing it in the EU traceroutes that I've done in the past.

StytchFingal

Prince Edward Island, Canada. Ping hovering around 300 since first login after maintenance yesterday on PC-NA; it is normally in the 130 to 150/160 range.

As a comparison my EU server ping is about 180 today, which is about where it normally sits (I didn't check it yesterday).

apophis999

My tracert

heaven13

ZOS_GinaBruno wrote: »

Hey all, can could you please let us know where you are located geographically? That will help us as we continue to look into a few potential solutions.

East coast, USA (North Carolina).

You can see my trace route to the US server here. I'm getting routed to Virginia then California, Australia, and back to Virginia.


And to EU, for giggles.


Like @Jem_Kindheart I did a ping test to Dallas - 49.


Just doing writs on my characters takes far longer than normal. Doing world boss fights resulted in deaths where normally there wouldn't be. I had to cancel both vBRP and vDSA runs yesterday because no way I could properly perform with my ping the way it is and not be a detriment to the rest of my group.

Ode2Order

ZOS_GinaBruno wrote: »

Hey all, can could you please let us know where you are located geographically? That will help us as we continue to look into a few potential solutions.

PC/EU connecting from the Netherlands

Bagatur

....and after normalizing for about 30-40 minutes, my ping went bonkers again. I'm afraid of this event, very afraid....

midnight_tea

ZOS_GinaBruno wrote: »

Hey all, can could you please let us know where you are located geographically? That will help us as we continue to look into a few potential solutions.

PC playing on NA from Poland. My average for ESO is around 180-210, but ever since yesterday it's 380-450.

mrfrontman

Melbourne, Australia. Gone from 220 ping (with a VPN) to 420 ping. Also 420 ping without a VPN, tested.

Tevalaur

While multiple players from the state of Washington have commented it affects them, I can say it doesn't affect everyone in the state who routes through Seattle. My latency is 133 and I live a ways north of Seattle. So perhaps the different ISPs should be considered as well, at least for us Americans?

I'm on Xfinity/Comcast for reference.

Cymotrichous

ZOS_GinaBruno wrote: »

Hey all, can could you please let us know where you are located geographically? That will help us as we continue to look into a few potential solutions.

I live and play in Philippines and typically has a ping ~220-240. Right after the maintenance, its over ~260-290. This is quite saddening despite that we were neglected to have our own Oceanic server yet we have still to endure this issue.

My tracer shows right after Akamai ping, it disappears into oblivion.

Jannisaries

I live near Smithers, B.C. Canada and my ping is solid at 300 lol. My ESO+ is supposed to renew in a few days but I think I will hold off on that until this is resolved. Shame really....

Olauron

@ZOS_GinaBruno

Geographically located: St. Petersburg, Russia. Ping almost doubled (from 230 to 400).
Tracert to 198.20.198.110:

Tracing route to 198.20.198.110 over a maximum of 30 hops

  1     9 ms     2 ms     2 ms  --
  2     *        *        *     Request timed out.
  3    17 ms    18 ms    17 ms  --
  4    29 ms    39 ms    55 ms  as6939.ix.dataix.ru [178.18.224.229]
  5   155 ms   183 ms   162 ms  100ge8-2.core1.ams1.he.net [184.105.65.125]
  6    70 ms    59 ms    82 ms  100ge16-1.core1.lon2.he.net [72.52.92.213]
  7   123 ms   128 ms   123 ms  100ge13-2.core1.nyc4.he.net [72.52.92.166]
  8   189 ms   186 ms   186 ms  100ge8-1.core1.sjc2.he.net [184.105.81.218]
  9   198 ms   198 ms   199 ms  10ge4-4.core1.sjc1.he.net [72.52.92.117]
 10   186 ms   185 ms   210 ms  vocus.gigabitethernet2-13.core1.sjc1.he.net [64.
71.184.46]
 11   345 ms   343 ms   344 ms  bundle-153.cor02.sjc01.ca.vocus.net [49.255.255.
24]
 12   332 ms   333 ms   333 ms  BE-201.cor02.syd04.nsw.VOCUS.net.au [49.255.255.
13]
 13   337 ms   346 ms   352 ms  bundle-101.bdr01.syd11.nsw.vocus.net.au [114.31.
192.83]
 14   348 ms   346 ms   343 ms  49.255.93.14
 15   344 ms   344 ms   344 ms  po110.bs-b.sech-syd3.netarch.akamai.com [23.57.1
08.245]
 16     *        *        *     Request timed out.
 17   333 ms   331 ms   334 ms  ae121.access-a.sech-syd3.netarch.akamai.com [23.
57.108.251]
 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.

Tracert to 198.20.200.24:

Tracing route to 198.20.200.24 over a maximum of 30 hops

  1     3 ms     5 ms     2 ms  --
  2     *        *        *     Request timed out.
  3    15 ms    18 ms    19 ms  --
  4    28 ms    32 ms    42 ms  as6939.ix.dataix.ru [178.18.224.229]
  5    50 ms    51 ms    50 ms  100ge8-2.core1.ams1.he.net [184.105.65.125]
  6    57 ms    63 ms    57 ms  100ge16-1.core1.lon2.he.net [72.52.92.213]
  7   125 ms   125 ms   124 ms  100ge13-2.core1.nyc4.he.net [72.52.92.166]
  8   207 ms   199 ms   199 ms  100ge8-1.core1.sjc2.he.net [184.105.81.218]
  9   216 ms   211 ms   199 ms  100ge13-2.core1.sjc1.he.net [184.105.65.113]
 10   188 ms   189 ms   187 ms  vocus.gigabitethernet2-13.core1.sjc1.he.net [64.
71.184.46]
 11   346 ms   344 ms   350 ms  bundle-153.cor02.sjc01.ca.vocus.net [49.255.255.
24]
 12   344 ms   344 ms   343 ms  100g-0-0-0-0.cor01.sjc01.ca.vocus.net [49.255.25
5.4]
 13   344 ms   347 ms   342 ms  100g-0-0-0-0.cor01.lax01.ca.vocus.net [49.255.25
5.1]
 14   342 ms   343 ms   342 ms  bundle-200.cor01.alb01.akl.vocus.net.nz [114.31.
202.44]
 15   342 ms   343 ms   348 ms  BE-201.cor01.syd11.nsw.VOCUS.net.au [114.31.202.
53]
 16   348 ms   346 ms   347 ms  BE-1.cor02.syd04.nsw.VOCUS.net.au [114.31.192.41
]
 17   338 ms   339 ms   338 ms  bundle-101.bdr01.syd11.nsw.vocus.net.au [114.31.
192.83]
 18   347 ms   346 ms   349 ms  49.255.93.14
 19   369 ms   349 ms   346 ms  po110.bs-a.sech-syd3.netarch.akamai.com [23.57.1
08.243]
 20     *        *        *     Request timed out.
 21   346 ms   352 ms   348 ms  ae120.access-a.sech-syd3.netarch.akamai.com [23.
57.108.249]
 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.

Tracert to 198.20.200.171:

Tracing route to 198.20.200.171 over a maximum of 30 hops

  1     3 ms     2 ms     2 ms  --
  2     *        *        *     Request timed out.
  3    16 ms    16 ms    20 ms  --
  4    29 ms    27 ms    28 ms  as6939.ix.dataix.ru [178.18.224.229]
  5    50 ms    51 ms    51 ms  100ge8-2.core1.ams1.he.net [184.105.65.125]
  6    60 ms    59 ms    57 ms  100ge16-1.core1.lon2.he.net [72.52.92.213]
  7   133 ms   124 ms   125 ms  100ge13-2.core1.nyc4.he.net [72.52.92.166]
  8   186 ms   187 ms   195 ms  100ge8-1.core1.sjc2.he.net [184.105.81.218]
  9   191 ms   198 ms   198 ms  100ge13-2.core1.sjc1.he.net [184.105.65.113]
 10   186 ms   186 ms   185 ms  vocus.gigabitethernet2-13.core1.sjc1.he.net [64.
71.184.46]
 11   344 ms   344 ms   346 ms  bundle-153.cor02.sjc01.ca.vocus.net [49.255.255.
24]
 12   332 ms   336 ms   332 ms  BE-201.cor02.syd04.nsw.VOCUS.net.au [49.255.255.
13]
 13   389 ms   336 ms   337 ms  bundle-101.bdr01.syd11.nsw.vocus.net.au [114.31.
192.83]
 14   345 ms   344 ms   343 ms  49.255.93.14
 15   348 ms   344 ms   345 ms  po110.bs-a.sech-syd3.netarch.akamai.com [23.57.1
08.243]
 16     *        *        *     Request timed out.
 17   344 ms   346 ms   344 ms  ae120.access-a.sech-syd3.netarch.akamai.com [23.
57.108.249]
 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.

The_Auror

Tennessee here also being routed through Syndney now. Ping went from 80 to 280-300 after maintenance yesterday. Using local electric co. fiber internet.
https://i.imgur.com/guXrWya.jpg

DBZVelena

From what traces have been post here. PC/NA connects to Vocus.net and then it sends everybody to it Australian or sometimes first it's New Zealand version, before it goes in to the Akamai hole of doom.

Somebody forgot to differentiate between domains .net, .net.nz and .net.au

Aren't computers fun...

D0RID0RI240

Succulent Nebraska and i am at 275 to 290 ping sitting in Shornhelm. I have a 1G fiber connection, and my ping previously is always 90 to 100. I just attacked a Skeever outside the writ turn in area and ping instantly spiked to 700 plus.

I would say yall had a good run, but...ya know.

Catsmoke14

Ping 300+ now on PC NA. Was about steady 100 ms before yesterdays patch.

Geographically located in western Massachusetts, closer to Albany NY than to the hub of the universe.

Glad to see you are somewhat interested in this. You should be.

oneway123

New Jersey, also 300+ ping