Maintenance for the week of December 16:
• PC/Mac: No maintenance – December 16
• NA megaservers for patch maintenance – December 17, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• EU megaservers for patch maintenance – December 17, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
• PC/Mac: No maintenance – December 16
• NA megaservers for patch maintenance – December 17, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• EU megaservers for patch maintenance – December 17, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
999+ Ping
Gaudium
Soul Shriven
Hello,
So i just recovered my account after not playing for several years.
What i found out is the game is now in an unplayable state. I've been in contact with support for the past week, and according to the last reply my issue has been elevated to another team that will look into the issue.
I am from Israel, using a 200 mpbs DL and 5 mpbs UL.
What seems to be happening is my connection being routed through U.S (I guess it is a login server?) then into EU and back into IL.
While i am getting 200-300 ping to the U.S server on this website https://pingtestlive.com/eso-status
I am getting +999 in game. While for EU the ping is in the 6000-9000 thousand. Which makes no sense since i play any other game from HOTS to LOL or PUBG with a ping of 60-90 on European servers.
This shows the way the connection is:
https://imgur.com/a/TnpfK1n
This is the same thing when i use a VPN and connect to a German server, notice the sudden improvement:
https://imgur.com/a/IpoZQoA
When in game with a VPN:
https://imgur.com/a/sgPXOi7
NETSTAT RESULTS
Active Connections
Proto Local Address Foreign Address State
TCP 100.127.255.253:49813 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49814 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49815 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49816 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49817 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49818 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49919 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49920 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49921 95.101.72.223:443 CLOSE_WAIT
TCP 100.127.255.253:49922 95.101.72.223:443 CLOSE_WAIT
TCP 100.127.255.253:49923 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49924 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49925 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49926 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49927 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49928 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49929 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49930 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49931 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49932 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49934 104.122.227.71:443 CLOSE_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55187 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55188 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55189 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55190 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55191 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55192 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55193 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55194 TIME_WAIT
TCP 127.0.0.1:54867 127.0.0.1:54868 TIME_WAIT
TCP 192.168.1.11:50316 13.115.90.56:443 ESTABLISHED
TCP 192.168.1.11:50392 34.198.69.12:443 ESTABLISHED
TCP 192.168.1.11:50404 34.202.170.241:443 ESTABLISHED
TCP 192.168.1.11:53140 13.107.42.11:443 ESTABLISHED
TCP 192.168.1.11:53715 64.30.228.84:443 ESTABLISHED
TCP 192.168.1.11:54181 40.67.251.132:443 ESTABLISHED
TCP 192.168.1.11:54906 162.159.136.234:443 ESTABLISHED
TCP 192.168.1.11:55140 162.159.134.233:443 ESTABLISHED
TCP 192.168.1.11:55154 162.159.129.232:443 ESTABLISHED
TCP 192.168.1.11:55162 159.100.232.100:24507 TIME_WAIT
TCP 192.168.1.11:55163 159.100.232.224:24121 TIME_WAIT
TCP 192.168.1.11:55164 40.69.216.251:443 ESTABLISHED
TCP 192.168.1.11:55166 74.117.206.104:443 TIME_WAIT
TCP 192.168.1.11:55167 74.117.206.104:443 TIME_WAIT
TCP 192.168.1.11:55168 52.109.24.4:443 ESTABLISHED
TCP 192.168.1.11:55169 52.114.128.9:443 ESTABLISHED
TCP 192.168.1.11:55170 52.114.128.9:443 ESTABLISHED
TCP 192.168.1.11:55172 198.20.198.110:443 ESTABLISHED
TCP 192.168.1.11:55174 2.22.146.145:80 ESTABLISHED
TCP 192.168.1.11:55181 82.166.7.235:443 CLOSE_WAIT
TCP 192.168.1.11:55182 74.117.206.104:443 ESTABLISHED
TCP 192.168.1.11:55183 159.100.230.9:443 TIME_WAIT
TCP 192.168.1.11:55185 95.100.156.104:80 ESTABLISHED
TCP 192.168.1.11:55186 159.100.230.100:80 ESTABLISHED
TCP 192.168.1.11:55195 88.221.170.14:443 ESTABLISHED
PING RESULTS
pinging: patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.136] with 32 bytes of data:
Reply from 95.100.156.136: bytes=32 time=105ms TTL=50
Reply from 95.100.156.136: bytes=32 time=92ms TTL=50
Reply from 95.100.156.136: bytes=32 time=88ms TTL=50
Reply from 95.100.156.136: bytes=32 time=90ms TTL=50
Ping statistics for 95.100.156.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 105ms, Average = 93ms
pinging: launcher.bethesda.net
Pinging launcher.bethesda.net [159.100.230.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 159.100.230.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
pinging: live.patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.136] with 32 bytes of data:
Reply from 95.100.156.136: bytes=32 time=78ms TTL=50
Reply from 95.100.156.136: bytes=32 time=79ms TTL=50
Reply from 95.100.156.136: bytes=32 time=207ms TTL=50
Reply from 95.100.156.136: bytes=32 time=79ms TTL=50
Ping statistics for 95.100.156.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 207ms, Average = 110ms
pinging: liveeu.patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.136] with 32 bytes of data:
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Ping statistics for 95.100.156.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms
pinging: pts.patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.145] with 32 bytes of data:
Reply from 95.100.156.145: bytes=32 time=76ms TTL=51
Reply from 95.100.156.145: bytes=32 time=78ms TTL=51
Reply from 95.100.156.145: bytes=32 time=76ms TTL=51
Reply from 95.100.156.145: bytes=32 time=77ms TTL=51
Ping statistics for 95.100.156.145:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 78ms, Average = 76ms
pinging: launcher.patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.136] with 32 bytes of data:
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=78ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Ping statistics for 95.100.156.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms
Pathping RESULTS
pathing: patcher.elderscrollsonline.com
Tracing route to a1092.d.akamai.net [95.100.156.145]
over a maximum of 30 hops:
0 192.168.1.11
1 192.168.1.1
2 10.206.2.1
3 172.18.4.206
4 172.17.0.82
5 172.17.10.181
6 82.102.128.9
7 * * *
Computing statistics for 1 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.11
0/ 1 = 0% |
1 40ms 0/ 1 = 0% 0/ 1 = 0% 192.168.1.1
0/ 1 = 0% |
2 --- 1/ 1 =100% 1/ 1 =100% 10.206.2.1
0/ 1 = 0% |
3 --- 1/ 1 =100% 1/ 1 =100% 172.18.4.206
0/ 1 = 0% |
4 --- 1/ 1 =100% 1/ 1 =100% 172.17.0.82
0/ 1 = 0% |
5 --- 1/ 1 =100% 1/ 1 =100% 172.17.10.181
0/ 1 = 0% |
6 11ms 0/ 1 = 0% 0/ 1 = 0% 82.102.128.9
Trace complete.
pathing: launcher.bethesda.net
Tracing route to launcher.bethesda.net [159.100.230.100]
over a maximum of 30 hops:
0 192.168.1.11
1 192.168.1.1
2 10.206.2.1
3 172.18.4.206
4 172.17.0.82
5 * * *
Computing statistics for 1 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.11
0/ 1 = 0% |
1 0ms 0/ 1 = 0% 0/ 1 = 0% 192.168.1.1
1/ 1 =100% |
2 --- 1/ 1 =100% 0/ 1 = 0% 10.206.2.1
0/ 1 = 0% |
3 --- 1/ 1 =100% 0/ 1 = 0% 172.18.4.206
0/ 1 = 0% |
4 --- 1/ 1 =100% 0/ 1 = 0% 172.17.0.82
Trace complete.
pathing: live.patcher.elderscrollsonline.com
Tracing route to a1092.d.akamai.net [95.100.156.145]
over a maximum of 30 hops:
0 192.168.1.11
1 192.168.1.1
2 10.206.2.1
3 172.18.4.206
4 172.17.0.82
5 * 172.17.10.181
6 82.102.128.9
7 * * *
Computing statistics for 1 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.11
0/ 1 = 0% |
1 0ms 0/ 1 = 0% 0/ 1 = 0% 192.168.1.1
0/ 1 = 0% |
2 --- 1/ 1 =100% 1/ 1 =100% 10.206.2.1
0/ 1 = 0% |
3 --- 1/ 1 =100% 1/ 1 =100% 172.18.4.206
0/ 1 = 0% |
4 --- 1/ 1 =100% 1/ 1 =100% 172.17.0.82
0/ 1 = 0% |
5 --- 1/ 1 =100% 1/ 1 =100% 172.17.10.181
0/ 1 = 0% |
6 14ms 0/ 1 = 0% 0/ 1 = 0% 82.102.128.9
Trace complete.
I wanted to share this, and to know if anyone else suffers the same problems from Israel or Europe?
I am no expert but it seems there are some serious issues with hops into U.S then EU, then U.S, then EU... that the client makes as you can see from that long report. Which you can also generate by the way via ESO launcher -> clicking the "Cog" icon top right -> then "About" and running "Game Consultant".
I refuse to believe this is on my end, since this is the only game that i have encountered something so hectic, in comparison to any other game out there that i currently play with no problem.
Obviously ports are forwarded via DMZ, DNS is flushed, everything is up to day etc etc..
I assume that if it works with a VPN that means the client changes routes from my starting location, which bring me to a similar issue i had with Escape From Tarkov.
In EFT they had the EU region, U.S Region, and everything else. That was couple years ago so something might've change by now.
What happened was that Israel fell under the "Everything Else" which defaulted into Australia servers i believe? Which gave me a ping of 400+ and i had to actually buy and upgrade to be able to connect to the EU servers.
Now this issue reminds me of that since a VPN seems to fix the problem.
So i just recovered my account after not playing for several years.
What i found out is the game is now in an unplayable state. I've been in contact with support for the past week, and according to the last reply my issue has been elevated to another team that will look into the issue.
I am from Israel, using a 200 mpbs DL and 5 mpbs UL.
What seems to be happening is my connection being routed through U.S (I guess it is a login server?) then into EU and back into IL.
While i am getting 200-300 ping to the U.S server on this website https://pingtestlive.com/eso-status
I am getting +999 in game. While for EU the ping is in the 6000-9000 thousand. Which makes no sense since i play any other game from HOTS to LOL or PUBG with a ping of 60-90 on European servers.
This shows the way the connection is:
https://imgur.com/a/TnpfK1n
This is the same thing when i use a VPN and connect to a German server, notice the sudden improvement:
https://imgur.com/a/IpoZQoA
When in game with a VPN:
https://imgur.com/a/sgPXOi7
NETSTAT RESULTS
Active Connections
Proto Local Address Foreign Address State
TCP 100.127.255.253:49813 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49814 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49815 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49816 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49817 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49818 104.122.227.71:443 CLOSE_WAIT
TCP 100.127.255.253:49919 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49920 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49921 95.101.72.223:443 CLOSE_WAIT
TCP 100.127.255.253:49922 95.101.72.223:443 CLOSE_WAIT
TCP 100.127.255.253:49923 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49924 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49925 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49926 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49927 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49928 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49929 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49930 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49931 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49932 23.210.254.117:80 CLOSE_WAIT
TCP 100.127.255.253:49934 104.122.227.71:443 CLOSE_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55187 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55188 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55189 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55190 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55191 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55192 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55193 TIME_WAIT
TCP 127.0.0.1:54062 127.0.0.1:55194 TIME_WAIT
TCP 127.0.0.1:54867 127.0.0.1:54868 TIME_WAIT
TCP 192.168.1.11:50316 13.115.90.56:443 ESTABLISHED
TCP 192.168.1.11:50392 34.198.69.12:443 ESTABLISHED
TCP 192.168.1.11:50404 34.202.170.241:443 ESTABLISHED
TCP 192.168.1.11:53140 13.107.42.11:443 ESTABLISHED
TCP 192.168.1.11:53715 64.30.228.84:443 ESTABLISHED
TCP 192.168.1.11:54181 40.67.251.132:443 ESTABLISHED
TCP 192.168.1.11:54906 162.159.136.234:443 ESTABLISHED
TCP 192.168.1.11:55140 162.159.134.233:443 ESTABLISHED
TCP 192.168.1.11:55154 162.159.129.232:443 ESTABLISHED
TCP 192.168.1.11:55162 159.100.232.100:24507 TIME_WAIT
TCP 192.168.1.11:55163 159.100.232.224:24121 TIME_WAIT
TCP 192.168.1.11:55164 40.69.216.251:443 ESTABLISHED
TCP 192.168.1.11:55166 74.117.206.104:443 TIME_WAIT
TCP 192.168.1.11:55167 74.117.206.104:443 TIME_WAIT
TCP 192.168.1.11:55168 52.109.24.4:443 ESTABLISHED
TCP 192.168.1.11:55169 52.114.128.9:443 ESTABLISHED
TCP 192.168.1.11:55170 52.114.128.9:443 ESTABLISHED
TCP 192.168.1.11:55172 198.20.198.110:443 ESTABLISHED
TCP 192.168.1.11:55174 2.22.146.145:80 ESTABLISHED
TCP 192.168.1.11:55181 82.166.7.235:443 CLOSE_WAIT
TCP 192.168.1.11:55182 74.117.206.104:443 ESTABLISHED
TCP 192.168.1.11:55183 159.100.230.9:443 TIME_WAIT
TCP 192.168.1.11:55185 95.100.156.104:80 ESTABLISHED
TCP 192.168.1.11:55186 159.100.230.100:80 ESTABLISHED
TCP 192.168.1.11:55195 88.221.170.14:443 ESTABLISHED
PING RESULTS
pinging: patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.136] with 32 bytes of data:
Reply from 95.100.156.136: bytes=32 time=105ms TTL=50
Reply from 95.100.156.136: bytes=32 time=92ms TTL=50
Reply from 95.100.156.136: bytes=32 time=88ms TTL=50
Reply from 95.100.156.136: bytes=32 time=90ms TTL=50
Ping statistics for 95.100.156.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 105ms, Average = 93ms
pinging: launcher.bethesda.net
Pinging launcher.bethesda.net [159.100.230.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 159.100.230.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
pinging: live.patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.136] with 32 bytes of data:
Reply from 95.100.156.136: bytes=32 time=78ms TTL=50
Reply from 95.100.156.136: bytes=32 time=79ms TTL=50
Reply from 95.100.156.136: bytes=32 time=207ms TTL=50
Reply from 95.100.156.136: bytes=32 time=79ms TTL=50
Ping statistics for 95.100.156.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 207ms, Average = 110ms
pinging: liveeu.patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.136] with 32 bytes of data:
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Ping statistics for 95.100.156.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms
pinging: pts.patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.145] with 32 bytes of data:
Reply from 95.100.156.145: bytes=32 time=76ms TTL=51
Reply from 95.100.156.145: bytes=32 time=78ms TTL=51
Reply from 95.100.156.145: bytes=32 time=76ms TTL=51
Reply from 95.100.156.145: bytes=32 time=77ms TTL=51
Ping statistics for 95.100.156.145:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 78ms, Average = 76ms
pinging: launcher.patcher.elderscrollsonline.com
Pinging a1092.d.akamai.net [95.100.156.136] with 32 bytes of data:
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=78ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Reply from 95.100.156.136: bytes=32 time=77ms TTL=50
Ping statistics for 95.100.156.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms
Pathping RESULTS
pathing: patcher.elderscrollsonline.com
Tracing route to a1092.d.akamai.net [95.100.156.145]
over a maximum of 30 hops:
0 192.168.1.11
1 192.168.1.1
2 10.206.2.1
3 172.18.4.206
4 172.17.0.82
5 172.17.10.181
6 82.102.128.9
7 * * *
Computing statistics for 1 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.11
0/ 1 = 0% |
1 40ms 0/ 1 = 0% 0/ 1 = 0% 192.168.1.1
0/ 1 = 0% |
2 --- 1/ 1 =100% 1/ 1 =100% 10.206.2.1
0/ 1 = 0% |
3 --- 1/ 1 =100% 1/ 1 =100% 172.18.4.206
0/ 1 = 0% |
4 --- 1/ 1 =100% 1/ 1 =100% 172.17.0.82
0/ 1 = 0% |
5 --- 1/ 1 =100% 1/ 1 =100% 172.17.10.181
0/ 1 = 0% |
6 11ms 0/ 1 = 0% 0/ 1 = 0% 82.102.128.9
Trace complete.
pathing: launcher.bethesda.net
Tracing route to launcher.bethesda.net [159.100.230.100]
over a maximum of 30 hops:
0 192.168.1.11
1 192.168.1.1
2 10.206.2.1
3 172.18.4.206
4 172.17.0.82
5 * * *
Computing statistics for 1 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.11
0/ 1 = 0% |
1 0ms 0/ 1 = 0% 0/ 1 = 0% 192.168.1.1
1/ 1 =100% |
2 --- 1/ 1 =100% 0/ 1 = 0% 10.206.2.1
0/ 1 = 0% |
3 --- 1/ 1 =100% 0/ 1 = 0% 172.18.4.206
0/ 1 = 0% |
4 --- 1/ 1 =100% 0/ 1 = 0% 172.17.0.82
Trace complete.
pathing: live.patcher.elderscrollsonline.com
Tracing route to a1092.d.akamai.net [95.100.156.145]
over a maximum of 30 hops:
0 192.168.1.11
1 192.168.1.1
2 10.206.2.1
3 172.18.4.206
4 172.17.0.82
5 * 172.17.10.181
6 82.102.128.9
7 * * *
Computing statistics for 1 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.11
0/ 1 = 0% |
1 0ms 0/ 1 = 0% 0/ 1 = 0% 192.168.1.1
0/ 1 = 0% |
2 --- 1/ 1 =100% 1/ 1 =100% 10.206.2.1
0/ 1 = 0% |
3 --- 1/ 1 =100% 1/ 1 =100% 172.18.4.206
0/ 1 = 0% |
4 --- 1/ 1 =100% 1/ 1 =100% 172.17.0.82
0/ 1 = 0% |
5 --- 1/ 1 =100% 1/ 1 =100% 172.17.10.181
0/ 1 = 0% |
6 14ms 0/ 1 = 0% 0/ 1 = 0% 82.102.128.9
Trace complete.
I wanted to share this, and to know if anyone else suffers the same problems from Israel or Europe?
I am no expert but it seems there are some serious issues with hops into U.S then EU, then U.S, then EU... that the client makes as you can see from that long report. Which you can also generate by the way via ESO launcher -> clicking the "Cog" icon top right -> then "About" and running "Game Consultant".
I refuse to believe this is on my end, since this is the only game that i have encountered something so hectic, in comparison to any other game out there that i currently play with no problem.
Obviously ports are forwarded via DMZ, DNS is flushed, everything is up to day etc etc..
I assume that if it works with a VPN that means the client changes routes from my starting location, which bring me to a similar issue i had with Escape From Tarkov.
In EFT they had the EU region, U.S Region, and everything else. That was couple years ago so something might've change by now.
What happened was that Israel fell under the "Everything Else" which defaulted into Australia servers i believe? Which gave me a ping of 400+ and i had to actually buy and upgrade to be able to connect to the EU servers.
Now this issue reminds me of that since a VPN seems to fix the problem.
2
-
MrGarlic✭✭✭✭✭
✭<SNIP>
Now this issue reminds me of that since a VPN seems to fix the problem.
That is what many of us do now.
Your second level ticket will just tell you it's your ISP. That's their default answer to this problem. Your ISP will say it's ZOS's fault. No one will fix the problem because neither your ISP nor ZOS will accept responsibility for the problem. So the onus is on us to solve our own problems, and a VPN seems to be the fix for you.
Mudfish VPN works well for me.
Good luck.
'Sharp Arrows'Mr.GarlicHidden by darkness, a shadow in the night,A sped arrow dissecting the gloom,Finding it's target, such delight.0 -
Unfadingsilence✭✭✭✭✭
✭Unfadingsilence wrote: »Get better internet
Thanks, that fixed my problem.
Honestly your running 200mpbs download speed which wont help your game play at all and only 5mpbs download speed like wow your probably better off using your cell phone as a hotspot with speeds that slow but in all honesty it does not matter the game is broken anyways I'm running 1gig upload and 1gig download speeds and still hit 5fps2 -
Delparis✭✭✭✭✭The EU server has serious issues
if you want my advice, better play in the US as servers seems to be better there.
also take a look at this thread to understand better what is happening
https://forums.elderscrollsonline.com/en/discussion/477841/eu-server-performance-update-from-matt-firor#latestEdited by Delparis on June 29, 2019 9:21PM1 -
MartiniDaniels✭✭✭✭✭
✭✭✭✭✭Yes, I HAD same issue two weeks ago. Now it became better, but I didn't change anything on my side. I think it depends on mere luck, i.e. to which server processor you were routed for processing (has nothing to do with login server). Of course I don't know how exactly ZOS megaserver works, but from servers I saw, uneven load on different boards is absolutely common thing.0 -
GaudiumSoul ShrivenI'm going to look into that MudFish VPN for now, thanks for the replies.
We'll see what support comes up with, but yeah i am not getting my hopes up.
0 -
GaudiumSoul ShrivenIn response to a support representative i found an interesting thing, at least i think so:
Hi,
I am not getting +999 ping for now, but i haven't tested it for some serious play time since EU server has been having some issues after the patch.
I am having a terrible latency still though, instead of having from 60-100 i am having a ping of 130-260+.
Which is noticeable and creates a very frustrating delay to everything you do in game.
I will provide links with screenshots with an app called WinMTR that Path of Exile uses to trace routing problems.
In these screenshots you can see a server that repeats itself in both EU and NA. That server loses packets, and is stationed in the U.S. Why am i being routed through it, i have no idea since it is number 5 in the route.
Another interesting thing is that your ip's are different on this page:
https://pingtestlive.com/eso-status
vs this page:
https://help.elderscrollsonline.com/app/answers/detail/a_id/30903/~/how-do-i-do-a-pathping-and-tracert-to-the-servers-to-test-my-connection?
That server exists for two different EU ip's and two different NA ip's.
172.17.10.181 it is number 5 in the routing test
These are NA and EU from you support page:
https://help.elderscrollsonline.com/app/answers/detail/a_id/30903/~/how-do-i-do-a-pathping-and-tracert-to-the-servers-to-test-my-connection?
https://imgur.com/a/Is66Lz5
Both have that US server at number 5 that drops packets.
Now these contain NA and EU from this page:
https://pingtestlive.com/eso-status
https://imgur.com/a/SLb1HAT
Now a test with a vpn, and a test without a vpn:
https://imgur.com/a/IdcpnFf
Look at the difference of EU ping, and it isn't only that, the response time of the test is less than a second while without a VPN it takes almost half a minute to show 2xx+ ping.
Sadly i don't know if it is at all possible to trace it how it actually goes through the VPN, all i know is that i firstly get connected to a German server.
On this page
https://pingtestlive.com/eso-status
198.20.198.110
The IP that says EU is U.S on your support page:
https://help.elderscrollsonline.com/app/answers/detail/a_id/30903/~/how-do-i-do-a-pathping-and-tracert-to-the-servers-to-test-my-connection?
198.20.198.110
And vice verse on the U.S ip that is a EU ip, on these two pages.
Just to note that out.
Now this is the ping i get in CMD:
https://imgur.com/a/uera6lp
Attached with a screenshots of what i am getting in game. which is 130+ and constantly varies.
This is not alright, this does not happen in LoL, PoE, PubG, Battlefield 3,4,5,1 you get the idea.
So i hope you guys can figure this out because i am not the only one with this problem, steam forums and your official forums are filled with the same issue, some people didn't do this extensive testing but some did trace route and noticed something is really wrong.
This is a trace of a Danish player
https://imgur.com/a/Q0sxs3l
He doesn't have that U.S server in the middle of the connection.
The U.S server he is connected through is 10.116.25.1 and does not lose any packets.
Nor he has that number 7 (number 7 in my route) completely dead route that drops everything.Edited by Gaudium on July 3, 2019 6:13PM0