Played all day yesterday with no issues using a VPN set to Sweden. Today, forgetting to start the VPN, the first loading screen freezes and I have to Alt+F4. People shouldn’t have to buy a VPN service to play this game. And someone from Blizzard needs to respond to this thread, because this issue is still unresolved.
1 Like
someone said further up in the thread they tagged them on twitter and got a response. they are aware and investigating but have no ETA. a formal response on this thread would still be appriciated though.
Just got my first frozen screen of the day after playing for about 4-5 hours.
Howdy!
We have taken steps to help resolve this issue! Can you please retest and let us know if things have improved?
Thank you!
4 Likes
EDIT: ^^^ Guess I was a bit slow there… 
I got a reply from Blizzard about an hour ago:
“…
Thanks for reporting your loading issue in-game, we’ve been looking into other reports and are investigating into an issue with connections reaching our realms from your country. That looks to be happening on diferent ISPs so seems to be a connection routing issue.
…”
I guess they’re onto it 
I think blizzard should give us all free VPN so we can play their game
1 Like
is this resolved now monday 16:00???
I’m actually getting frozen every single screen now, Iogging in is hard too and I often get a black screen in the character select. Worst it’s ever been right now.
1 Like
Hello,
I started testing WoW Retail without VPN again about 16.40 (appr. 15 minutes ago). I started with logging off Bnet client, and exit completely. Then started Bnet and logon. Then start WoW.
At first I could log on a character and did about 12 portals (Valdrakken ↔ Stormwind) before loading screen freeze.
At that point I had to Alt-F4. I re-launched WoW immediately and tried entering with a character but could never get in. Alt-F4. I then exited Bnet, and restarted Bnet. Started WoW.
I then logged on to a different character, did 3 portals, back to character selection and selected a different character. Did about 6 portals (Valdrakken ↔ Stormwind) before loading screen freeze.
So to summarize: In the last 15 minutes during testing, 3 loading screen freeze.
Login attempts start at 16:50. Reaching character screen consistently (not the case before):
Character 1 (Emerald Dream):
1st - Disconnect at abt 75%
2nd - Stuck at 100% (some in-game-sounds)
3rd - Successful after 45 sec
Char 2 (Valdrakken):
1st - Succesfull after 25 sec
Char 1 again (Emerald Dream)
1st - Successful after 30 sec
Char 3 (Orgrimmar)
1st - Successfull after 20 sec
Seems about fixed. Some hickup at the start, dunno if it needed a successfull login to go through or what caused it. Will report back if it reappears
Edit: 18:10
Char 1 - Loading into Emerald Dream, stuck at abt. 60%
Still happening on my end, both getting stuck on loading screens, as well as getting disconnected when changing zones such as changing between Valdrakken ↔ Thaldraszus
No change in status. Still ongoing issues
Easier way to reproduce these connection issues is flying between valdrakken and the open world, doing it a few times always gets you disconnected without actually disconnecting your account right away, you’ll notice youre no longer connected due to no NPCs respawning when you enter valdrakken again as well as vigor stops regenerating.
Hi all, thanks for the updates on this we’re still monitoring this situation.
For those of you still affected can you please post a traceroute here for your connection without a VPN being used, so we can gather those for looking into this further.
3 Likes
Issue also causes various hangs and other issues in D4, opening menus, map, etc flat out causes the game to lock up, either recovering or entering a “disconnected state where its stuck on reconnecting” after multiple minutes.
Non VPN Tracert:
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.0.1
2 4 ms 4 ms 4 ms 126.79-160-116.customer.lyse.net [79.160.116.126]
3 5 ms 4 ms 4 ms 15.213-167-114.customer.lyse.net [213.167.114.15]
4 * 15 ms 15 ms ae71.edge7.London1.Level3.net [217.163.134.165]
5 23 ms 22 ms 22 ms ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
6 22 ms 22 ms 22 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
7 25 ms 25 ms 25 ms 137.221.78.27
8 25 ms 38 ms 25 ms 137.221.65.75
9 25 ms 25 ms 25 ms 137.221.78.47
10 25 ms 25 ms 25 ms 185.60.112.157
I have the same issue, each of my 11 lvl 70 chars has the same problem, deleted all addons without resolving the issue, renamed the wtf… and so on files.
1 Like
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.1
2 5 ms 5 ms 4 ms 188.79-160-116.customer.lyse.net [79.160.116.188]
3 5 ms 4 ms 4 ms 15.213-167-114.customer.lyse.net [213.167.114.15]
4 16 ms 17 ms 16 ms ae71.edge7.London1.Level3.net [217.163.134.165]
5 23 ms 23 ms 25 ms ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
6 34 ms 23 ms 71 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
7 26 ms 26 ms 27 ms 137.221.78.27
8 26 ms 26 ms 234 ms 137.221.65.75
9 26 ms 26 ms 26 ms 137.221.78.49
10 26 ms 26 ms 26 ms 137.221.66.43
11 27 ms 27 ms 26 ms 185.60.112.157
Trace complete.
Tracing route to 185.60.112.158 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.1
2 4 ms 4 ms 6 ms 188.79-160-116.customer.lyse.net [79.160.116.188]
3 5 ms 5 ms 5 ms 15.213-167-114.customer.lyse.net [213.167.114.15]
4 21 ms 16 ms 21 ms ae71.edge7.London1.Level3.net [217.163.134.165]
5 47 ms * 30 ms ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
6 24 ms 23 ms 23 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
7 26 ms 26 ms 34 ms 137.221.78.27
8 * * * Request timed out.
9 26 ms 26 ms 26 ms et-0-0-31-pe02-eqam1.as57976.net [137.221.78.69]
10 26 ms 26 ms 26 ms 185.60.112.158
Trace complete.
Tracing route to 185.60.114.159 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.1
2 4 ms 4 ms 4 ms 188.79-160-116.customer.lyse.net [79.160.116.188]
3 5 ms 5 ms 5 ms 15.213-167-114.customer.lyse.net [213.167.114.15]
4 32 ms 23 ms 16 ms ae71.edge7.London1.Level3.net [217.163.134.165]
5 23 ms 23 ms 23 ms ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
6 23 ms 23 ms 23 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
7 * * * Request timed out.
8 28 ms 28 ms 27 ms et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92]
9 28 ms 27 ms 27 ms et-0-0-1-pe04-eqpa4.as57976.net [137.221.77.53]
10 28 ms 28 ms 28 ms 137.221.66.39
11 28 ms 28 ms 27 ms 185.60.114.159
Trace complete.
Tracing route to 185.60.114.159 over a maximum of 30 hops
1 1 ms 1 ms 1 ms router [192.168.10.1]
2 5 ms 5 ms 7 ms 238.79-160-116.customer.lyse.-net [79.160.116.238]
3 6 ms 5 ms 5 ms 219.213-167-114.customer.lyse.-net [213.167.114.219]
4 6 ms 5 ms 5 ms oso-b1-link.ip.twelve99.-net [62.115.12.214]
5 17 ms 17 ms 17 ms hbg-bb3-link.ip.twelve99.-net [62.115.112.84]
6 24 ms 23 ms 23 ms adm-bb1-link.ip.twelve99.-net [80.91.252.42]
7 24 ms 23 ms 23 ms adm-b10-link.ip.twelve99.-net [62.115.120.227]
8 24 ms 23 ms 24 ms blizzard-ic-348623.ip.twelve99-cust.-net [62.115.178.203]
9 1243 ms 659 ms 219 ms ae1-br02-eqam1.as57976.-net [137.221.78.35]
10 43 ms 38 ms 31 ms et-0-0-3-br02-eqpa4.as57976.-net [137.221.65.92]
11 31 ms 31 ms 31 ms et-0-0-1-pe04-eqpa4.as57976.-net [137.221.77.53]
12 32 ms 31 ms 31 ms 137.221.66.39
13 32 ms 32 ms 31 ms 185.60.114.159
Trace complete.
Tracing route to 185.60.112.158 over a maximum of 30 hops
1 1 ms 1 ms 1 ms router [192.168.10.1]
2 7 ms 5 ms 5 ms 238.79-160-116.customer.lyse.-net [79.160.116.238]
3 6 ms 5 ms 5 ms 219.213-167-114.customer.lyse.-net [213.167.114.219]
4 5 ms 5 ms 5 ms oso-b1-link.ip.twelve99.-net [62.115.54.185]
5 17 ms * 17 ms hbg-bb3-link.ip.twelve99.-net [62.115.112.84]
6 24 ms 24 ms 23 ms adm-bb1-link.ip.twelve99.-net [80.91.252.42]
7 24 ms 23 ms 23 ms adm-b10-link.ip.twelve99.-net [62.115.120.227]
8 24 ms 23 ms 24 ms blizzard-ic-348623.ip.twelve99-cust.-net [62.115.178.203]
9 57 ms 69 ms 24 ms ae1-br01-eqam1.as57976.-net [137.221.78.33]
10 * * * Request timed out.
11 24 ms 31 ms 23 ms 137.221.78.55
12 23 ms 23 ms 23 ms 137.221.66.41
13 24 ms 23 ms 24 ms 185.60.112.158
Trace complete.
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 1 ms 1 ms 1 ms router [192.168.10.1]
2 6 ms 5 ms 6 ms 238.79-160-116.customer.lyse.-net [79.160.116.238]
3 5 ms 5 ms 5 ms 219.213-167-114.customer.lyse.-net [213.167.114.219]
4 5 ms 5 ms 5 ms oso-b1-link.ip.twelve99.-net [213.248.77.48]
5 17 ms 17 ms 17 ms hbg-bb3-link.ip.twelve99.-net [62.115.112.84]
6 23 ms 23 ms 23 ms adm-bb1-link.ip.twelve99.-net [80.91.252.42]
7 24 ms 23 ms 23 ms adm-b10-link.ip.twelve99.-net [62.115.120.227]
8 24 ms 24 ms 24 ms blizzard-ic-348623.ip.twelve99-cust.-net [62.115.178.203]
9 255 ms 219 ms 246 ms ae1-br02-eqam1.as57976.-net [137.221.78.35]
10 24 ms 24 ms 26 ms et-0-0-5-br01-eqam3.blizzardonline.-net [137.221.65.159]
11 23 ms 23 ms 23 ms 137.221.78.49
12 23 ms 23 ms 23 ms 137.221.66.43
13 23 ms 22 ms 23 ms 185.60.112.157
Trace complete.
Added - before net because forum wont accept links.
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 * 3 ms 4 ms 192.168.86.1
2 4 ms 3 ms 4 ms 192.168.10.1
3 7 ms 6 ms 3 ms 246.79-160-116.customer.lyse.net [79.160.116.246]
4 7 ms 5 ms 5 ms 217.213-167-114.customer.lyse.net [213.167.114.217]
5 6 ms 4 ms 10 ms ae65.edge1.Oslo2.Level3.net [62.67.17.221]
6 41 ms 33 ms 31 ms ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
7 35 ms 37 ms 36 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
8 94 ms 230 ms 207 ms 137.221.78.27
9 * * * Request timed out.
10 30 ms 30 ms 29 ms 137.221.78.53
11 31 ms 30 ms 29 ms 137.221.66.47
12 31 ms 30 ms 31 ms 185.60.112.157
Trace complete.
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 5 ms 2 ms <1 ms 192.168.86.1
2 4 ms 2 ms 3 ms 8.79-160-116.customer.lyse.net [79.160.116.8]
3 3 ms 4 ms 2 ms 219.213-167-114.customer.lyse.net [213.167.114.219]
4 2 ms 2 ms 4 ms oso-b1-link.ip.twelve99.net [213.248.77.48]
5 * 15 ms * hbg-bb3-link.ip.twelve99.net [62.115.112.84]
6 21 ms 21 ms 22 ms adm-bb1-link.ip.twelve99.net [80.91.252.42]
7 22 ms 22 ms 21 ms adm-b10-link.ip.twelve99.net [62.115.120.227]
8 22 ms 20 ms 22 ms blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
9 21 ms 20 ms 20 ms ae1-br01-eqam1.as57976.net [137.221.78.33]
10 * * * Request timed out.
11 22 ms 21 ms 21 ms 137.221.78.55
12 21 ms 20 ms 22 ms