ZOS FIX your SERVERS!!!

AlMcFly · December 2016

Yep, for the last three weeks I'd been playing this game solid with zero lag during PvE. It's been perfect. Fast-forward and I log in after the first (of three) maintenances that happened Monday. Holy sh*t the lag was immediately noticeable. All PvE mobs attacks were delayed. All my attacks were delayed damage. Nothing but delays in everything reacting to my button clicks.

Some people blaming this on AT&T, and people who have service through them. I call BS as I'm Comcast and am experiencing the same exact thing. The servers are just really really painful to play on, and I'm just PvE world questing. I can't imagine dungeon-running right now.

aetherial_heavenn · December 2016

The problem for me is constant disconnect to load screen then to log in screen. Or straight to log in screen.
Used tracert to 198.20.198.110 and it is timing out completely at the ggr3.dlstx.ip.att.net
node mentioned in other posts. It is doing this every disconnect.
This is unrelated to huge ping time. My ping and FPS are normal but then everything freezes except me. Then I'm at log in again. A few times it has said check your internet while my discord is functioning fine and my internet is ok at my end. This leads me to believe some of s are being routed thru a broken node: ggr3.dlstx.ip.att.net

Prior to this I until last night my time (Oceanic) I was only getting all the One Tam issues, dungeons group finder issues, huge random lag spikes (990 ping 2 fps) long loadscrens and roll backs. I have uninstalled all add-ons and reinstalled the minimum one by one. I have rolled back a windows update. Rebooted router. Flushed DNS. Cleaned ini file. Nothing helped. But at least I could play a bit. The constant booting out of the gaME IS MAKING ME A BIT CROSS. subconscious caps lock.

sorry.

SirAndy · December 2016

Still happening as of tonight ...

aetherial_heavenn · December 2016

......and it happened 60 secs after logging back in again! Just after posting this....Help someone?

pareidolon · December 2016

AlMcFly wrote: »

Yep, for the last three weeks I'd been playing this game solid with zero lag during PvE. It's been perfect. Fast-forward and I log in after the first (of three) maintenances that happened Monday. Holy sh*t the lag was immediately noticeable. All PvE mobs attacks were delayed. All my attacks were delayed damage. Nothing but delays in everything reacting to my button clicks.

Some people blaming this on AT&T, and people who have service through them. I call BS as I'm Comcast and am experiencing the same exact thing. The servers are just really really painful to play on, and I'm just PvE world questing. I can't imagine dungeon-running right now.

That's what a lot of people don't seem to realize. There's lag in populated zones that we've had for a long time, and then there's this new lag that cropped up right after the latest patch and/or maintenance and doesn't seem to go away no matter how many times we relog or what time of day we play, and routinely kicks players from the server or crashes the game. Fortunately, dungeon running seems pretty much unaffected with cities getting hit the hardest and the overworld being about 50-50.

Pallmor · December 2016

pareidolon wrote: »

AlMcFly wrote: »

Yep, for the last three weeks I'd been playing this game solid with zero lag during PvE. It's been perfect. Fast-forward and I log in after the first (of three) maintenances that happened Monday. Holy sh*t the lag was immediately noticeable. All PvE mobs attacks were delayed. All my attacks were delayed damage. Nothing but delays in everything reacting to my button clicks.

Some people blaming this on AT&T, and people who have service through them. I call BS as I'm Comcast and am experiencing the same exact thing. The servers are just really really painful to play on, and I'm just PvE world questing. I can't imagine dungeon-running right now.

That's what a lot of people don't seem to realize. There's lag in populated zones that we've had for a long time, and then there's this new lag that cropped up right after the latest patch and/or maintenance and doesn't seem to go away no matter how many times we relog or what time of day we play, and routinely kicks players from the server or crashes the game. Fortunately, dungeon running seems pretty much unaffected with cities getting hit the hardest and the overworld being about 50-50.

Yep, whatever this problem is, it has something to do with the patch, not AT&T.

Soleya · December 2016

pareidolon wrote: »

AlMcFly wrote: »

Yep, for the last three weeks I'd been playing this game solid with zero lag during PvE. It's been perfect. Fast-forward and I log in after the first (of three) maintenances that happened Monday. Holy sh*t the lag was immediately noticeable. All PvE mobs attacks were delayed. All my attacks were delayed damage. Nothing but delays in everything reacting to my button clicks.

Some people blaming this on AT&T, and people who have service through them. I call BS as I'm Comcast and am experiencing the same exact thing. The servers are just really really painful to play on, and I'm just PvE world questing. I can't imagine dungeon-running right now.

That's what a lot of people don't seem to realize. There's lag in populated zones that we've had for a long time, and then there's this new lag that cropped up right after the latest patch and/or maintenance and doesn't seem to go away no matter how many times we relog or what time of day we play, and routinely kicks players from the server or crashes the game. Fortunately, dungeon running seems pretty much unaffected with cities getting hit the hardest and the overworld being about 50-50.

I can attest that Vet Maestrom was unplayable last night, and since that is a solo instance there is no population there with me.

gard · December 2016

ZOS_GinaBruno wrote: »

bottleofsyrup wrote: »

ZOS_GinaBruno wrote: »

We're going to be bringing PC NA offline for maintenance in about a half hour to address the issues reported here with high latency and ping. Should be approximately 4 hours to complete.

