I am having the same issue.
My tracert looks about the same as the rest of you guys.
Once it hits that Att network it drops.

Lirkin wrote: »

Where are ZoS servers located?

i have been asking that question for a long time and the only people who answer that question are people who simply do not know what thier saying,
the people who "Should" answer that question are zenimax employees.

Logged in just now. And i haven't recieved a crippling timeout yet so far. usually would have kicked in by now. Pingplotter reveals there is still issues, But it's not as bad as before. before was unplayable. Now it's just irritating. lol.

Still about 8 to 10% packetloss now, which is better then the timeouts and 25% rate i was getting

So obviously someone is looking into something. or it wouldn't have improved slightly.

Last night for me at least was getting the ping spikes to over 1000 ect like I was for the last week then I got kicked logged in again and a steady 140 ping all night no spikes (been getting spikes since morrowind)

I'm having the same problem, though I've been having it since the launch of Morrowind (when I returned to the game). Latency sits around 117 normally but spikes up erratically at all hours. Sometimes it will spike to 350, other times 999+. The problem is pretty clear when using monitoring software. In my case, PingPlotter set to 1s intervals.

The gar24.dlstx.ip.att.net hop (12.122.100.77) is FUBAR. The response time fluctuates wildly every second, from 50ish to 500 or so. Sometimes packet loss is present, other times not. Here's the rub, though. I've tried every VPN location available from VyprVPN (which I paid $80 for). No matter what angle you come in from, it always goes through here to get to ESO's NA server.

AT&T's node is bjorked, and I expect that the only way to see it fixed is for Zenimax to deal with them directly. I could be wrong here, but until something is done ESO is either unplayable or problematic at all times.

I do hope that whatever fix they implemented isn't the extent of their solution. I haven't seen the update to which you are referring, so I can only hope that that is not exactly what they said. In my experience, once a problem is declared "fixed", no more attention will ever be paid to it.

That said, my connection to the game hasn't changed at all. Still awful, and wild latency swings at gar24.dlstx.ip.att.net. That hop was hitting 900ms periodically earlier today. I don't know who is to blame, as it could be Zenimax, AT&T, perhaps Cogent, or someone else. The end result is the same though -- awful game lag.

Like many others, I've gone ahead and cancelled my sub until such a time that things just work better than they do right now.

I'm in North Carolina, too, as are two friends of mine who play. Same issue for everyone. It's definitely the gar24.dlstx.ip.att.net hop. I can watch it's latency swing wildly on PingPlotter. One second it's 49ms, the next it's 850ms, then it's anything in between. This is often accompanied by packet loss when network loads are high, but even when it isn't this is obviously contributing to the lag spikes in the game which make it difficult or even impossible to play.

