8/19 - Stuck at Logging in to game server

Used a private VPN from a work office a couple cities over, but in the same state (WA), and it worked. Here’s a tracert from that:

1 * * * Request timed out.
2 * * * Request timed out.
3 12 ms 15 ms 11 ms ae9—0.car01.evrt.wa.frontiernet. net [74.40.70.61]
4 13 ms 12 ms 13 ms ae3—0.cor02.sttl.wa.frontiernet. net [74.40.1.101]
5 11 ms 15 ms 10 ms ae1—0.cbr01.sttl.wa.frontiernet. net [74.40.5.126]
6 12 ms 11 ms 12 ms eqix-se2.blizzardentertainment. com [198.32.134.68]
7 59 ms 78 ms 59 ms ae1-br02-eqse2.as57976. net [137.221.73.35]
8 57 ms 56 ms 57 ms xe-0-0-1-1-br02-eqch2.as57976. net [137.221.65.42]
9 58 ms 58 ms 57 ms be2-pe02-eqch2.as57976. net [137.221.69.73]
10 61 ms 61 ms 61 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
11 59 ms 63 ms 59 ms 24.105.62.129

Alternatively, here was the tracert again from my other office:

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 3 ms 3 ms 4 ms [redacted]
2 2 ms 3 ms 2 ms [redacted]
3 4 ms 6 ms 6 ms sea-brdr-03.inet.qwest. net [67.14.41.150]
4 6 ms 6 ms 4 ms 4.68.75.121
5 5 ms 4 ms 6 ms ae-2-3613.edge1.seattle3.level3. net [4.69.160.73]
6 5 ms 6 ms 4 ms blizzard-en.edge1.seattle3.level3. net [4.59.232.146]
7 * * * Request timed out.
8 * * 52 ms xe-0-0-1-1-br02-eqch2.as57976. net [137.221.65.42]
9 53 ms 51 ms 52 ms be2-pe02-eqch2.as57976. net [137.221.69.73]
10 54 ms 53 ms 53 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
11 53 ms 54 ms 56 ms 24.105.62.129

Edit: There are a lot of tracert’s that involve Level3 - worth investigating. Seattle router uses CenturyLink and routes through the Level3 Blizzard server, Bellevue router (via VPN to that office) uses Frontier and does not go through Level3. In searching the posts on here, hundreds appear to be routing through Level3. Not all of them, but a large chunk.

1 Like
traceroute to 24.105.62.129 (24.105.62.129), 64 hops max, 52 byte packets
1  192.168.1.1 (192.168.1.1)  1.333 ms  0.916 ms  1.603 ms
2  10.1.240.1 (10.1.240.1)  10.178 ms  6.857 ms  8.109 ms
3  host-24-246-128-77.com.morrisbb.com (24.246.128.77)  7.856 ms  8.133 ms  7.372 ms
4  207.144.87.33 (207.144.87.33)  9.891 ms  19.330 ms  8.068 ms
5  bldw-mlx-sprt-mlxe8-roadm-ss.skybest.com (69.77.128.233)  8.790 ms  10.309 ms  9.066 ms
6  xe-8-3-2.bar2.raleigh1.level3.net (4.71.162.193)  13.177 ms  13.216 ms *
7  ae-1-3514.edge2.atlanta4.level3.net (4.69.150.197)  18.067 ms  18.292 ms  16.740 ms
8  * * *
9  * * *
10  * * *

and it goes on from there

An update besides “We are continuing working on this issue…” would be nice. Like, you know, what’s going on? Did a server catch fire? Is Blizzard being hacked? Is it DDOS? Did China invade?

2 Likes

Really? I’m unable to log into any horde characters I have of Greymane. However, I can log onto and play an aliance character on Bonechewer.

Preeeetty damn crazy that this was an issue an hour or two before I got home at 0730, and it’ still an issue this late into the day with nothing on the launcher to suggest that something is even wrong.