Hope I don't sound rude, but have they found the cause this time?

Yes. The maintenance yesterday was for general performance issues and disconnects; today is specifically for the high ping, which we recently resolved internally (otherwise we certainly would have done it all at the same time yesterday).

@ZOS_GinaBruno
Will there be another maintenance to address the high ping that people have been and still are experiencing?

P3ZZL3 · December 2016

PC-EU Unplayable.

2 Bounces and kick outs advising me that I need an internet connection to play.

Ping rate averaging 770 - even though I normally get 80-100

London, EU, PC.

Oh, and I'm posting, so I do have an internet connection

chrissouza7ub17_ESO · December 2016

StonerMk2 wrote: »

mrs_gibbs wrote: »

I'm kind of sad there won't be anymore maintenance until the new year. No more fixes until then either.

Im not at all surprised, its getting close to the holidays, barring any major issues, they are people with families as well. They deserve to be with their families.

Like Chester Cheetah from Cheese Puffs commercial says: "No they deserve to be fired"

Kirsch9 · March 2017

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\User>tracert 198.20.198.110

Tracing route to 198.20.198.110 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home
2 7 ms 4 ms 6 ms lo0-100.NRFLVA-VFTTP-306.verizon-gni.net [96.238
.95.1]
3 8 ms 7 ms 7 ms B3306.NRFLVA-LCR-22.verizon-gni.net [100.41.219.
8]
4 * * * Request timed out.
5 20 ms 16 ms 20 ms 0.ae4.BR1.IAD8.ALTER.NET [140.222.227.9]
6 22 ms 19 ms 19 ms 192.205.36.137
7 61 ms 59 ms 59 ms cr82.wshdc.ip.att.net [12.122.135.182]
8 57 ms 55 ms 57 ms cr2.wswdc.ip.att.net [12.122.134.94]
9 59 ms 56 ms 55 ms cr1.wswdc.ip.att.net [12.122.2.29]
10 60 ms 64 ms 63 ms cr2.dlstx.ip.att.net [12.122.2.110]
11 86 ms 56 ms 66 ms ggr3.dlstx.ip.att.net [12.122.138.25]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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.

Trace complete.

WORKING AS INTENDED I SUPPOSE?

Sovaso · March 2017

Nebthet78 wrote: »

Seriously!! Your servers are getting so bad now, they are causing whole raiding parties to crash back to character select screen in the middle of Trials! It's unacceptable!

It will never be repaired.

qsnoopyjr · March 2017

To be brutally honest,

When games get so many players, what usually happens is they hope the players leave, aka get bored.

This is what happened with Pokemon GO, 'we'll just wait till all the bandwagon players leave and servers should be okay'.
Game is now dead.

Games need to start thinking about meeting and exceeding demand. You have a lot of players, start using that extra revenue and make sustainable servers for the extra players. Stop cutting costs.

I swear every business, wants to cut costs.
"we'll just keep servers as is, and wait for 2 more years before we decide to do something big, we have to cut costs!"
"making servers better? more capacity??? Thats not cutting costs!"

Cronopoly · March 2017

Kirsch9 wrote: »

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\User>tracert 198.20.198.110

Tracing route to 198.20.198.110 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home
2 7 ms 4 ms 6 ms lo0-100.NRFLVA-VFTTP-306.verizon-gni.net [96.238
.95.1]
3 8 ms 7 ms 7 ms B3306.NRFLVA-LCR-22.verizon-gni.net [100.41.219.
8]
4 * * * Request timed out.
5 20 ms 16 ms 20 ms 0.ae4.BR1.IAD8.ALTER.NET [140.222.227.9]
6 22 ms 19 ms 19 ms 192.205.36.137
7 61 ms 59 ms 59 ms cr82.wshdc.ip.att.net [12.122.135.182]
8 57 ms 55 ms 57 ms cr2.wswdc.ip.att.net [12.122.134.94]
9 59 ms 56 ms 55 ms cr1.wswdc.ip.att.net [12.122.2.29]
10 60 ms 64 ms 63 ms cr2.dlstx.ip.att.net [12.122.2.110]
11 86 ms 56 ms 66 ms ggr3.dlstx.ip.att.net [12.122.138.25]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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.

Trace complete.

WORKING AS INTENDED I SUPPOSE?

Sorry but as a 22 year IT professional Tracerouts are not the best item to use for tracking performance. They are good for checking which route for the most part unless you see a hop that has abysmal mn >200 for example.

That you get 16-60ms avg on the first 11 hops of the ATT journey is normal. That the rest time out is normal as well. Many Internet Routers are configured to NOT allow ICMP traffic responses for security reasons to rpevent some 12 year old from using their infrastructure DDoS attack or potentially hacking the Router itself.

Looking at it your Tracert is normal.

At ZOS there are Edge Routers (Cisco Etc), Firewalls (NAT tables), Database servers, Large Terabyte Storage frames (EMC types), DNS Servers, DMZ Zones, Fiber channels etc...

It really is too shallow for anyone to say "ZOS servers", as the effected bottleneck could be anything in the infrastructure. I can tell you what "the problem" is in my experience. People.

ZOS_Bill · March 2017

We've closed this thread as it is a necro from December. Please do not revive old threads as any PC technical issues should be posted in PC Technical Support.