This is 2017 not 2014

QuebraRegra

ZOS definitely has some server/platform issues.

Looks like they need some help:
https://jobs.zenimax.com/requisitions/view/1196

Autolycus

casparian wrote: »

Autolycus wrote: »

SirAndy wrote: »

KingRegis wrote: »

This is 2017 not 2014

I remember 2014 like it was just three years ago.
Also, loading screens were generally much shorter back then.

Putting the abysmal Client/Server implementation aside for a moment, ZOS has been continuously scaling down their Server hardware ever since launch.

It should be no surprise to anyone that this is getting worse instead of better.

Agreed. I and several of my friends all ran Traceroutes to the server IP address provided directly by ZOS support, and every test returned the same result. Our findings suggest (if not outright prove) that packets are being rejected by the endpoint, aka their server. I got their ISP involved after seeing this, and their engineers ran their own investigation and confirmed the same thing. Information is transmitted successfully all the way to the server, and for whatever reason (most likely they don't have the capacity for everything flowing in simultaneously) they reject it.

The takeaway here is that ZOS is not fixing it. A combination of too little or underperforming hardware and ZOS's iconic lack of caring about our performance despite hard evidence is likely the culprit here. No, we shouldn't be surprised. And yes, I did send all of my findings to ZOS and was ignored. The whole process was a constant, daily exchange between me and support trying to troubleshoot. The second I provided this data to them, my ticket was closed.

Autolycus, I think a number of us would appreciate it if you turned this comment into a more detailed write-up in a standalone thread. It sounds like you did some incredibly in-depth research on this which led to some striking findings, and greater publicity about it could help many of us understand our own connection issues and possibly get more attention from ZOS.

While I don't recall creating my own standalone thread for this, I've mentioned it a number of times in various threads and tagged a number of people. The original data I sent went directly to the supervisor of the support team I was working with (names intentionally omitted). The initial ticket was opened and responded to by two (iirc) of the frontline support representatives, and then was escalated to the aforementioned supervisor. Some of the information I provided is ordinarily inconclusive, the results on these traceroutes alone would not necessarily be enough to declare that the server itself can't handle the traffic, that much of it is subjective. Involvement with both my ISP and their ISP brought to light some inconsistencies that ZOS said would be escalated and investigated, but I can't personally use this information to improve the situation.

There were many, many other things in this entire process that led to my conclusion, but ultimately my personal issues were mostly resolved with the next base game update. Although several people I know started experiencing the same issues when my situation improved, there's not really anything I can do with this information to make a difference. So in a nutshell, sharing my results from just these tests, without results from various other tests on my end and the ISPs', and without testing other factors, doesn't really make any difference. Whether or not ZOS used the info and made improvements, I don't know. I can play today, I guess that's all that really matters. ZOS closed my ticket following all of this troubleshooting because they didn't have any other advice to offer, which is disappointing but understandable.

¯\_(ツ)_/¯

Elsonso

Autolycus wrote: »

SirAndy wrote: »

KingRegis wrote: »

This is 2017 not 2014

I remember 2014 like it was just three years ago.
Also, loading screens were generally much shorter back then.

Putting the abysmal Client/Server implementation aside for a moment, ZOS has been continuously scaling down their Server hardware ever since launch.

It should be no surprise to anyone that this is getting worse instead of better.

Agreed. I and several of my friends all ran Traceroutes to the server IP address provided directly by ZOS support, and every test returned the same result. Our findings suggest (if not outright prove) that packets are being rejected by the endpoint, aka their server. I got their ISP involved after seeing this, and their engineers ran their own investigation and confirmed the same thing. Information is transmitted successfully all the way to the server, and for whatever reason (most likely they don't have the capacity for everything flowing in simultaneously) they reject it.

The takeaway here is that ZOS is not fixing it. A combination of too little or underperforming hardware and ZOS's iconic lack of caring about our performance despite hard evidence is likely the culprit here. No, we shouldn't be surprised. And yes, I did send all of my findings to ZOS and was ignored. The whole process was a constant, daily exchange between me and support trying to troubleshoot. The second I provided this data to them, my ticket was closed.

This is a misinterpretation of traceroute results. You cannot use traceroute in the manner you are using it to determine what you are trying to determine.

Radinyn

Ive just got new PC, i almost dont have loading screens