AngryChelse wrote: »I just completed the Trial. The network situation is much better than it was a few days ago!
What is puzzling is that I can't figure out why this problem was resolved. I did not change any network settings, nor did I reinstall.
It has been a strange few days
StihlReign wrote: »
Packet loss and high latency can be traced to the anti-DDoS servers all data is routed to before it gets to the ESO servers. This has been well documented with tracerts for years.
https://forums.elderscrollsonline.com/en/discussion/436992/high-latency-at-akamai-com/p1
Good ole Akamai anti-ddos service at it again?
Easy to test.
Windows key + R
Type cmd or cmd.exe in the box.
Type: tracert 198.20.200.1 in the command window and press Enter. Akamai filtering confirmed.
You can also run ping 198.20.200.1
Tracing route to 198.20.200.1 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms xxx.xxx.xxx.xxx 2 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx 3 12 ms 16 ms 2 ms xxx.xxx.xxx.xxx 4 3 ms 2 ms 3 ms 82.113.32.226 5 2 ms 2 ms 2 ms xe-4-0-0.prg11.ip4.tinet.net [213.200.74.93] 6 2 ms 2 ms 2 ms ip4.gtt.net [77.67.120.54] 7 7 ms 7 ms 7 ms ae23-xcr1.vie.cw.net [195.2.25.254] 8 8 ms 8 ms 8 ms 62.208.246.59 9 7 ms 8 ms 8 ms a2-21-119-97.deploy.static.akamaitechnologies.com [2.21.119.97] 10 * * * Request timed out. 11 147 ms 147 ms 143 ms 198.20.200.1For comparison EU server 159.100.232.124
Tracing route to 159.100.232.124 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms xxx.xxx.xxx.xxx 2 3 ms 2 ms 3 ms xxx.xxx.xxx.xxx 3 3 ms 2 ms 2 ms xxx.xxx.xxx.xxx 4 3 ms 3 ms 3 ms 82.113.32.226 5 5 ms 2 ms 4 ms xe-4-0-0.prg11.ip4.tinet.net [213.200.74.93] 6 2 ms 2 ms 2 ms ip4.gtt.net [77.67.120.54] 7 7 ms 7 ms 8 ms ae23-xcr1.vie.cw.net [195.2.25.254] 8 8 ms 8 ms 8 ms 62.208.246.59 9 8 ms 8 ms 8 ms a2-21-119-147.deploy.static.akamaitechnologies.com [2.21.119.147] 10 17 ms 20 ms 19 ms a184-26-104-158.deploy.static.akamaitechnologies.com [184.26.104.158] 11 20 ms 19 ms 20 ms 195.122.154.2 12 28 ms 26 ms 26 ms 159.100.224.33 13 15 ms 19 ms 19 ms 159.100.232.124
Windows key + R
Type cmd or cmd.exe in the box.
Type: tracert 198.20.200.1 in the command window and press Enter. Akamai filtering confirmed.
You can also run ping 198.20.200.1
May I ask what I should see? I got a timeout after Akamai.
It's a good thing that ZOS is a customer of akamai because they provide top notch ddos mitigation solutions but it doesn't mean there's any ddos mitigations currently active.
[snip]
Here is my tracert:
<snip>
14 7 ms 6 ms 6 ms 198.20.200.1
So yeah the game delay..ugh.. I don't use addons either. Not worried about the time outs, it happens and some hops don't reply.
Here is my tracert:
<snip>
14 7 ms 6 ms 6 ms 198.20.200.1
So yeah the game delay..ugh.. I don't use addons either. Not worried about the time outs, it happens and some hops don't reply.
This is excellent information that could help ZOS narrow down the scope of the issue by seeing the route you take to the NA server.
Your latency to the NA server is so low! I am envious. However, traceroute isn't great at showing intermittent packet loss. I suggest pinging the server continuously with: ping -t 198.20.200.1
The benefit of pinging continuously is one can switch to the shell window to see if their in-game issues correlate with packet loss. That was usually the case for me on Thursday. On Friday I had almost no packet loss and absolutely no issues while grinding a trial and doing misc overland/trading/banking tasks in between from 7 PM to 1 AM EDT.
A continuous ping can be interrupted with a ctrl-c, which will display stats.
I'm honestly surprised that my connection to the NA server is over 11 hops and to the EU (which is in a neighboring state) over 13.
Anyway, I've been observing that timeout on Akamai for about 2-3 years, when I was solving my internet over two ISPs and almost 10 network devices due to ESO (Crashes, disconnects, booting from server etc. Luckily after ISP change this was solved by replacing the second ISP's router with a gateway on my fiber connection [A lot of arguing with technicians about having two routers in a row when I'm still not allowed to touch their main one is nonsense lol, I hate not having control over the settings, so I got a gateway], and I also still have two more routers in backup for possible replacement).
According to a geoip lookup, you're connecting to the akamai router in Austria. You don't see more hops because between them and ZOS you're within Akamai's network. There is likely several hops between Austria and Texas.
Of course one should expect latency between Austria and Maryland Texas. The geo ip info for 198.20.200.1, but a ZOS help article says the NA server is hosted in Texas.
Yes the sever is in Texas. I could throw a rock at the data center and hit it since I live in Dallas. This is why I have to wonder about the server being an issue. My connection is flawless unless my provider or the server is having issues. No provider issues but I will run the ping today when I play and see what I get.
I personally think a client issue is least likely, but it's not impossible.
Wildberryjack wrote: »
Wildberryjack wrote: »
Here's the thing, this all started after the May 7 update and that mess with stuff carrying over from PTS to live. I don't believe in coincidences. It's on their end. They need to sort it and fix it.
Wildberryjack wrote: »
Here's the thing, this all started after the May 7 update and that mess with stuff carrying over from PTS to live. I don't believe in coincidences. It's on their end. They need to sort it and fix it.
The logical conclusion is that any ddos attack was likely to have been provoked by the PTS incident, not that the issue is at the server.
Wildberryjack wrote: »Either way it's on their end. Funny that it started for everyone on May 7, after that PTS debacle, and that the EU server is not having this issue.
May I ask what I should see? I got a timeout after Akamai.
Yes, it looks like your signal got hung up at Akami before it was redirected to ZOS. 143ms is significant lag.It's a good thing that ZOS is a customer of akamai because they provide top notch ddos mitigation solutions but it doesn't mean there's any ddos mitigations currently active.
I guarantee you that every bit of data that gets to the ZOS servers is sent to the scrubber service first.
[snip]
[edited for baiting]