205 ms 205 ms 213 ms et-0-0-0-pe02-eqch2.as57976. net [137.221.69.49]
This is tracert to 24.105.62.129 (US Central)
Consistent 205ms ping in game. Rebooted my router, just cuz, didn’t change a thing.
Googled the as57976. net server and see tons of people complaining about that same one in the past… you guys can’t afford good hardware with those billions of dollars we’ve given ya?
A ping to google returns 16ms consistently, nothing else online is slow or problematic.
Edit 1: Still ongoing problem. Ping in game VERRRRY solid 205-206… oddly specific.
Quoting one hop in the test doesn’t mean much for the overall picture. Blizzard’s hops, just like most gaming companies, deprioritize pings from external sources because it’s a DDoS protection mechanism. And that’s why it’s easy to find complaints about it, even if it’s not the actual source of the problem
Please make sure you add a WinMTR here for troubleshooting.
Seems likely that the majority of the lag is coming from Level3 in the Chicago area. I say this because I’ve tried pinging the Chicago datacenter from my location (in the South) and my average ping is 57ms, with a worst of 63ms. But my connection does not use Level3 nodes to reach Blizzard.
While that company does work with Blizzard, and designated that node for Blizzard traffic, they’re not owned by them. Additionally, many of their hops seem hidden in the test (probably intended by them). Unfortunately, there is not much you can do about Level3 on your own, but this data may be something Blizzard can inquire about for players connecting in that area.
Cool, thank you for the response. I really appreciate it. It’s still on going many hours on. It’s really bizarre… it’s VERY solid 205ms… it’s almost like im being throttled.
I would LOVE to turn on a VPN to test it, but I’m concerned about doing that for obvious reasons.
ISPs do specifically throttle gaming traffic. However, Level3 showing those pings means it’s outside the ISP’s network and on a routing peer. A VPN can be used with WoW for testing, or even a mobile hotspot.
I see the number spikes, but they are data mitigation. We can tell this because all that truly matters is the ping and averages on the final hop. In the test you posted, this is 34ms average, 42ms worst ping.
I am having similar issues, when using battle.net looking glass it seems that the ping is being introduced from blizzard owned IPs and not specifically from Level 3. (My ISP goes through L3. I even tested it with my work VPN and saw the spikes in the same 137.221.x.x IPs from blizzard.
The Chicago L3 ip is adding another ~50ms to the total latency but the biggest spike is before it even gets to L3.
TRACEROUTE:
traceroute to --MY IP-- (--MY IP--), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.349 ms 0.317 ms 0.313 ms
2 37.244.23.131 (37.244.23.131) 0.562 ms 0.585 ms 0.650 ms
3 24.105.62.152 (24.105.62.152) 0.849 ms 0.891 ms 0.893 ms
4 137.221.66.10 (137.221.66.10) 1.911 ms 1.917 ms 1.916 ms
5 * * *
6 * * *
7 * * *
8 137.221.65.31 (137.221.65.31) 181.868 ms 182.120 ms 182.098 ms
9 137.221.65.97 (137.221.65.97) 181.865 ms 181.804 ms 181.785 ms
10 137.221.85.32 (137.221.85.32) 181.885 ms 183.835 ms 181.893 ms
11 Bundle-Ether100.ken-edge903.sydney.telstra.net (139.130.253.89) 184.612 ms 184.677 ms 184.319 ms
12 cen3361629.lnk.telstra.net (203.54.217.110) 189.658 ms 189.568 ms 189.800 ms
13 ae-1-3508.ear7.Chicago2.Level3.net (4.69.142.174) 185.534 ms 185.115 ms 185.078 ms
14 --LOCAL ISP IP-- (--LOCAL ISP IP--) 198.955 ms 198.940 ms 198.963 ms
15 --MY IP-- (--MY IP--) 198.612 ms 198.572 ms 198.532 ms
18/07/2021 17:30:14 UTC
--------------------
TRACEROUTE:
traceroute to --MY IP-- (--MY IP--), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.679 ms 0.665 ms 0.683 ms
2 24.105.18.2 (24.105.18.2) 0.960 ms 0.987 ms 1.083 ms
3 137.221.105.10 (137.221.105.10) 0.899 ms 0.919 ms 0.925 ms
4 137.221.66.20 (137.221.66.20) 1.096 ms 1.097 ms 1.093 ms
5 137.221.83.84 (137.221.83.84) 138.921 ms 138.978 ms 138.987 ms
6 * * *
7 137.221.65.31 (137.221.65.31) 139.021 ms 139.058 ms 139.069 ms
8 137.221.65.97 (137.221.65.97) 138.907 ms 138.914 ms 138.914 ms
9 137.221.85.32 (137.221.85.32) 139.054 ms 138.890 ms 138.893 ms
10 Bundle-Ether100.ken-edge903.sydney.telstra.net (139.130.253.89) 141.502 ms 141.920 ms 142.201 ms
11 cen3361629.lnk.telstra.net (203.54.217.110) 146.593 ms 146.850 ms 146.845 ms
12 ae-1-3508.ear7.Chicago2.Level3.net (4.69.142.174) 185.526 ms 185.556 ms 185.550 ms
13 --LOCAL ISP IP-- (--LOCAL ISP IP--) 198.611 ms 198.447 ms 198.547 ms
14 --MY IP-- (--MY IP--) 198.298 ms 198.340 ms 198.273 ms
18/07/2021 17:30:14 UTC
--------------------
MTR:
Start: Sun Jul 18 17:30:14 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.6 0.4 0.8 0.0
2.|-- 24.105.18.2 0.0% 10 0.9 0.8 0.6 0.9 0.0
3.|-- 137.221.105.10 0.0% 10 0.9 1.1 0.8 1.7 0.0
4.|-- 137.221.66.20 0.0% 10 0.7 6.6 0.5 60.5 18.9
5.|-- 137.221.83.84 0.0% 10 138.8 174.3 138.8 325.7 61.2
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.65.31 0.0% 10 139.1 151.3 138.8 202.1 26.0
8.|-- 137.221.65.97 0.0% 10 179.2 149.9 138.7 179.2 16.8
9.|-- 137.221.85.32 0.0% 10 139.0 144.9 139.0 171.5 12.2
10.|-- Bundle-Ether100.ken-edge903.sydney.telstra.net 0.0% 10 141.3 141.6 141.3 142.3 0.0
11.|-- cen3361629.lnk.telstra.net 0.0% 10 146.8 148.0 146.3 158.9 3.8
12.|-- ae-1-3508.ear7.Chicago2.Level3.net 0.0% 10 185.4 185.4 185.2 185.7 0.0
13.|-- --LOCAL ISP IP-- 0.0% 10 198.5 205.3 198.5 216.2 5.7
14.|-- --MY IP-- 0.0% 10 198.4 198.4 198.3 198.6 0.0
18/07/2021 17:30:13 UTC
--------------------
MTR:
Start: Sun Jul 18 17:30:15 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.7 0.3 0.2 0.7 0.0
2.|-- 37.244.23.131 0.0% 10 0.5 0.5 0.4 0.6 0.0
3.|-- 24.105.62.152 0.0% 10 0.9 0.8 0.7 0.9 0.0
4.|-- 137.221.66.10 0.0% 10 2.0 2.0 1.8 2.1 0.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.65.0 0.0% 10 1559. 2305. 1559. 3135. 422.8
8.|-- 137.221.65.31 0.0% 10 181.8 185.2 181.8 210.1 8.9
9.|-- 137.221.65.97 0.0% 10 181.9 218.2 181.8 358.2 62.3
10.|-- 137.221.85.32 0.0% 10 181.9 191.1 181.9 210.8 13.0
11.|-- Bundle-Ether100.ken-edge903.sydney.telstra.net 0.0% 10 184.5 184.5 184.4 184.6 0.0
12.|-- cen3361629.lnk.telstra.net 0.0% 10 190.1 190.8 189.6 197.6 2.3
13.|-- ae-1-3508.ear7.Chicago2.Level3.net 0.0% 10 185.2 185.2 185.1 185.4 0.0
14.|-- --LOCAL ISP IP-- 0.0% 10 199.2 200.3 198.7 204.7 2.3
15.|-- --MY IP-- 0.0% 10 198.8 198.7 198.6 198.8 0.0
Thanks for bringing this up, Drosera. I’m a bit surprised that this is still an issue. I can’t recall something like this lasting this long with WOW/Blizzard.
I’ve updated the title as this appears to be a routing issue between Level 3 Communications and the Blizzard network. Several smaller ISPs use Level 3 as a backbone to reach Blizzard servers (Greenlight Networks for example), so this issue will affect different ISPs. We are currently looking to gather connection data (WinMTR and Looking-Glass) in order to track the issue so that a solution can be found.
If anyone new comes across this thread please reply with 1) The name of your internet provider 2) State/country and 3) a WinMTR connection test. Thanks!
Right-click on the downloaded .zip folder and select “Extract All”, to extract the files to a new folder.
Open the new folder that was created, then open the WinMTR_x64 folder.
Right-click on the WinMTR application and select “Run as administrator”.
Type the IP address 137.221.105.2 in the “Host” field.
Click on “Start” and then launch the game. Allow the test to run for at least 10 minutes. Click on “Stop” when you’re done playing after you have experienced the latency or connection issue.
Click on “Copy Text to Clipboard”, paste the results here, then highlight everything and hit the </> button in the posting section so it will allow links.
Wow I have this exact same problem and it’s been driving me nuts. My ISP is Greenlight Networks, I’m located in NY. My WoW latency is absolutely pegged at between 200-205ms for the past week or so. Before that I’d be in the 20-30ms range. I’ve tried everything I can think of, deleted cache, addon, WTF folders, reinstalled wow entirely. Reinstalled network client adapter, factory reset router. Rebooted modem. Updated drivers, router firmware. If I connect to my 4G hotspot and play wow the problem goes away. I have no other latency issues like this elsewhere.
