Dont play on a vpn thats stupid. Its a good way to get hacked much easier and lose your account all together. Just be patient. Yes it sucks, but patience will at least allow you to keep your account yours.
1 Like
I tried posting my traceroute and ping results but kept getting an error message about not being able to post links, and I haven’t been able to figure out how to make the preformatted text button work. So, I removed the ‘t’ from ‘net’ so it no longer appears as a ‘link’. So here are rather lengthy results using looking glass from DC area, using Verizon FIOS:
TRACEROUTE:
traceroute to 108.56.145.166 (108.56.145.166), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.224 ms 2.227 ms 2.229 ms
2 24.105.18.3 (24.105.18.3) 2.231 ms 2.239 ms 2.244 ms
3 137.221.105.12 (137.221.105.12) 1.239 ms 1.521 ms 1.547 ms
4 137.221.66.16 (137.221.66.16) 1.745 ms 1.760 ms 1.763 ms
5 137.221.83.66 (137.221.83.66) 34.305 ms 34.332 ms 34.339 ms
6 137.221.65.68 (137.221.65.68) 6.397 ms 6.394 ms 6.170 ms
7 137.221.68.32 (137.221.68.32) 6.337 ms 6.164 ms 6.159 ms
8 [link to telia redacted] (62.115.178.200) 5.983 ms 6.156 ms 6.291 ms
9 [link to alter redacted] (152.179.21.77) 5.880 ms 5.698 ms 5.679 ms
10 * * *
11 [link to DC Verizon redacted] (130.81.221.225) 62.890 ms 62.912 ms 62.853 ms
12 [DC Verizon FIOS redacted] (108.56.145.166) 69.246 ms 69.267 ms 69.658 ms
PING:
PING 108.56.145.166 (108.56.145.166) 56(84) bytes of data.
64 bytes from 108.56.145.166: icmp_seq=1 ttl=47 time=74.4 ms
64 bytes from 108.56.145.166: icmp_seq=2 ttl=47 time=69.9 ms
64 bytes from 108.56.145.166: icmp_seq=3 ttl=47 time=70.1 ms
64 bytes from 108.56.145.166: icmp_seq=4 ttl=47 time=71.0 ms
— 108.56.145.166 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 69.948/71.417/74.481/1.826 ms
PING:
PING 108.56.145.166 (108.56.145.166) 56(84) bytes of data.
64 bytes from 108.56.145.166: icmp_seq=1 ttl=47 time=67.7 ms
64 bytes from 108.56.145.166: icmp_seq=2 ttl=47 time=67.7 ms
64 bytes from 108.56.145.166: icmp_seq=3 ttl=47 time=68.6 ms
64 bytes from 108.56.145.166: icmp_seq=4 ttl=47 time=69.6 ms
— 108.56.145.166 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 67.756/68.474/69.690/0.819 ms
TRACEROUTE:
traceroute to 108.56.145.166 (108.56.145.166), 15 hops max, 60 byte packets
1 Blizzard Blizzard 4.105 ms 4.234 ms 4.250 ms
2 24.105.18.131 (24.105.18.131) 5.081 ms 5.086 ms 5.112 ms
3 137.221.105.16 (137.221.105.16) 5.037 ms 5.082 ms 5.086 ms
4 137.221.66.18 (137.221.66.18) 4.837 ms 5.260 ms 5.272 ms
5 137.221.83.66 (137.221.83.66) 19.834 ms 19.859 ms 19.865 ms
6 137.221.65.68 (137.221.65.68) 9.505 ms 6.052 ms 6.044 ms
7 137.221.68.32 (137.221.68.32) 6.234 ms 6.365 ms 6.381 ms
8 las-b21-link.telia (62.115.178.200) 5.856 ms 5.833 ms 5.831 ms
9 xe-5-3-2.BR3.LAX15.ALTER.NE (152.179.21.77) 7.909 ms 7.328 ms 7.322 ms
10 * * *
11 ae204-0.WASHDC-VFTTP-313.verizon-gni.ne (130.81.221.227) 65.654 ms 65.496 ms 65.326 ms
12 pool-108-56-145-166.washdc.fios.verizon.ne (108.56.145.166) 69.812 ms 71.988 ms 72.077 ms
19/08/2019 20:59:15 UTC
TRACEROUTE:
traceroute to 108.56.145.166 (108.56.145.166), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.345 ms 0.349 ms 0.355 ms
2 24.105.18.131 (24.105.18.131) 1.047 ms 1.053 ms 1.067 ms
3 137.221.105.16 (137.221.105.16) 1.003 ms 1.044 ms 1.061 ms
4 137.221.66.18 (137.221.66.18) 0.996 ms 1.008 ms 1.014 ms
5 137.221.83.66 (137.221.83.66) 3.379 ms 3.401 ms 3.406 ms
6 137.221.65.68 (137.221.65.68) 227.934 ms 226.701 ms 344.571 ms
7 137.221.68.32 (137.221.68.32) 7.567 ms 7.570 ms 7.574 ms
8 las-b21-link.telia.ne (62.115.178.200) 5.976 ms 5.972 ms 6.144 ms
9 xe-5-3-2.BR3.LAX15.ALTER.NE (152.179.21.77) 5.775 ms 5.799 ms 5.611 ms
10 * * *
11 ae204-0.WASHDC-VFTTP-313.verizon-gni.ne (130.81.221.227) 65.345 ms 64.769 ms 64.741 ms
12 pool-108-56-145-166.washdc.fios.verizon.ne (108.56.145.166) 69.682 ms 69.791 ms 69.919 ms
19/08/2019 20:59:17 UTC
PING:
PING 108.56.145.166 (108.56.145.166) 56(84) bytes of data.
64 bytes from 108.56.145.166: icmp_seq=1 ttl=47 time=71.2 ms
64 bytes from 108.56.145.166: icmp_seq=2 ttl=47 time=71.7 ms
— 108.56.145.166 ping statistics —
4 packets transmitted, 2 received, 50% packet loss, time 2998ms
rtt min/avg/max/mdev = 71.206/71.460/71.715/0.369 ms
19/08/2019 20:59:16 UTC
PING:
PING 108.56.145.166 (108.56.145.166) 56(84) bytes of data.
64 bytes from 108.56.145.166: icmp_seq=1 ttl=47 time=71.0 ms
64 bytes from 108.56.145.166: icmp_seq=2 ttl=47 time=71.0 ms
64 bytes from 108.56.145.166: icmp_seq=3 ttl=47 time=71.9 ms
64 bytes from 108.56.145.166: icmp_seq=4 ttl=47 time=72.2 ms
— 108.56.145.166 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 71.053/71.580/72.249/0.614 ms
19/08/2019 20:59:19 UTC
MTR:
Start: Mon Aug 19 20:59:12 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.12 0.0% 10 0.5 0.8 0.5 2.3 0.3
4.|-- 137.221.66.16 0.0% 10 0.8 1.0 0.8 1.1 0.0
5.|-- 137.221.83.66 0.0% 10 0.8 5.0 0.8 14.5 4.5
6.|-- 137.221.65.68 0.0% 10 5.7 82.3 5.7 501.8 156.5
7.|-- 137.221.68.32 0.0% 10 34.2 12.6 5.9 43.2 13.9
8.|-- las-b21-link.telia.ne 0.0% 10 5.8 6.1 5.5 9.5 1.0
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NE 0.0% 10 5.7 5.7 5.6 6.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.WASHDC-VFTTP-313.verizon-gni.ne 0.0% 10 62.9 63.0 62.8 63.5 0.0
12.|-- pool-108-56-145-166.washdc.fios.verizon.ne 20.0% 10 67.9 69.1 67.9 70.0 0.5
19/08/2019 20:59:12 UTC
MTR:
Start: Mon Aug 19 20:59:13 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 0.5 0.6 0.4 1.1 0.0
3.|-- 137.221.105.12 0.0% 10 0.5 0.6 0.4 0.9 0.0
4.|-- 137.221.66.16 0.0% 10 0.9 1.8 0.9 7.1 1.8
5.|-- 137.221.83.66 0.0% 10 5.2 7.5 4.3 16.3 3.4
6.|-- 137.221.65.68 0.0% 10 5.7 82.1 5.7 555.4 178.6
7.|-- 137.221.68.32 0.0% 10 6.0 7.4 5.8 19.8 4.3
8.|-- las-b21-link.telia.ne 0.0% 10 5.7 5.7 5.5 5.9 0.0
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NE 0.0% 10 5.7 5.7 5.6 6.5 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.WASHDC-VFTTP-313.verizon-gni.ne 0.0% 10 62.9 63.2 62.8 65.4 0.7
12.|-- pool-108-56-145-166.washdc.fios.verizon.ne 20.0% 10 68.6 68.5 66.1 69.8 1.1
19/08/2019 20:59:12 UTC
MTR:
Start: Mon Aug 19 20:59:15 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.7 0.3 2.6 0.6
2.|-- 24.105.18.131 0.0% 10 0.7 0.8 0.6 1.6 0.0
3.|-- 137.221.105.16 0.0% 10 0.7 0.9 0.5 3.6 0.7
4.|-- 137.221.66.18 0.0% 10 0.9 1.5 0.8 3.9 0.9
5.|-- 137.221.83.66 0.0% 10 7.3 5.4 1.2 8.7 2.7
6.|-- 137.221.65.68 0.0% 10 67.8 62.6 5.7 331.8 106.7
7.|-- 137.221.68.32 0.0% 10 5.9 8.6 5.9 30.9 7.8
8.|-- las-b21-link.telia.ne 0.0% 10 5.7 5.8 5.5 6.0 0.0
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NE 0.0% 10 5.7 5.8 5.6 6.6 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae204-0.WASHDC-VFTTP-313.verizon-gni.ne 0.0% 10 64.9 67.2 64.8 81.9 5.3
12.|-- pool-108-56-145-166.washdc.fios.verizon.ne 20.0% 10 70.6 71.0 69.9 71.9 0.4
19/08/2019 20:59:15 UTC
MTR:
Start: Mon Aug 19 20:59:16 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.7 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 1.7 0.5 8.2 2.5
3.|-- 137.221.105.16 0.0% 10 0.5 0.6 0.5 0.7 0.0
4.|-- 137.221.66.18 0.0% 10 0.9 10.0 0.8 52.1 18.5
5.|-- 137.221.83.66 0.0% 10 5.4 5.7 0.9 10.3 2.9
6.|-- 137.221.65.68 0.0% 10 5.7 70.8 5.6 204.0 79.9
7.|-- 137.221.68.32 0.0% 10 13.8 11.9 5.8 36.6 9.8
8.|-- las-b21-link.telia.ne 0.0% 10 5.5 6.0 5.4 8.9 0.8
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NE 0.0% 10 5.7 7.4 5.7 21.4 4.9
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae204-0.WASHDC-VFTTP-313.verizon-gni.ne 0.0% 10 64.8 65.5 64.8 66.7 0.3
12.|-- pool-108-56-145-166.washdc.fios.verizon.ne 20.0% 10 70.8 71.2 70.1 72.1 0.0
19/08/2019 20:59:16 UTC
Passed the authentication boss, but the load screen boss still stands as I’m stuck at 90% 
1 Like
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 19 ms 19 ms 18 ms tukw-dsl-gw76.tukw.qwest.net [63.231.10.76]
3 19 ms 20 ms 19 ms tukw-agw1.inet.qwest.net [63.226.198.89]
4 20 ms 21 ms 20 ms sea-brdr-03.inet.qwest.net [67.14.41.150]
5 * * * Request timed out.
6 23 ms 20 ms 20 ms ae-1-3513.edge1.Seattle3.Level3.net [4.69.160.69]
7 20 ms 21 ms 20 ms BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146]
8 * * * Request timed out.
9 * 69 ms * xe-0-0-1-1-br02-eqch2.as57976.net [137.221.65.42]
10 70 ms 69 ms 69 ms be2-pe01-eqch2.as57976.net [137.221.69.71]
11 70 ms 69 ms 69 ms 24.105.62.129
Trace complete.Centurylink is my ISP. Replaced “.” with “-” so I could post this.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms ptld-dsl-gw50-ptld-qwest-net [207.225.84.50]
3 3 ms 2 ms 2 ms ptld-agw1-inet-qwest-net [207.225.86.137]
4 3 ms 2 ms 2 ms 209-180-169-2-ptld-qwest-net [209.180.169.2]
5 6 ms 6 ms 6 ms ae-1-3513-edge1-Seattle3-Level3-net [4.69.160.69]
6 7 ms 7 ms 7 ms BLIZZARD-EN-edge1-Seattle3-Level3-net [4.59.232.146]
7 28 ms 28 ms 28 ms ae1-br01-eqse2-as57976-net [137.221.73.33]
8 28 ms 28 ms 28 ms xe-0-0-0-1-br01-eqsv5-as57976-net [137.221.65.40]
9 28 ms 27 ms 28 ms et-0-0-29-br02-eqsv5-as57976-net [137.221.65.117]
10 28 ms 28 ms 28 ms xe-0-0-1-1-br02-eqla1-as57976-net [137.221.65.6]
11 28 ms 28 ms 27 ms be2-pe01-eqla1-as57976-net [137.221.68.71]
12 28 ms 28 ms 28 ms 24.105.30.129
Trace complete.
1 Like
Still down in Pacific Northwest. Olympia Washington.
1 Like
Ugh. Just Ugh
1 Like
I have been trying to log on for over 6 hrs and have the same provider.
1 Like
wanted to get the last of my raid runs done. Figure today would be the day ICC drops the mount I won’t get. I really need to stop running raids on last day before reset.
1 Like
Read the hundreds of posts regarding a problem they are working on… its been off all day.
Tracing route to xx.domain [198.105.244.23]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms modem.domain [192.168.0.1]
2 8 ms 8 ms 8 ms stpl-dsl-gw11.stpl.qwest [207.109.2.11]
3 8 ms 8 ms 8 ms stpl-agw1.inet.qwest [207.109.3.81]
4 17 ms 17 ms 18 ms chp-brdr-03.inet.qwest [67.14.8.194]
5 17 ms 17 ms 17 ms 63.146.26.170
6 35 ms 35 ms 35 ms 100ge16-1.core1.nyc4.he [184.105.223.162]
7 35 ms 35 ms 52 ms xerocole-inc.10gigabitethernet12-4.core1.nyc4.he[216.66.41.242]
8 *
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 8 ms 7 ms 7 ms 24.105.62.129
Trace complete.
Hey all,
Just to provide some more information and a work around, we’ve identified that this is an ISP issue and we’re doing everything we can on our end to fix it. Because it is an ISP issue rather than a server issue, most players can connect using a VPN client (or mobile hotspot/tether). We can’t recommend any or support this directly because they can cause other connection errors of their own, but if you’re itching to get in ASAP, there are plenty out there you can try.
Thanks for all the tests and reports so far, either way!
3 Likes
How do you figure that a VPN makes you less secure?
Try using wow companion app through phone without wifi - using phone provider see if you can connect and switch characters - once you go through your list log out completely then try the game using your wifi client.
Then why, the time I actually managed to log in, was the game missing all my battle pets?
Oh and after a PTR copy the pets were missing there too …
And on a quick check just now I made it to the character selection screen (ie I reached the realm server allegedly) and no characters were listed …
This is clearly not a routing problem (at least not an external routing problem) …
2 Likes
$hit i know this, blizz gonna have to give us all a day of game time back, at least update your breaking news alert saying the game is offline today and tomorrow instead of just tomorrow.
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 22 ms 22 ms 22 ms tukw-dsl-gw76.tukw.qwest
[63.231.10.76]
3 22 ms 59 ms 22 ms tukw-agw1.inet.qwest
[63.226.198.89]
4 22 ms 23 ms 22 ms sea-brdr-03.inet.qwest
[67.14.41.150]
5 * * * Request timed out.
6 23 ms 23 ms 22 ms ae-1-3513.edge1.Seattle3.Level3 [4.69.160.69]
7 23 ms 23 ms 23 ms BLIZZARD-EN.edge1.Seattle3.Level3 [4.59.232.146]
8 55 ms 56 ms 56 ms ae1-br01-eqse2.as57976
[137.221.73.33]
9 56 ms 56 ms 56 ms xe-0-0-0-1-br01-eqsv5.as57976 [137.221.65.40]
10 56 ms 57 ms 56 ms et-0-0-29-br02-eqsv5.as57976 [137.221.65.117]
11 128 ms 220 ms 218 ms xe-0-0-1-1-br02-eqla1.as57976 [137.221.65.6]
12 3829 ms 1099 ms 219 ms et-0-0-29-br01-eqla1.as57976 [137.221.65.0]
13 80 ms 56 ms 57 ms et-0-0-2-br01-swlv10.as57976
[137.221.65.69]
14 58 ms 56 ms 56 ms et-0-0-31-pe02-swlv10.as57976
[137.221.83.69]
15 56 ms 56 ms 55 ms 137.221.105.2
I am having same problem, I was just looking forward to my limited few hours of play after work…they should at least do a free day, I know its not much but really…
TRACEROUTE:
traceroute to 74.104.119.23 (74.104.119.23), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.735 ms 0.766 ms 0.772 ms
2 24.105.18.131 (24.105.18.131) 8.436 ms 8.465 ms 8.479 ms
3 137.221.105.12 (137.221.105.12) 8.474 ms 8.483 ms 8.486 ms
4 137.221.66.16 (137.221.66.16) 31.909 ms 31.949 ms 31.958 ms
5 137.221.83.66 (137.221.83.66) 31.205 ms 31.246 ms 31.387 ms
6 137.221.65.68 (137.221.65.68) 8.414 ms 6.038 ms 6.034 ms
7 137.221.68.32 (137.221.68.32) 7.647 ms 7.103 ms 7.114 ms
8 las-b21-link.telia .net (62.115.178.200) 5.843 ms 6.225 ms 6.229 ms
9 xe-5-3-2.BR3.LAX15.ALTER .NET (152.179.21.77) 6.246 ms 6.244 ms 5.519 ms
10 * * *
11 ae203-0.BSTNMA-VFTTP-335.verizon-gni .net (100.41.0.111) 66.728 ms 66.735 ms 66.739 ms
12 pool-74-104-119-23.bstnma.fios.verizon .net (74.104.119.23) 73.206 ms 73.230 ms 73.315 ms