Maintenance for the week of May 18:
• NA megaservers for maintenance – May 18, 4:00AM EDT (8:00 UTC) - 9:00AM EDT (13:00 UTC)
• EU megaservers for maintenance – May 18, 8:00 UTC (4:00AM EDT) - 13:00 UTC (9:00AM EDT)
• NA megaservers for maintenance – May 18, 4:00AM EDT (8:00 UTC) - 9:00AM EDT (13:00 UTC)
• EU megaservers for maintenance – May 18, 8:00 UTC (4:00AM EDT) - 13:00 UTC (9:00AM EDT)
Crippling Lag (still)
cr4mf157
✭✭✭
In spite of my better judgment and in spite of the crippling lag coming from AT&T's nodes all the way into the ESO servers, I optimistically did one more month of ESO+. As if the world itself was trying to tell me something, the lag instantly got just a bit worse. Zenimax -- can you fix this routing issue or not? 500-999+ latency spikes every few seconds aren't fun and make the game playable. I need to know whether I should go ahead and abandon this game entirely.
As you can see, packet loss starts on the very first AT&T hop (192.205.36.237) then continues through to the server. (Well, the hop just before the server anyway, since they have set the server itself to refuse to respond to ICMP.) Then, the last hop before the ESO server also has wild latency fluctuations. It changes every second from as low as 50ms (where it should be) to 800+.
I've attached an image of the connection at its very best. It's a whole pile of bad.
*** Edit to fix image URL.
Edited by cr4mf157 on July 18, 2017 1:07AM As you can see, packet loss starts on the very first AT&T hop (192.205.36.237) then continues through to the server. (Well, the hop just before the server anyway, since they have set the server itself to refuse to respond to ICMP.) Then, the last hop before the ESO server also has wild latency fluctuations. It changes every second from as low as 50ms (where it should be) to 800+.
I've attached an image of the connection at its very best. It's a whole pile of bad.
*** Edit to fix image URL.
2
-
Mayanpup✭✭✭I also face the same lag/fps issues as have happened in the past several weeks (try doing a dolem at 1-3 FPS). Usually if it lasts for over a minute I quit and come back later.
I feel this is more an ISP issue than game content issue. Maybe when contract renewal with the ISP's comes up changes and remedies for the current issues can be more strictly defined.1 -
baltic1284✭✭✭✭The game has always had issues with latency and ping spikes since there release and they haven't done much to fix the issue instead of biting the bullet and better equipment and material and employees they just shelve it and hope players keep giving theme money. At least eliminate the game itself and there bad servers out of the equation and such and work harder to make the game experience fun instead of bad. I would do a check on your end so that they cant have an excuse as to why.1 -
Ardaghion✭✭✭✭In spite of my better judgment and in spite of the crippling lag coming from AT&T's nodes all the way into the ESO servers, I optimistically did one more month of ESO+. As if the world itself was trying to tell me something, the lag instantly got just a bit worse. Zenimax -- can you fix this routing issue or not? 500-999+ latency spikes every few seconds aren't fun and make the game playable. I need to know whether I should go ahead and abandon this game entirely.
As you can see, packet loss starts on the very first AT&T hop (192.205.36.237) then continues through to the server. (Well, the hop just before the server anyway, since they have set the server itself to refuse to respond to ICMP.) Then, the last hop before the ESO server also has wild latency fluctuations. It changes every second from as low as 50ms (where it should be) to 800+.
I've attached an image of the connection at its very best. It's a whole pile of bad.
That's weird, I don't see an image showing packet loss, I see an image that says the name of the file.0 -
Tandor✭✭✭✭✭
✭✭✭✭✭I can't access the image, but you appear to be saying that the problem is before the game servers, so why are you asking ZOS to fix it rather than asking your ISP to sort out its routing?0 -
cr4mf157✭✭✭@baltic1284
Yeah. I've checked every possible avenue. The problem is most definitely the AT&T nodes across which a lot of our data has to go to reach their servers. To a lesser extent, the Cogent nodes before that are also mildly problematic. I don't know if it's also their servers themselves as they have made sure we have no way of knowing. They won't respond to ICMP.
@Tandor
I'm pressing Zenimax on it because I have dealt directly with my ISP for many, many hours. I've discussed things directly with their engineers, and have even gone so far as to tour their server facilities. It's not their choice in routing, because everyone goes through at least that last hop (gar24.dlstx.ip.att.net) which is problematic. You can verify this by using any VPN. No matter what, everyone goes through there. That suggests to me that it's likely Zenimax's hosting -- that is, the only way it will get fixed is if Zenimax puts some pressure on AT&T. They claim to have fixed routing issues before, even as recently as last week.
Here's the PingPlotter graphic to see what I mean again. I can see the first one, but it seems like nobody else can:
0