-
latency issue at Paris 1
C:\Users\wilhi>tracert 188.138.40.87
Tracing route to loft4745.serverprofi24.eu [188.138.40.87]
over a maximum of 30 hops:
1 4 ms 3 ms 2 ms SkyRouter.Home [192.168.0.1]
2 9 ms 11 ms 8 ms 97e7fe7e.skybroadband.com [151.231.254.126]
3 14 ms 13 ms 12 ms be367.pr2.bllon.isp.sky.com [2.120.8.6]
4 12 ms 16 ms 15 ms lag-102.ear1.London1.Level3.net [212.113.9.141]
5 * * 22 ms ae-1-3102.ear2.Paris1.Level3.net [4.69.140.30]
6 49 ms 29 ms 29 ms 213.242.120.246
7 31 ms 29 ms 29 ms ae0-v100.sr-helios.sxb1.mass.systems [87.230.112.5]
8 26 ms 26 ms 35 ms 92.204.12.11
9 33 ms 27 ms 31 ms static-ip-62-75-135-102.inaddr.ip-pool.com [62.75.135.102]
10 27 ms 26 ms 26 ms loft4745.serverprofi24.eu [188.138.40.87]
Trace complete.
C:\Users\wilhi>
The above is causing me real headaches as the game is unplayable. There is notthing wrong with my network and all ports are opened. The trace has shown the issue to be at hop 5 Paris 1. Is there a workaround to avoid that hop?
-
Latency after that hop looks mostly fine. So it might be just dropping ping requests because of high load while processing everything else normally. Besides, you are tracing the route to logon server not to the realm that you are playing on.
If that hop really is what's causing your issue, the only thing you can do is using a VPN. But VPNs that use a shared IP address and especially free ones can get your account banned because most of their IP addresses are already banned because people have been using them to break the rules.
Edit: Icecrown realms IP is 54.36.105.148. If you are playing on Icecrown and want more accurate results, use ping or tracert command on that. But most of the hops won't answer to tracert.