The problem here is that this is AT&T's data infrastructure (which sucks) coming off of Cogent's (which sucks almost as much). I have to assume that the problem lies squarely with AT&T (who most likely don't care in the slightest), leaving Zenimax in the position of hoping that they are a big enough company to convince AT&T to fix their stuff. If not, I don't see it ever being fixed. That's why I cancelled my sub. I'll hop on every once in a while and check it out without a sub to see if it ever gets better.

Lag in this game has been notoriously bad since the beginning. I wonder if this is the cause? It seems like either AT&T has to fix this, or Zenimax has to find a way to avoid that route (if it's possible). What are the chances that either of those two things will ever actually happen?

MrLuchenkov wrote: »

Pretty decent, actually, provided that Zenimax considers it a problem worth resolving. So far, they have at least publicly acknowledged it a day ago via Bethesda Support on Twitter.

The main issue is making sure they do something about it and don't leave it to the generally incompetent 1st-level tech support to tell us we need to contact our ISP or remove add-ons and what not.

Thats what drove me nuts. I spelled out everything in an email, and they were telling me to check my add ons etc. i wrote back and said do you guys check the forums, the issue is not me. I attached a game consultant report and it clearly shows the route is screwed, not out of my isp. heh. drove me bonkers. i just stopped contacting em. posting here instead.

i was away all weekend, issue still present? i'm about to log in.

MrLuchenkov wrote: »

Pretty decent, actually, provided that Zenimax considers it a problem worth resolving. So far, they have at least publicly acknowledged it a day ago via Bethesda Support on Twitter.

The main issue is making sure they do something about it and don't leave it to the generally incompetent 1st-level tech support to tell us we need to contact our ISP or remove add-ons and what not.

Given that they have made it a point to put up a red notification on the forum to let us know that they are, in fact, looking into it, I'm going to be optimistic and agree with you here. Since then, though, they have put up another banner declaring the problem fixed, then taken that down entirely. I won't have a chance to test the route from home until I get there in a few more hours, but I'll make it a point to post an update from my perspective when I do.

Yep. I just logged in to see if I could play -- I can't. It's awful.

Running a trace to their servers with PingPlotter (so I can monitor it in 1s intervals), I can see that it is indeed worse than usual.

As soon as the trace hits Cogent's crap in DC (154.54.30.53) the packet loss starts. This continues all the way through Cogent's infrastructure (DC to two hops in Atlanta) and then into AT&T's stuff (Atlanta to two servers in Dallas) where it gets much, much worse. The last hop in Texas (Garland) before the ESO servers is at around 20% packet loss and the usual wild latency swings, changing every second from 60ms up to over 900ms (seemingly randomly).

The entire path is FUBAR, unfortunately, and everyone stuck on it is just screwed right now. It's been like this for me since Morrowind launched, though, and I've noticed no change at any point. Playable with problems during non-peak hours and completely unplayable during peak hours (like right now).

It looks like a fix would require the coordination of Cogent, AT&T, and Zenimax. As such, my faith that the game is ever going to work again for anyone stuck on this path is exhausted. Even if Zenimax did desperately want to get the problem fixed, I doubt they'd stand a chance to do so. It's like when you call your ISP to report a problem -- times 1,000,000.

As I sit watching PingPlotter right now, the packet loss starts the second it hits AT&T -- at 192.205.36.237. It's at a constant 9-15% packet loss here which carries through all the way to Garland (since the final server doesn't respond). It then has to go through Atlanta to Dallas and then to that final hop (which does show the wild latency spikes every second).

cr4mf157 wrote: »

As an update, I sent another ticket in last night to inform them that the route to the servers from here is still awful. Unfortunately, they refuse to receive PingPlotter data and traceroute output doesn't clearly show the problem (given it's root in packet loss and wild latency swings at the last hop).

SO, we're currently at the obligatory point where they spend days telling me that it's a port issue (which it isn't), an antivirus issue (which it absolutely isn't), and then that my ISP sucks. Given that I can easily observe the entire route myself (and have spent about 100 hours with my ISP in direct contact with their engineers), it's clearly isn't that, either.

I'm more convinced than ever that they simply can't fix this routing problem and that ESO is a lost cause.

Yes, that's my biggest fear too. The same happened to a lot of us on ArcheAge and the company completly refused to even acknowledge the issue, even though it was widespread and affected over 27 different ISPs (I asked ppl to give me their info and tracert / pingplotter to make a big file), across Mexico, Canada and the USA.

It's not our ISP. It's not our settings, an antivirus or my PC. It's the hop we go through to reach your servers, Zenimax.

Could anyone please help diagnose similar issues on the EU Cluster?
I'm playing from South Africa, use a VPN (BattlePing) and have been trying out various routes with brief periods of success. What I don't understand is that routing via US East Coast as a test grants a more stable ping, while routing straight to Germany I get a better ping (230ms on average) but with more frequent spikes.

If I use MTR/PingPlotter which addresses should I be tracing (PC EU)?
Thanks in advance.

crowbartool wrote: »

I have EXACTLY the same problem from the same geographical location (Western Canada - Langley BC) using a fibre connection from Telus. The issue disappears ONLY when running through a US VPN. This issue has been ongoing for the good part of a week now.

I am in the same city with the exact same problem on Shaw right now. Was wondering if it was maybe saturation off the Shaw network in my neighborhood. Apparently not.

With that, as said above, there are a lot of edge devices that do not respond to ping attempts. It's quite common when you hit enterprise and ISP level stuff. A lot of things just deny the request but they should also pass things along.

I'd be remiss if I didn't add to my previous statement about Zenimax not fixing the problem and it being time to give up. I got one last response from customer service before they marked my ticket about all of this as "solved" (which it obviously is not, but the troubleshooting has obviously run its course):

"Upon researching this issue further our developers are currently investigating reports of some players encountering higher than normal latency issues due to the connect path they are using. As this is something our developers will be working with ISPs to resolve I'm unfortunately unable to provide a timeframe as to when exactly this will be permanently resolved however rest assured that we will look in to this further."

I suggested that put the "We know it sucks and we're trying to fix it" banner back up so at least people can cling to some home that things will eventually work.