I am getting extremely high world latency for seemingly no reason. This has never been an issue for me in the past. I deleted all addons, reset interface, ensured no firewall conflict, and etc. I can’t seem to fix it. Game is unplayable.
Tracert is below to server Illidan US.
Can anyone help me understand what is happening?
C:\Users\NAME>tracert 206.18.148.176
Tracing route to 206.18.148.176 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms [192.168.1.254]
2 2 ms 1 ms 1 ms 107-141-0-1. [107.141.0.1]
3 2 ms 2 ms 2 ms 99.174.25.206
4 16 ms 16 ms 16 ms 32.130.24.64
5 17 ms 17 ms 17 ms 32.130.20.5
6 17 ms 17 ms 17 ms 32.130.20.44
7 24 ms 23 ms 23 ms 32.130.17.83
8 21 ms 23 ms 23 ms [12.122.152.70]
9 17 ms 16 ms 17 ms 12.122.97.13
10 178 ms 244 ms 229 ms [12.124.15.30]
11 * * * Request timed out.
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 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Users\NAME>
The wiki ip addresses are outdated, the ip address may not be updated as blizzard no longer publicly posts those. World just happens to be the server you’re connected to, especially with crossrealms, you could be connecting Vegas, Chicago or Australia.
What i do see is a backbone handoff, hop 10. Where are you connecting from, and what kind of internet?
Everything after 10 is simply rejects of the ping packet, normal security to help reject some DDoS attacks.
It doesn’t look to be in your network, and maybe a backbone outside of your isp. Nothing to fix on your end.
AT&T Fiber.
Tennessee, US
This is the only game I have a problem with.
same thing is happening to me. It’s causing me a lot of issues with keys and raiding. All of the disconnects and lag I’m having is isolated to WoW only. All other services I use including TV streaming, youtube, etc never have sudden lag or drops in connection. It all started happening around March 13th. Before then I never had any problems.
The jump from hop 9 to 10 shows a problem inside AT&T’s network so you’ll want to give them a call.
That is always possible with any service since they aren’t hosted in the same building. It’s like the road to your grocery store being blocked, but the road to your dentist is fine.
Total noob here, but I’m having a similar issue but with a different ISP (comcast).
When you say the hop shows a problem inside AT&Ts network, how do you know that? Is it just the ping increase between step 9 and 10? What would I say when I call the ISP?
For reference my results w. a similar test don’t show a marketed step up in ping on any one step, however, should i be concerned about the ‘timed out’ going from step 9 to 10?
Thanks for the help!
Tracing route to 206.18.148.176 over a maximum of 30 hops
1 3 ms 3 ms 2 ms 10.0.0.1
2 17 ms 21 ms 24 ms 10.112.238.67
3 18 ms 16 ms 18 ms [68.85.103.205]
4 13 ms 15 ms 18 ms [68.85.86.193]
5 17 ms 20 ms 30 ms [68.85.57.245]
6 16 ms 20 ms 29 ms [96.216.230.178]
7 20 ms 20 ms 18 ms [96.216.231.69]
8 * 21 ms 24 ms [68.86.93.253]
9 20 ms 36 ms 26 ms [96.110.40.222]
10 * * * Request timed out.
11 42 ms 44 ms 40 ms [96.110.39.21]
12 53 ms 38 ms 42 ms [96.110.36.206]
13 43 ms 42 ms 44 ms [96.110.39.97]
14 46 ms 44 ms 39 ms [96.110.39.66]
15 67 ms 64 ms 62 ms [96.110.37.149]
16 64 ms 64 ms 66 ms [96.110.35.53]
17 62 ms 78 ms 66 ms [96.110.35.22]
18 70 ms 66 ms 67 ms [96.110.36.105]
19 64 ms 68 ms 67 ms [68.86.84.201]
20 70 ms 69 ms 62 ms [68.86.84.74]
21 86 ms 84 ms 75 ms [96.110.38.66]
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 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Please don’t hijack someone’s thread with your issue. I’ll answer your questions, but if you have other questions, you’ll need to make a new thread. All replies alert the OP, and it’s not fair to keep doing so when we already finished their troubleshooting.
Yes.
As you said, you’re not experiencing this, so you wouldn’t mention anything about those hops because that wouldn’t make sense.
The test you’re using isn’t meant for testing connection quality. This test is ideal if you can’t login and that’s about it. For ongoing latency issues, you need something like a WinMTR. You’ll have to run the test to Google’s DNS (8.8.8.8) or something else because WoW server IPs aren’t posted publicly for me to share.
Additional troubleshooting will only take place in a new thread.