Pinging ESO server

azfardajiwang

I need to ping ESO NA/PC Megaserver to test my connection issue.
Kept on getting lag spikes after reinstalling the game yesterday.
Is the updated IP 198.20.198.110 ?

I got the link from 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 . Not sure if it''s outdated tho.

@ZOS_GinaBruno @ZOS_JessicaFolsom

Elsonso

ZeniMax owns a lot of IP addresses. I would not use 198.20.198.110. Today, I am connected to 198.20.200.159 and 198.20.200.23.

It does not matter since you won't be able to ping the megaserver, anyway. There are blocks in place to prevent that.

Nadar

While it's true that your pathping will get blocked before it reaches the actual server, running it is still very useful as many of the lag, disconnect and other connection-type issues are actually with your ISP or their extended network rather than ZOS itself. If your pathping shows ZERO packet loss (or 100% on some nodes that are blocking the ping), the issue is likely with ZOS...but if the report shows some level of packet loss on intermediate nodes that is between 0% and 100%, the issue is likely with your ISP.

BTW, one way to find out the ip@ of the ZOS server you've connected with is to use the Windows resource monitor (with win7/8/10 at least).

• log into eso and be in the game
• right click on your task bar and select 'Start Task Manager'
• select the 'Performance' tab
• select 'Open Resource Monitor' link along the bottom of the dialog (should bring up a new dialog window)
• select the 'Network' tab
• In the 'Processes with Network Activity' section, select eso64.exe (or probably eso.exe if running 32bit). This will filter out other network activity and make it easier to find the eso connections.
• In the 'Network Activity' section you'll see several eso connections, use the ip@ from the one with the most activity. Currently, eso NA appears to be running on a 198.20.200.xx subnet although as the change from what the reddit post shows, it can change over time.

Elsonso

Nadar wrote: »

While it's true that your pathping will get blocked before it reaches the actual server, running it is still very useful as many of the lag, disconnect and other connection-type issues are actually with your ISP or their extended network rather than ZOS itself. If your pathping shows ZERO packet loss (or 100% on some nodes that are blocking the ping), the issue is likely with ZOS...but if the report shows some level of packet loss on intermediate nodes that is between 0% and 100%, the issue is likely with your ISP.

If you are showing ZERO packet loss between your computer and Akamai, the issue could be anywhere between the Akamai entry point and ZOS, including nodes in both Akamai and ZOS, but also including any node between them that might not be owned by either.

If you are showing packet loss between your computer and Akamai, then the problem is with the first node where there is packet loss, which could be your local hardware, your ISP, or it could be some node along the path.

Nadar

Thanks for the clarification....although it doesn't make much difference as the only node a gamer is likely able to do anything about would be for issues with their gateway device (or other LAN nodes they control). Anything beyond that is out of their control and they'll likely not even be able to get anyone from an ISP (or beyond) to admit there is a problem.

My point was that pathping can help narrow where the problem is and perhaps let you know if you should be mad at ZOS , one of the ISPs in the connection path or with your local equipment.

Elsonso

Nadar wrote: »

Thanks for the clarification....although it doesn't make much difference as the only node a gamer is likely able to do anything about would be for issues with their gateway device (or other LAN nodes they control). Anything beyond that is out of their control and they'll likely not even be able to get anyone from an ISP (or beyond) to admit there is a problem.

My point was that pathping can help narrow where the problem is and perhaps let you know if you should be mad at ZOS , one of the ISPs in the connection path or with your local equipment.

Under the best conditions, it is possible to isolate a node on the internet between Player and Game that is a problem. We found one such node a couple months back. With the help of ZOS, who did not own the problem node, I guess that got resolved. Now, with Akamai in the mix, we cannot even do that as effectively. If there is a node between the Akamai entry point and the ZOS server that is dropping packets, we cannot tell where it is.

We can certainly tell when there might be equipment problems locally. However, I find that the best way to tell that is to Google the make and model of the local router to see what complaints people have. Not all routers are made the same. Some are woefully underpowered or have limited buffer memory. These routers can result in lag or lost packets, and that won't show up in a ping report, and might not even show up in a speed report. A proper stress test needs to be done to determine at what point the router gives up and cries Uncle!

Every game has the potential to load the router differently, too. Multiple people on the same router can change how the router works. There are a lot of ways cheap routers can cause problems, depending on what is going on locally and how it is being used.

aetherial_heavenn

