SwaminoNowlino wrote: »ZOS_GinaBruno wrote: »To give you all an update, one of the routes we identified as a problem was recently fixed by the internet service provider. If you're continuing to have issues with latency, please submit a ticket with Support and include your traceroute information (you can find instructions on how to find that here).
@ZOS_GinaBruno thanks for the update. Maybe a long shot, but could you define "recently fixed" a bit better? Are we talking within the last 8 hours, the last 24 hours, or more?
lordrichter wrote: »SwaminoNowlino wrote: »ZOS_GinaBruno wrote: »To give you all an update, one of the routes we identified as a problem was recently fixed by the internet service provider. If you're continuing to have issues with latency, please submit a ticket with Support and include your traceroute information (you can find instructions on how to find that here).
@ZOS_GinaBruno thanks for the update. Maybe a long shot, but could you define "recently fixed" a bit better? Are we talking within the last 8 hours, the last 24 hours, or more?
Apparently "this afternoon", according to them on ESO Live today.
ZOS_GinaBruno wrote: »To give you all an update, one of the routes we identified as a problem was recently fixed by the internet service provider. If you're continuing to have issues with latency, please submit a ticket with Support and include your traceroute information (you can find instructions on how to find that here).
JasonSilverSpring wrote: »I am one of the lucky people who has not been impacted by these issues. I have had very stable performance throughout. But, out of curiosity, I went to this link and tried both the pathping and tracert for the NA server. Oddly, both failed to make it to 198.20.198.110. The tracert would get stuck at gar24.dlstx.ip.att.net.
I am not honestly confused why I am not having any issues if the tracert is not working.
I also tested the EU server IP and it does resolve and ironically does so in less hops than the NA server one got stuck on request timed out.
Am I missing something?
ZOS_GinaBruno I still have huge ping spikes in completely random situations, here are expamples from this week (there are no crowds around me, nobody is spamming with abilities etc):
- riding on a mount in Vvardenfell - 489 ping spike
- standing alone in my unfurnished home - 364 ping spike
- sitting on mount in Elden Root - 326 ping spike
- sitting on mount near Craglorn wayshrine - 375 ping spike
- looting treasure chest in Vvardenfell - 398 ping spike
It happens every few seconds, after ping spike latency goes to normal (80-120) but after few seconds again it goes up. Over and over. And no, it's not fault of my internet cause I have this issue only in ESO since around a week or so. Today I had such a big lag in EH 1 that I was dying all the time cause I couldn't roll dodge fast enough etc. Seriously I'm fed up with this. Should I really cancel my sub and stop playing this game until it will be fixed?
ZOS_GinaBruno I still have huge ping spikes in completely random situations, here are expamples from this week (there are no crowds around me, nobody is spamming with abilities etc):
- riding on a mount in Vvardenfell - 489 ping spike
- standing alone in my unfurnished home - 364 ping spike
- sitting on mount in Elden Root - 326 ping spike
- sitting on mount near Craglorn wayshrine - 375 ping spike
- looting treasure chest in Vvardenfell - 398 ping spike
It happens every few seconds, after ping spike latency goes to normal (80-120) but after few seconds again it goes up. Over and over. And no, it's not fault of my internet cause I have this issue only in ESO since around a week or so. Today I had such a big lag in EH 1 that I was dying all the time cause I couldn't roll dodge fast enough etc. Seriously I'm fed up with this. Should I really cancel my sub and stop playing this game until it will be fixed?
@Astrid_V Was this within the last *couple hours*. Many folks have experienced those issues this past week, but as mentioned earlier in the thread and on ESO Live the ISP repaired some routes this afternoon (so within a few hours ago). Just making sure you're not referring to an experience you have 8 hours ago for example.
As well be sure to send in a support ticket with tracert so they can see if your route is still damaged - so they can let the ISP know to fix it.
ZOS_GinaBruno wrote: »To give you all an update, one of the routes we identified as a problem was recently fixed by the internet service provider. If you're continuing to have issues with latency, please submit a ticket with Support and include your traceroute information (you can find instructions on how to find that here).
Funny, I have been playing the game just fine.
Still awful coming into their servers from North Carolina. During off-peak hours, the second the data hits AT&T's last node in Texas (the previously mentioned hop in Garland) it is subject to wild latency swings every second -- 50ms one second, 900+ the next. During peak hours, there is plenty of packet loss on Cogent's nodes, then when it hits AT&T's nodes it doubles up all the way to Garland. This produces poor latency during off-peak hours and unplayable latency during peak times.
I'm watching this all in real time using PingPlotter.
In summary, at least for me and several others in North Carolina, ESO is an unplayable mess.
I'm coming in from eastern N.C. with Suddenlink (cable). I have a friend in central N.C. with Windstream and another friend the the Charlotte area with Spectrum (I believe).
We're all running in through Cogent's stuff in DC and Atlanta and then into AT&T's nodes. The latency issues and point of breakdown is the same for all of us.
Yeah. I actually paid a year for VyprVPN. I've tried every server they have in the world. I *CAN* circumvent Cogent's stuff from a couple of them (at the cost of about 50ms added to the overall latency), but unfortunately that last hop before hitting the ESO servers is always plagued with either wild latency swings (directly reflected in the in-game latency, as you would expect) or wild latency swings *AND* horrible packet loss, depending on the time of day.
gar24.dlstx.ip.att.net is the bane of my existence (at least partially). I don't think it's avoidable, which leads me to wonder why every player isn't suffering the exact same crippling lag.
That was exactly the point of my last sentence, lordrichter. I'm a little confused as to why every user isn't having the same problem given that everyone has to run through that node.
I can pull up PingPlotter to the ESO servers at 1s intervals and watch the return time to that specific hop go from 50ms one second to 900ms the next, to 170, to 800, to 40, to 750, on so on. If this is during off-peak hours, that's the only problem I see in the route. If it's during peak hours, add to that severe packet loss starting with Cogent's crap and extending all the way through -- but increasing significantly at the gar24 hop.
Maybe the problem is actually elsewhere and that hop just isn't reporting latency correctly. Either way, something in the route is FUBAR and a lot of us just can't play as a result.
lordrichter wrote: »Once a node starts dropping packets, it isn't going to drop just it's own packets. It is going to have a chance to drop any packet that goes through it.