got in, did 2 quests now game is stuck…
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 2 ms 2 ms 2 ms 192.168.1.1
2 5 ms 2 ms 2 ms 112.208.128.1.pldt.net [112.208.128.1]
3 5 ms 2 ms 2 ms 122.2.206.58.static.pldt.net [122.2.206.58]
4 10 ms 6 ms 3 ms 210.213.130.118.static.pldt.net [210.213.130.118]
5 14 ms 5 ms 3 ms 210.213.128.133.static.pldt.net [210.213.128.133]
6 6 ms 4 ms 2 ms 210.213.131.81.static.pldt.net [210.213.131.81]
7 71 ms 50 ms 48 ms 210.173.176.98
8 224 ms 195 ms 195 ms et-0-0-48-br01-eqty2.blizzardonline.net [137.221.81.33]
9 * * * Request timed out.
10 190 ms 192 ms 191 ms et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
11 191 ms 192 ms 192 ms 137.221.65.133
12 193 ms 192 ms 193 ms be1-pe01-eqch2.as57976.net [137.221.69.67]
13 193 ms 193 ms 192 ms chi-eqch2-ia-bons-02.as57976.net [137.221.66.11]
14 194 ms 191 ms 195 ms 24.105.62.129
Trace complete.
Location: Philippines
ISP PLDT Fibr 15mbps
Issues: able to login and play in world maps no response when zoning into instances.
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 2 ms 3 ms 3 ms 24.105.62.129
Trace complete.
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 2 ms 3 ms 3 ms 24.105.62.129
Trace complete.
Problems started after a rather large windows update
Windows update KB4512508
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms 1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 2 ms 5 ms 6 ms 24.105.62.129
Trace complete.
Blizzard says they’re still looking into this on twitter.
Have you tried turning WoW off then on again or resseting the WoW realms?
I got in with VPN but no go on anything else. This does not appear to be an ISP issue, this is a blizzard issue. I have 3 separate internet providers, and no matter which I switch my network to they all have the same issue. I wish Blizzard would let us know what they are working on, my assumption is that something went sideways, either a hack or code update. All we can do is wait for them to resolve the issue, but a little communication goes a long way. Second, time to go outside lol 
When is the last time we heard from a BLUE poster, I’ve seen the volunteer green poster which is very nice but not the same. Blizz, we aren’t shareholders but don’t leave us in the dark and high and dry, we’re just your loyal fan base… that’s all…
As someone mentioned here free ProtonVPN service WORKS. Idk how long this might take to get fixed last time it happened took around a week so i might as well get the paid ProtonVPN for like 5 bucks and forget about this.
1 3 ms 2 ms 2 ms 192.168.2.1
2 14 ms 8 ms 8 ms loop0.57w.ba09.stjh.nf.aliant.net [142.163.63.12]
3 11 ms 9 ms 8 ms be14-181.dr01.stjh.nf.aliant.net [142.176.208.57]
4 17 ms 25 ms 23 ms be1.dr01.crbk.nf.aliant.net [142.166.149.126]
5 18 ms 18 ms 19 ms ae3-50.dr02.crbk.nf.aliant.net [142.166.181.54]
6 26 ms 27 ms 28 ms et-0-3-0.cr02.hlfx.ns.aliant.net [142.166.181.113]
7 24 ms 30 ms 28 ms hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net [142.166.149.93]
8 40 ms 48 ms 48 ms be19.bx01.nycm.ny.aliant.net [207.231.227.110]
9 40 ms 48 ms 49 ms lag-197.ear3.NewYork1.Level3.net [4.71.230.101]
10 45 ms 48 ms 49 ms 4.69.216.226
11 43 ms 54 ms 43 ms BLIZZARD-EN.ear1.NewYork5.Level3.net [4.35.72.34]
12 146 ms 176 ms 151 ms ae1-br01-eqny8.as57976.net [137.221.71.33]
13 119 ms 129 ms 128 ms et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
14 125 ms 127 ms 127 ms et-0-0-29-br01-eqch2.as57976.net [137.221.65.2]
15 124 ms 127 ms 117 ms 137.221.65.132
16 105 ms 108 ms 107 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
17 124 ms 127 ms 127 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
18 123 ms 127 ms 127 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
19 130 ms 222 ms 127 ms 24.105.30.129was trying to run a dungeon now i’m stuck in the load screen lol
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms
2 1 ms <1 ms <1 ms
3 3 ms 4 ms 3 ms
4 3 ms 3 ms 3 ms
5 14 ms 11 ms 15 ms
6 * * * Request timed out.
7 4 ms 4 ms 4 ms
8 5 ms 29 ms 4 ms
9 37 ms 55 ms 37 ms
10 37 ms 37 ms 37 ms
11 37 ms 37 ms 37 ms
12 242 ms 219 ms 219 ms
13 37 ms 37 ms 37 ms
14 37 ms 37 ms 37 ms
15 37 ms 37 ms 37 ms
16 37 ms 37 ms 37 ms
17 37 ms 37 ms 37 ms 137.221.105.2
Trace complete.
Damn I hate to say this but I’m glad to see it’s not just me. Thought it was my internet or something else that’d force me to re-install. Cleared my cache though just to see if that could possibly be related in any way.
I get error code wow51900329 when trying to log in. I can’t get past the login screen and if I do the character screen won’t show my characters, if I go to “select server” at the top of the character select screen it lets me know I’ve been disconnected and gives me that error.
2 Likes
I just got into the game but nothing works
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 2 ms <1 ms <1 ms amplifi.lan [192.168.213.1]
2 2 ms 2 ms 2 ms 104-232-95-129.in-addr.arpa [104.232.95.129]
3 2 ms 2 ms 2 ms 10.0.0.6
4 2 ms 2 ms 2 ms 10.0.126.253
5 13 ms 12 ms 12 ms 5-2-2.bear2.Sacramento1.Level3.net [4.53.42.13]
6 * * * Request timed out.
7 25 ms 26 ms 25 ms BLIZZARD-EN.ear3.LosAngeles1.Level3.net [4.71.135.106]
8 25 ms 26 ms 50 ms ae1-br01-eqla1.as57976.net [137.221.68.33]
9 26 ms 25 ms 25 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
10 26 ms 26 ms 26 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
11 25 ms 25 ms 26 ms 24.105.30.129
Trace complete.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 34 ms <1 ms <1 ms amplifi.lan [192.168.213.1]
2 2 ms 2 ms 2 ms 104-232-95-129.in-addr.arpa [104.232.95.129]
3 2 ms 2 ms 2 ms 10.0.0.6
4 2 ms 2 ms 2 ms 10.0.126.253
5 12 ms 12 ms 12 ms 5-2-2.bear2.Sacramento1.Level3.net [4.53.42.13]
6 * * * Request timed out.
7 26 ms 25 ms 25 ms BLIZZARD-EN.ear3.LosAngeles1.Level3.net [4.71.135.106]
8 58 ms 58 ms 58 ms ae1-br01-eqla1.as57976.net [137.221.68.33]
9 * * * Request timed out.
10 59 ms * * 137.221.65.133
11 58 ms 58 ms 58 ms be1-pe01-eqch2.as57976.net [137.221.69.67]
12 60 ms 58 ms 59 ms 24.105.62.129
Trace complete.
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 34 ms <1 ms <1 ms amplifi.lan [192.168.213.1]
2 2 ms 2 ms 2 ms 104-232-95-129.in-addr.arpa [104.232.95.129]
3 2 ms 2 ms 2 ms 10.0.0.6
4 2 ms 2 ms 2 ms 10.0.126.253
5 12 ms 12 ms 12 ms 5-2-2.bear2.Sacramento1.Level3.net [4.53.42.13]
6 * * * Request timed out.
7 26 ms 26 ms 26 ms BLIZZARD-EN.ear3.LosAngeles1.Level3.net [4.71.135.106]
8 30 ms 30 ms 30 ms ae1-br01-eqla1.as57976.net [137.221.68.33]
9 31 ms 31 ms 31 ms et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
10 31 ms 31 ms 30 ms et-0-0-31-pe02-swlv10.as57976.net [137.221.83.69]
11 30 ms 30 ms 30 ms las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
12 32 ms 30 ms 29 ms 137.221.105.2
Trace complete.im still having trouble getting in 
Far from alone, they dont let you share links here but you can check out downdetector dot com slash status slash world-of-warcraft slash map slash
the outage map shows a major issue in the Northeast as well as Florida and Southern Brazil and Argentina
Damn intern almost got caught looking at p*rn at work, shut the computer off and screwed us all.
Confirmed ISP issue - Verizon FiOS in Philly suburbs. Turned on VPN and problems went away immediately.
Its not a blue but its still blizzard official.