Rastreando a rota para 24.105.62.129 com no m ximo 30 saltos

  1    <1 ms    <1 ms    <1 ms  Broadcom.Home [192.168.1.1] 
  2     *        *        *     Esgotado o tempo limite do pedido.
  3     8 ms     8 ms     8 ms  187-100-198-100.dsl.telesp.net.br [187.100.198.100] 
  4     3 ms     8 ms     9 ms  187-100-194-14.dsl.telesp.net.br [187.100.194.14] 
  5     4 ms     8 ms     9 ms  187-100-39-37.dsl.telesp.net.br [187.100.39.37] 
  6    15 ms    18 ms    17 ms  hu-0-3-0-2-100-grtriotw3.priv.net.telefonicaglobalsolutions.com [94.142.103.230] 
  7   118 ms   118 ms   118 ms  5.53.5.149 
  8   140 ms   136 ms   139 ms  84.16.12.159 
  9   133 ms   136 ms   136 ms  81.173.106.21 
 10     *        *        *     Esgotado o tempo limite do pedido.
 11     *      148 ms   146 ms  et-0-0-2-br01-eqch2.as57976.net [137.221.65.13] 
 12   154 ms   155 ms   155 ms  be1-pe01-eqch2.as57976.net [137.221.69.67] 
 13   156 ms   155 ms   155 ms  24.105.62.129 

Rastreamento conclu¡do.

hey guys it is a routing issue turn on your vpn (mine is Cyberghost)and it instantly played perfectly. Like it never had an issue. Wow is running perfect.

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Linksys08317 [192.168.1.1] 
  2     3 ms     3 ms     3 ms  100.105.24.1 
  3     *        *        *     Request timed out.
  4    12 ms     1 ms    <1 ms  100.100.1.99 
  5    <1 ms    <1 ms    <1 ms  100.100.0.2 
  6     1 ms     1 ms     1 ms  208.95.183.254 
  7    19 ms    68 ms    10 ms  208.95.183.245 
  8    10 ms    10 ms    10 ms  10-2-4.ear1.Atlanta1.Level3.net [4.71.20.205] 
  9    10 ms    10 ms    10 ms  ae-2-3514.edge2.Atlanta4.Level3.net [4.69.150.165] 
 10    10 ms    10 ms    11 ms  BLIZZARD-EN.edge2.Atlanta4.Level3.net [4.53.238.70] 
 11    59 ms    72 ms    35 ms  ae1-br01-eqat2.as57976.net [137.221.75.33] 
 12    33 ms    32 ms     *     et-0-0-4-br02-eqch2.as57976.net [137.221.65.46] 
 13    33 ms    33 ms    33 ms  be2-pe01-eqch2.as57976.net [137.221.69.71] 
 14    34 ms    34 ms    34 ms  24.105.62.129 

Trace complete.

Heck at this point with all of us probably constantly attempting to log in, I’d bet that we’re doing a ddos by accident or something.

All of the time-outs people are getting at the 137.221.65.42 is the Ripenet address. That is a european IP .

Why does a tracerout to blizzard server go through Ripenet ?

It’s fixed for me!

*Note: i also have my pets back…

  1    <1 ms    <1 ms    <1 ms  
  2    <1 ms    <1 ms    <1 ms  
  3     2 ms     3 ms     4 ms   
  4    18 ms    12 ms    25 ms  tukw-agw1.inet.qwest.net [63.226.198.1] 
  5     5 ms     4 ms     4 ms  sea-brdr-03.inet.qwest.net [67.14.41.150] 
  6     *        *        *     Request timed out.
  7     4 ms     4 ms     3 ms  ae-1-3513.edge1.Seattle3.Level3.net [4.69.160.69] 
  8     4 ms     4 ms     4 ms  BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146] 
  9    54 ms    53 ms    54 ms  ae1-br02-eqse2.as57976.net [137.221.73.35] 
 10    53 ms    53 ms     *     xe-0-0-1-1-br02-eqch2.as57976.net [137.221.65.42] 
 11    54 ms    53 ms    54 ms  be2-pe01-eqch2.as57976.net [137.221.69.71] 
 12    54 ms    54 ms    53 ms  24.105.62.129 

Trace complete.

Just to add another data point, New Hampshire is still out since I am unable to play, I was hoping to get some gaming on my day off :frowning:

1 Like

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms wc69lt [172.16.140.2]
2 26 ms 2 ms 2 ms 24.105.62.129

Trace complete.

I can now get to character selection but get stuck at 75 percent loading in

fixed for me, try logging in now I’m not using any VPNS

Finally able to log and able to do nothing. Now got disconnected again

I can log in and play just fine, I can solo dgs and other instances,. but if I use the dg finder or que for a bg, once I enter the dg or bg i get hug lag spikes and im unable to do anything but ctrl alt del out. then my character gets stuck in the instance. but i can use my other characters no problem, as long as i dont que for anything… weird

Started working for me as well after long hours of frustration :slight_smile:

That’s happened to me a couple of times BRODEE, and also I’ve been able to get in to my server, but obviously nothing happening. But mostly I just get the trying to login …