We appreciate all the reports thus far. We’ve opened an internal ticket on our end to see if there’s anything we can do to help. We can’t currently promise anything, since we’re not sure where the failure is and we only have so much power over ISP connections, so keep in mind that the message Kershew sent is still the best wisdom for this problem. Please use a VPN or alternate network such as a Mobile Hotspot to connect for now, and contact your ISP to let them know about the problem. They should be able to work with us to fix any peering issues.
For some further clarification, this appears to be affecting players in the northwestern US (Washington, Oregon, California) - on any ISP that uses Wave Broadband nodes to reach us. There are a number of smaller ISPs which are having the issue.
We don’t consider alternate connections a fix, just a work around, but either your ISP or we should be able to get whatever peering issue is causing this fixed. We appreciate your patience in the mean time.
Please note: You should avoid all types of ranked gameplay while this issue is being worked on. We do not reimburse rating or remove leaver debuffs for connectivity issues.
I started having this issue yesterday, and I’m also a Wave customer in the Sacramento area. My connectivity issues seem to occur when I try to do anything instanced (particularly rated PVP). I either get stuck at the loading screen, or I zone in but am unable to take any actions with my character (buff/heal teammates) without 15-20s of delay. I then get stuck in the BG/arena until it closes, at which point I disconnect. If I’m getting routed through Amsterdam in these situations, as others have indicated, that makes sense. I’ll give the VPN workaround a try.
Seeing the same issue here with WoW & Overwatch - this forum post over on Overwatch has a bluepost that there is an internal ticket looking @ the network issue :
It wont let me include my trace, but no issues here. Wave gigabit on camano island.
C:\Users\Tom>tracert 24.105.62.129
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1 2 12 ms 10 ms 12 ms 172.92.240.1 3 8 ms 9 ms 11 ms 174.127.182.6 4 12 ms 11 ms 10 ms be3.cr1-lghe-b.bb.as11404.net [174.127.150.66] 5 8 ms 9 ms 10 ms be19.cr1-lghe-b.bb.as11404.net [174.127.151.109] 6 13 ms 11 ms 11 ms hu0-6-0-21-0.cr1-bds.bb.as11404.net [174.127.148.164] 7 11 ms 11 ms 12 ms hu0-5-0-20-0.cr2-sea-b.bb.as11404.net [174.127.148.136] 8 12 ms 12 ms 12 ms six.blizzardonline.net [206.81.81.122] 9 56 ms 57 ms 57 ms ae1-br02-eqse2.as57976.net [137.221.73.35] 10 * * * Request timed out. 11 57 ms 55 ms 55 ms et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51] 12 59 ms 66 ms * 24.105.62.129 13 * 57 ms 59 ms 24.105.62.129
game isnt working. sticks on logging in to server screen then after about 10 minutes it goes into character screen but its a black screen. Ive read in forums that if you have WAVE internet its them but thats weird because wow has worked in the past.
Hi All, just confirming I had the same issue on th 13AUG and 14AUG. Cant get past the blue bar after charater log in.
Seattle WaveG.
As of 14AUG 6pm I was able to create a new character, and log into the world. Then I was able to log into my main on Stormrage.
I did enable IPV6 on my router, windows network adapter, and on the wow client. not sure if that helped though (seems unlikely after reading this thread). After submitting a ticket I was referred to this thread, so hopefully it is able to get resolved.
This is EXACTLY What I’m seeing as of 13-Aug… it’s blowing up between two of Blizzard’s servers.
Blockquote
TRACEROUTE:
traceroute to 24.113.175.250 (24.113.175.250), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.486 ms 0.476 ms 0.475 ms
2 24.105.18.130 (24.105.18.130) 1.251 ms 1.260 ms 1.255 ms
3 137.221.105.10 (137.221.105.10) 1.246 ms 1.247 ms 1.261 ms
4 137.221.66.20 (137.221.66.20) 0.600 ms 0.615 ms 0.615 ms
5 137.221.83.84 (137.221.83.84) 892.093 ms 892.132 ms 892.154 ms ← Bad Hop
6 * * *
7 137.221.65.1 (137.221.65.1) 65.834 ms 65.843 ms 65.840 ms
8 137.221.65.7 (137.221.65.7) 12.668 ms 12.983 ms 12.968 ms
9 137.221.70.34 (137.221.70.34) 13.079 ms 12.908 ms 12.909 ms
10 as11404.sfmix.org (206.197.187.21) 14.277 ms 15.015 ms 14.101 ms
11 192.175.30.253 (192.175.30.253) 14.626 ms 14.539 ms 13.996 ms
12 * * *
13 be1.cr1-sanmat-b.bb.as11404.net (192.175.30.125) 16.757 ms 16.581 ms 16.572 ms
14 be11.cr2-529bryant.bb.as11404.net (192.175.29.160) 14.992 ms 14.342 ms 14.326 ms
15 cr1-529bryant-be12.bb.as11404.net (192.175.30.55) 14.015 ms 14.186 ms 14.210 ms
15/08/2021 04:31:29 UTC
I looked up IP locations with https://whois.domaintools.com/
137.221.66.20 is a Blizzard server in Las Vegas just before the problem server.
137.221.83.84 is a Blizzard server in Las Vegas that is apparently the issue (+1000 msec).
137.221.65.1 is a Blizzard server in New York that might be part of the problem (+60 msec).
All the other 137.221.x.y Blizzard servers are are <20 msec, but .83.84 and .65.1are both high latency within Blizzard’s server set. I’m Wave broadband in WA state, but why does the MTR show a problem on Blizzard’s side that only affects Wave?! The MTR shows that Blizz server .65.68 is dropping 90% of packets with like a 15-sec delay (not msec).
Edit: The basic VPN included with my anti-virus seems to do the trick although it bumps by “normal” ping from 50 home/25 world to 125/125. Still better than not being able to play with my raid group on Duskwood (I have no issues with the VPN off playing on Proudmoore and queued instances unless I try to group with people from Duskwood).
Hello! Adding my voice to the mix - Nothing new to report, just adding my details in hopes of helping Blizzard prioritize the issue as requested in their response to my ticket.
I’m in the Seattle area, using WaveG, issues started yesterday with extreme lag in Korthia/Maw/Oribos and slightly less extreme lag in other Shadowlands zones. Used the “stuck character” service to move my main to Westfall, tried repairing the game, refreshing DNS, etc., but obviously none of that helped. Now I can’t log in to the game at all (stuck on “Logging in to game server”) unless I tether my phone.
I did contact WaveG and spent some time mystifying their support team (“What’s Blizzard?” mhmm). They added the note about the peering issue to my account. Maybe if enough of us do that it will have an effect… hope springs eternal.
Point your techs towards these three servers within Blizzard’s domains…
137.221.83.84 is a Blizzard server in Las Vegas that is apparently the issue-1 (+1000 msec).
137.221.65.1 is a Blizzard server in New York that might be part of the problem (+60 msec).
137.221.65.68 is a Blizzard server in New York that is apparently the issue-2 (+15 sec, not msec).
I’m in the Portland Metro area. I was able to play with no issues on Friday. On Saturday, I wasn’t able to log any characters in. The loading screen would get to about 90% then hang. Today, it takes a very long time to log into the game server. The character select screen stays black.
I am able to log into the Classic servers with no issues.
Blizzard has a web-based MTR tool called Looking Glass that doesn’t require you to download anything and lets you identify your specific server (not just a regional gateway). I would recommend using that over WinMTR.
We’re getting some positive reports from players using this work around, so I’m quoting it for visibility. If it doesn’t work, please check the post here.
I’ve been able to reconnect and play both OW and WoW at the moment with my normal latency. Seems the issue may have been fixed, anyone else able to get back on as well?
Edit: Thank you Blizz for reaching out on our behalf to Wave as well to help expedite the issue!