ZonasArch wrote: »

As the title suggests, I have a seriously inconvenient issue that came up after the update. Used to play on NA for years, latency around 200-250, living in brazil and brazil being far away from NA. On EU I play a little too and latency is usually between 270-310.

After update, EU remains as it was, no spikes or anything, but on NA, my main server, it's game breaking unstable. I can't place skills because of spikes, i can't bar swap effectively and i even have issues using menus because actions take variable amount of times to go through when spikes are happening.

These spikes make my latency meter in-game go to upwards of 600 from time to time, and by that i mean every few seconds at best. Been having issues even with Delve bosses, when my main build can even solo WB.

Before the mandatory "it's your connection" shows up, read again here: My connection is perfectly fine since my connection to EU server is still exactly perfect as it was before. if my connection was an issue, i wouldn't be able to enjoy EU as before. My game installation is also fine, since, again, the EU server works fine. Same with addons. I use the same addons for both servers, and issue still persisted without literally ANY addons running too.

Tested connection with tracert to the suggested ip on the "help" menu, and EU was, again, perfectly stable on all connections, but NA had various ping fluctuations, and also a huge amount of servers not ever returning any result because i got timed out. Dunno if for excessive latency or just unresponsive servers in general. While doing that, I also pingd google to make sure it wasn't another kind of issue, and it returned, yet again, a really good result.

This looks clearly as a routing issue from South America to North America, even though i have no clue what nodes my connection goes through to get to NA. This is truly game breaking and frustrating, since i've been playing ESO for years and all my best friends are there and i can't join them after the update.

It is good that you play ESO on both the EU and NA megaservers, respectively. So you can compare their relative performance.

From your report, yes, there is a "connection issue" -- between your computer and the NA megaserver.

There is probably not an issue with your LAN connection to the ISP network which connects to the Internet backbone. It seems to be a performance issue with one or more routers on the Western Hemisphere Internet, per se, to which your ISP's network sends packet into, and receives packets from, the Internet. (In Brazil, I suppose that your Internet Service Provider is a government agency, whether it matters, telecommunications corporations are no better or worse.)

The utility tracert.exe should be able to trace the entire route from your own connection to your ISP, through the ISP network, and through the Internet to the megaserver. In practice, there might be a limit to the number of "hops" that it can investigate, although I've never found a route so long that the trace fails to reach the destination server for that reason. If it encounters a router through which it cannot continue because of too many time-outs, then that router is probably not operating. The packets just disappear. In that situation, you need advice and assistance that I hesitate to offer. Perhaps ZOS and/or your ISP can do so.

Note also that packets do not necessarily follow the same route when they are sent by the megaserver to your computer as the route followed by the ones which your computer sends to the megaserver. So, even if the route from your computer to the megaserver is clear, one or more routers on the route from the megaserver to your computer might have a problem.

Given the recurring latency issues that I am also finding with my own connection to the megaserver from my computer in Florida (USA), it seems that I must investigate them once again. In my experience, about once each year some router on the Internet between my computer and the megaserver has a serious problem. We might prefer to think that an ISP routinely checks for problems. But in my experience, network hardware personnel prefer to assume that everything is working well until someone convinces them that it isn't.

By the way, as you may know, you can store the tracert.exe output in text file by redirecting it ( > pathname\filename).