No... this post is about people being kicked from the servers in the middle of a trial, but NOT kicked (or logged out) of the game, ONLY their characters.
Other players are reporting issues logging into their characters as well as other issues related to the servers, in addition to bad pathing though ATT's networks.
Yes, the servers are spazzing out and its giving people problems with staying logged into certain characters or being able to log into them again.
Again, there's nothing wrong with AT&T's routers. You will stop getting reponses to ping commands after a certain router as means of protection and to not stress out the infrastructure.
Notice how my tracert stops at the same point, yet after manging to get back onto my right character again, I had no problems staying on. If there was an issue with that last hop, I wouldn't even be able to connect, especially since the address I used is seemingly the one for the login server. I actually had problems last week with connectivity to the game because Cogent was having network issues, so I definitely know what its like when there's a network issue going on outside of ZOS's realm.
Obviously, the maint they had to fix the server problems only made things worse and ZOS really needs to step in here and say something.

Mountain33r wrote: »Mountain33r wrote: »Do yourself a favor and not jump to ZOS problem, check it for yourself. Open up Command prompt. type tracert 198.20.198.110
From others who have posted on here that is the MEGASERVER IP address. Check to make sure you are not getting a bunch of timeouts after att.net
exactly what mine says, everyone might be blaming ZOS when in reality its AT&T fault
No... this post is about people being kicked from the servers in the middle of a trial, but NOT kicked (or logged out) of the game, ONLY their characters.
Other players are reporting issues logging into their characters as well as other issues related to the servers, in addition to bad pathing though ATT's networks.
Yes, the servers are spazzing out and its giving people problems with staying logged into certain characters or being able to log into them again.
Again, there's nothing wrong with AT&T's routers. You will stop getting reponses to ping commands after a certain router as means of protection and to not stress out the infrastructure.
Notice how my tracert stops at the same point, yet after manging to get back onto my right character again, I had no problems staying on. If there was an issue with that last hop, I wouldn't even be able to connect, especially since the address I used is seemingly the one for the login server. I actually had problems last week with connectivity to the game because Cogent was having network issues, so I definitely know what its like when there's a network issue going on outside of ZOS's realm.
Obviously, the maint they had to fix the server problems only made things worse and ZOS really needs to step in here and say something.
So, you're saying that tracert doesn't actually trace a route to an address, and it is a useless application that just stops somewhere in the middle of it's job because doing it's job is too hard on the system it's being used to diagnose.
OK.
If only there was some application that could be used to find a path from a starting node to an ending node, it could be used to determine the viability of that path, and it might be useful to discover weaknesses in the infrastructure.
Mountain33r wrote: »Do yourself a favor and not jump to ZOS problem, check it for yourself. Open up Command prompt. type tracert 198.20.198.110
From others who have posted on here that is the MEGASERVER IP address. Check to make sure you are not getting a bunch of timeouts after att.net
No... this post is about people being kicked from the servers in the middle of a trial, but NOT kicked (or logged out) of the game, ONLY their characters.
Other players are reporting issues logging into their characters as well as other issues related to the servers, in addition to bad pathing though ATT's networks.
Yes, the servers are spazzing out and its giving people problems with staying logged into certain characters or being able to log into them again.
Again, there's nothing wrong with AT&T's routers. You will stop getting reponses to ping commands after a certain router as means of protection and to not stress out the infrastructure.
Notice how my tracert stops at the same point, yet after manging to get back onto my right character again, I had no problems staying on. If there was an issue with that last hop, I wouldn't even be able to connect, especially since the address I used is seemingly the one for the login server. I actually had problems last week with connectivity to the game because Cogent was having network issues, so I definitely know what its like when there's a network issue going on outside of ZOS's realm.
Obviously, the maint they had to fix the server problems only made things worse and ZOS really needs to step in here and say something.
So, you're saying that tracert doesn't actually trace a route to an address, and it is a useless application that just stops somewhere in the middle of it's job because doing it's job is too hard on the system it's being used to diagnose.
OK.
If only there was some application that could be used to find a path from a starting node to an ending node, it could be used to determine the viability of that path, and it might be useful to discover weaknesses in the infrastructure.
Skinless_Jerk wrote: »Games are supposed to become better as time passes, this game just gets worse. I yes, like many others had niggles and complaints on release BUT it's just getting worse it feels

Does anyone think that any announcement they make will matter ?
The flames will just change direction
Luckily I am heading to bed. Good timing @ZOS_GinaBrunoZOS_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.
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.
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?
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 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).