nafensoriel wrote: »Can you confirm it happened exclusively after the servers came up or rather(and more likely) during the time the server was down doing maint?
The former is the server.
The latter is not.
It doesn't matter what correlative evidence you have suggesting the server is to blame because suddenly a thing happened. Your issue could easily be explained by someone along your route to the sever spilling a cup of coffee on a router during ESOs maint cycle.
If EVERYONE isn't having the issue then it is most likely NOT the servers fault but rather some part of the ISP chain between you and that server. Unfortunately, it's usually not a router your ISP can control itself so frankly, you are SOL till whoever broke something fixes it.
All zos can do is ask nicely and get told to *** off by the far larger and more powerful T1/2/3s.
Apparently as others have discovered, ESO use of Akami is for some reason being routed through Sydney, Australia, hence the insanely gamebreaking ping.
Apparently as others have discovered, ESO use of Akami is for some reason being routed through Sydney, Australia, hence the insanely gamebreaking ping.
Alinhbo_Tyaka wrote: »Apparently as others have discovered, ESO use of Akami is for some reason being routed through Sydney, Australia, hence the insanely gamebreaking ping.
Knowing ZOS this is their way of balancing our Aussie friends horrendous ping time with those of us resident in the US. You know don't fix the problem just take out the nerf bat and nerf everything else.
Apparently as others have discovered, ESO use of Akami is for some reason being routed through Sydney, Australia, hence the insanely gamebreaking ping.
Apparently as others have discovered, ESO use of Akami is for some reason being routed through Sydney, Australia, hence the insanely gamebreaking ping.
I've been told repeatedly even at these levels of ping, which us Aussies have enjoyed for a long time, it was a "l2p issue", and all we needed to do was "git gud", so, I must admit, my sympathy is mixed with a little schadenfreude.
I think perhaps this may be the work of hackers maybe. It's not outside of possibility
Apparently as others have discovered, ESO use of Akami is for some reason being routed through Sydney, Australia, hence the insanely gamebreaking ping.
I've been told repeatedly even at these levels of ping, which us Aussies have enjoyed for a long time, it was a "l2p issue", and all we needed to do was "git gud", so, I must admit, my sympathy is mixed with a little schadenfreude.
apologies if i came off as tone deaf
nafensoriel wrote: »Can you confirm it happened exclusively after the servers came up or rather(and more likely) during the time the server was down doing maint?
The former is the server.
The latter is not.
It doesn't matter what correlative evidence you have suggesting the server is to blame because suddenly a thing happened. Your issue could easily be explained by someone along your route to the sever spilling a cup of coffee on a router during ESOs maint cycle.
If EVERYONE isn't having the issue then it is most likely NOT the servers fault but rather some part of the ISP chain between you and that server. Unfortunately, it's usually not a router your ISP can control itself so frankly, you are SOL till whoever broke something fixes it.
All zos can do is ask nicely and get told to *** off by the far larger and more powerful T1/2/3s.
Since we can't check our game latency when servers are down and for over a year through 3:00 am last night my latency ran consistently around 80 ms, I can say this happened exclusively after the servers came up this morning.
Whether or not someone spilled coffee on a router during the same time servers were down for maintenance is immaterial. A connectivity issue for a significant number of people has occurred simultaneously after a planned patch maintenance. I don't really care whose fault it is. But a simple acknowledgement of something that negatively affects THEIR product and our experience of it is a basic matter of customer care and courtesy.
nafensoriel wrote: »nafensoriel wrote: »Can you confirm it happened exclusively after the servers came up or rather(and more likely) during the time the server was down doing maint?
The former is the server.
The latter is not.
It doesn't matter what correlative evidence you have suggesting the server is to blame because suddenly a thing happened. Your issue could easily be explained by someone along your route to the sever spilling a cup of coffee on a router during ESOs maint cycle.
If EVERYONE isn't having the issue then it is most likely NOT the servers fault but rather some part of the ISP chain between you and that server. Unfortunately, it's usually not a router your ISP can control itself so frankly, you are SOL till whoever broke something fixes it.
All zos can do is ask nicely and get told to *** off by the far larger and more powerful T1/2/3s.
Since we can't check our game latency when servers are down and for over a year through 3:00 am last night my latency ran consistently around 80 ms, I can say this happened exclusively after the servers came up this morning.
Whether or not someone spilled coffee on a router during the same time servers were down for maintenance is immaterial. A connectivity issue for a significant number of people has occurred simultaneously after a planned patch maintenance. I don't really care whose fault it is. But a simple acknowledgement of something that negatively affects THEIR product and our experience of it is a basic matter of customer care and courtesy.
That is precisely my point.
The servers cannot cause this issue intermittently. The servers didn't do a darn thing. Maint didn't do a darn thing. Nothing whatsoever in ZOSs power did anything. This is squarely an "isp" issue.
The latest find with Akami actually point-blank tells you ESO servers and ZOS have nothing what-so-ever to do with the problem. All ZOS can do is politely ask Akami to correct the routing error. All Akami will do is laugh at the email/phone call and go back to doing whatever they want.
They won't say squat because saying anything will increase demands for ZOS to "fix it" when they have ZERO POWER TO DO SO.
There was a time when my business was routed through Chicago to get to California. My office is not on the eastern side of the continent. It took my provider four months to get an answer and fix from the T2.
nafensoriel wrote: »nafensoriel wrote: »Can you confirm it happened exclusively after the servers came up or rather(and more likely) during the time the server was down doing maint?
The former is the server.
The latter is not.
It doesn't matter what correlative evidence you have suggesting the server is to blame because suddenly a thing happened. Your issue could easily be explained by someone along your route to the sever spilling a cup of coffee on a router during ESOs maint cycle.
If EVERYONE isn't having the issue then it is most likely NOT the servers fault but rather some part of the ISP chain between you and that server. Unfortunately, it's usually not a router your ISP can control itself so frankly, you are SOL till whoever broke something fixes it.
All zos can do is ask nicely and get told to *** off by the far larger and more powerful T1/2/3s.
Since we can't check our game latency when servers are down and for over a year through 3:00 am last night my latency ran consistently around 80 ms, I can say this happened exclusively after the servers came up this morning.
Whether or not someone spilled coffee on a router during the same time servers were down for maintenance is immaterial. A connectivity issue for a significant number of people has occurred simultaneously after a planned patch maintenance. I don't really care whose fault it is. But a simple acknowledgement of something that negatively affects THEIR product and our experience of it is a basic matter of customer care and courtesy.
That is precisely my point.
The servers cannot cause this issue intermittently. The servers didn't do a darn thing. Maint didn't do a darn thing. Nothing whatsoever in ZOSs power did anything. This is squarely an "isp" issue.
The latest find with Akami actually point-blank tells you ESO servers and ZOS have nothing what-so-ever to do with the problem. All ZOS can do is politely ask Akami to correct the routing error. All Akami will do is laugh at the email/phone call and go back to doing whatever they want.
They won't say squat because saying anything will increase demands for ZOS to "fix it" when they have ZERO POWER TO DO SO.
There was a time when my business was routed through Chicago to get to California. My office is not on the eastern side of the continent. It took my provider four months to get an answer and fix from the T2.
24 hours later. Ping still sitting at 300+ with spikes to 700+ and still not a peep about the issue from ZOS.
January1171 wrote: »24 hours later. Ping still sitting at 300+ with spikes to 700+ and still not a peep about the issue from ZOS.
http://forums.elderscrollsonline.com/en/discussion/comment/6508704#Comment_650870 4 They are looking into it, just haven't announced a resolution
nafensoriel wrote: »Can you confirm it happened exclusively after the servers came up or rather(and more likely) during the time the server was down doing maint?
The former is the server.
The latter is not.
It doesn't matter what correlative evidence you have suggesting the server is to blame because suddenly a thing happened. Your issue could easily be explained by someone along your route to the sever spilling a cup of coffee on a router during ESOs maint cycle.
If EVERYONE isn't having the issue then it is most likely NOT the servers fault but rather some part of the ISP chain between you and that server. Unfortunately, it's usually not a router your ISP can control itself so frankly, you are SOL till whoever broke something fixes it.
All zos can do is ask nicely and get told to *** off by the far larger and more powerful T1/2/3s.