1 2 ms 1 ms 2 ms dsldevice.lan [10.1.1.1]
2 27 ms 28 ms 29 ms nme-apt-bur-bras31-lo1.tpgi.com.au [203.219.198.42]
3 37 ms 34 ms 38 ms 203-219-155-130.tpgi.com.au [203.219.155.130]
4 52 ms 39 ms 38 ms 203-221-3-68.tpgi.com.au [203.221.3.68]
5 149 ms 139 ms 139 ms ix-ae-7-0.tcore2.tv2-tokyo.as6453.net [180.87.181.21]
6 184 ms 179 ms 178 ms 180.87.181.42
7 149 ms 148 ms 139 ms po110.bs-a.sech-tyo.netarch.akamai.com [72.52.56.192]
8 154 ms 148 ms 149 ms ae120.access-a.sech-tyo.netarch.akamai.com [72.52.56.197]
9 222 ms 218 ms 217 ms 93.191.173.29
10 257 ms 248 ms 249 ms a72-52-29-88.deploy.static.akamaitechnologies.com [72.52.29.88]
11 247 ms 248 ms 249 ms 198.20.192.4
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 *

Vapirko

You can't really ping ESO servers anymore because of their DDOS protection. Sometimes it shows the end result sometimes it gets the request time out.

ajm1946

Have just done a ping test from NZL.
NZL - Aus (Telstra) - HKG then on from there, no bloody wonder lag is xxxx at the moment

Tracing route to 198.20.200.159 over a maximum of 30 hops

0 DESKTOP-EN1OFK5 [192.168.1.67]
1 homerouter.cpe [192.168.1.254]
2 10.207.224.169
3 * mdr-ip24-int.msc.global-gateway.net.nz [122.56.116.6]
4 ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
6 xe1-0-2.sebr3.global-gateway.net.nz [202.50.232.114]
7 122.56.119.86
8 i-0-4-0-0.sydp01.bi.telstraglobal.net [202.84.223.10]
9 i-0-1-0-7.sydp-core03.bi.telstraglobal.net [202.84.223.9]
10 i-11101.hkhh-core02.telstraglobal.net [202.84.138.45]
11 i-0-0-0-2.hkmi02.telstraglobal.net [202.84.138.113]
12 unknown.telstraglobal.net [202.127.78.186]
13 po110.bs-a.sech-hkg2.netarch.akamai.com [72.52.2.176]
14 ae120.access-a.sech-hkg2.netarch.akamai.com [72.52.2.181]
15 93.191.173.93
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-EN1OFK5 [192.168.1.67]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% homerouter.cpe [192.168.1.254]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.207.224.169
0/ 100 = 0% |
3 50ms 0/ 100 = 0% 0/ 100 = 0% mdr-ip24-int.msc.global-gateway.net.nz [122.56.116.6]
0/ 100 = 0% |
4 52ms 0/ 100 = 0% 0/ 100 = 0% ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
0/ 100 = 0% |
5 50ms 0/ 100 = 0% 0/ 100 = 0% ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
0/ 100 = 0% |
6 75ms 0/ 100 = 0% 0/ 100 = 0% xe1-0-2.sebr3.global-gateway.net.nz [202.50.232.114]
0/ 100 = 0% |
7 76ms 0/ 100 = 0% 0/ 100 = 0% 122.56.119.86
0/ 100 = 0% |
8 80ms 0/ 100 = 0% 0/ 100 = 0% i-0-4-0-0.sydp01.bi.telstraglobal.net [202.84.223.10]
0/ 100 = 0% |
9 80ms 0/ 100 = 0% 0/ 100 = 0% i-0-1-0-7.sydp-core03.bi.telstraglobal.net [202.84.223.9]
0/ 100 = 0% |
10 190ms 0/ 100 = 0% 0/ 100 = 0% i-11101.hkhh-core02.telstraglobal.net [202.84.138.45]
0/ 100 = 0% |
11 189ms 0/ 100 = 0% 0/ 100 = 0% i-0-0-0-2.hkmi02.telstraglobal.net [202.84.138.113]
0/ 100 = 0% |
12 212ms 0/ 100 = 0% 0/ 100 = 0% unknown.telstraglobal.net [202.127.78.186]
100/ 100 =100% |
13 --- 100/ 100 =100% 0/ 100 = 0% po110.bs-a.sech-hkg2.netarch.akamai.com [72.52.2.176]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% ae120.access-a.sech-hkg2.netarch.akamai.com [72.52.2.181]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 93.191.173.93

Trace complete.