8/19 - Stuck at Logging in to game server

Unplayable for 6 hours so far. I was disconnected while in a +10 mythic Sethraliss on the trash before the end boss.

Reddit AMA Tomorrow, FYI EVERYONE… Now’s your opportunity to let Blizz know how you feel.

2 Likes

I was able to log in Kil’Jaedon and play my toons on there but when I log into Bleeding Hollow, it gets stuck on loading up my toon screen. Hmmm. Is it just certain realms that are down?

Same issue here.
First login: frozen unable to move or open menus.
Second login: Character screen wouldn’t load.
Third login: Loading screen would not complete.

I’ve tried to log in on multiple characters who were in different zones and I still have the same issue.

2 Likes
Tracing route to 24.105.30.129 over a maximum of 30 hops

  1     1 ms     2 ms     1 ms  modem.Home [192.168.0.1] 
  2    20 ms    20 ms    23 ms  phn4-dsl-gw06.phn4.qwest.net [71.32.112.6] 
  3    20 ms    20 ms    20 ms  phn4-agw1.inet.qwest.net [71.32.113.41] 
  4    21 ms    20 ms    20 ms  209.181.128.2 
  5     *        *        *     Request timed out.
  6    30 ms    29 ms    29 ms  blizzard-en.ear3.losangeles1.level3.net [4.71.135.106] 
  7    29 ms    29 ms    32 ms  ae1-br02-eqla1.as57976.net [137.221.68.35] 
  8    29 ms    29 ms    29 ms  be2-pe02-eqla1.as57976.net [137.221.68.73] 
  9    30 ms    36 ms    30 ms  lax-eqla1-ia-bons-03.as57976.net [137.221.66.7] 
 10    29 ms    29 ms    30 ms  24.105.30.129 

Trace complete.

Yes it is, but my T-Mobile phones hotspot has the same result.

For overwatch I switched from americas to europe and I work fine… lol

So how about an update at least Blizz?

2 Likes

they having too much fun reading my qq’s atm to go fix it

Same exact thing for my, at around 7am est on 8/19 a huge lag spike and it still is happening. I get to Area 52 login screen and no characters load

It’s clearly a Blizz sided issue - I can load non-blizzard games with no issue what so ever.

3 Likes
Rastreando a rota para 137.221.105.2 com no m ximo 30 saltos

  1    <1 ms    <1 ms    <1 ms  192.168.1.1 
  2     *        *        *     Esgotado o tempo limite do pedido.
  3     *        *        *     Esgotado o tempo limite do pedido.
  4     *        *        *     Esgotado o tempo limite do pedido.
  5     8 ms    15 ms    15 ms  86-165-89-200.fibertel.com.ar [200.89.165.86] 
  6     9 ms     9 ms    10 ms  85-165-89-200.fibertel.com.ar [200.89.165.85] 
  7    11 ms     9 ms     8 ms  197-165-89-200.fibertel.com.ar [200.89.165.197] 
  8    15 ms    16 ms    14 ms  222-165-89-200.fibertel.com.ar [200.89.165.222] 
  9     *        *        *     Esgotado o tempo limite do pedido.
 10   136 ms   137 ms   136 ms ae1-300G.ar5.MIA1.gblx.net ``[67.17.94.249] 
 11     *        *        *     Esgotado o tempo limite do pedido.
 12     *      136 ms   135 ms  ae-2-52.ear2.Miami1.Level3.net [4.69.207.25] 
 13   142 ms   151 ms   168 ms  BLIZZARD-EN.ear2.Miami1.Level3.net [4.16.176.198] 
 14   209 ms   181 ms   182 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33] 
 15   182 ms   186 ms   204 ms  xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62] 
 16   182 ms   179 ms   183 ms  et-0-0-2-br02-swlv10.as57976.net [137.221.65.67] 
 17   181 ms   183 ms   183 ms  et-0-0-67-pe02-swlv10.as57976.net [137.221.83.73] 
 18   180 ms   217 ms   180 ms  137.221.105.2 

Rastreamento conclu¡do.


Rastreando a rota para 24.105.62.129 com no m ximo 30 saltos

  1    <1 ms    <1 ms    <1 ms  192.168.1.1 
  2     *        *        *     Esgotado o tempo limite do pedido.
  3     *        *        *     Esgotado o tempo limite do pedido.
  4     *        *        *     Esgotado o tempo limite do pedido.
  5    13 ms    15 ms    15 ms  86-165-89-200.fibertel.com.ar [200.89.165.86] 
  6    10 ms     9 ms     9 ms  ae6.baires3.bai.seabone.net [185.70.203.22] 
  7   136 ms   134 ms   137 ms  et2-1-0.miami19.mia.seabone.net [89.221.41.181] 
  8   141 ms   138 ms   138 ms  be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17] 
  9   137 ms   138 ms   143 ms  be3400.ccr21.mia01.atlas.cogentco.com [154.54.47.17] 
 10   142 ms   139 ms   137 ms  be3410.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.6.86] 
 11   138 ms   138 ms   138 ms  te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42] 
 12   139 ms   136 ms   135 ms  gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5] 
 13   169 ms   161 ms   171 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33] 
 14   170 ms   179 ms   166 ms  xe-0-0-0-1-br01-eqat2.as57976.net [137.221.65.50] 
 15     *        *      166 ms  et-0-0-4-br02-eqch2.as57976.net [137.221.65.46] 
 16   166 ms   165 ms   167 ms  be2-pe02-eqch2.as57976.net [137.221.69.73] 
 17   169 ms   171 ms   173 ms  24.105.62.129 

Rastreamento conclu¡do.

Yeah i was able at one point to get onto moon guard and i was able to play characters there but i cant get to my main on Area 52

Tracing route to 24.105.30.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     1 ms     1 ms     2 ms  24.105.30.129 

Trace complete.

Why doesn’t Blizzard put up a message that there are problems logging in for some people so we don’t have to waste time attempting to…

2 Likes

Yes, been having this same issue for the past several hours. It seems to manifest in different ways and is one of or a combination of the following:

  • Stuck at 3/4’s during loading
  • Stuck at or really long wait at “logging in” screen
  • Manage to log in as a character but literally can’t do anything or talk to anyone(tabards also don’t display guild logo, can’t rez at spirit healer, etc)

Edit: Tried several different realms with no luck but guess who IS online, it’s ya boi Asmongold! ffs… LOL

4 Likes

Can’t log in to server for going on 5 hours now! Come on Blizzard. Get it together!

4 Likes

Tracing route to 24.105.30.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 * * * Request timed out.
3 6 ms 3 ms 3 ms 172.102.105.58
4 4 ms 4 ms 4 ms ae8—0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 5 ms 7 ms 6 ms ae1—0.cbr01.lsan.ca.frontiernet.net [74.40.3.214]
6 4 ms 4 ms 4 ms lag-101.ear2. LosAngeles1. Level3. net [4.16.30.129]
7 * * * Request timed out.
8 5 ms 5 ms 6 ms BLIZZARD-EN.ear3. LosAngeles1 .Level3.net [4.71.135.106]
9 1106 ms 879 ms 199 ms ae1-br01-eqla1.as57976. net [137.221.68.33]
10 5 ms 4 ms 4 ms be1-pe01-eqla1.as57976. net [137.221.68.67]
11 6 ms 6 ms 6 ms lax-eqla1-ia-bons-02.as57976. net [137.221.66.3]
12 5 ms 5 ms 5 ms 24.105.30.129

Trace complete.

If youre trying to play OW, switch servers to EU and youll be able to connect. not sure how to get around it for WoW

I don’t understand why they don’t shut the servers down and try to fix this issue/maintenance. Instead they are letting the issue grow and effect more people…

1 Like
 Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  modem.Home [192.168.0.1] 
  2    30 ms    42 ms    30 ms  slcy-dsl-gw11.slcy.qwest.net [207.108.176.11] 
  3    31 ms    30 ms    30 ms  slcy-agw1.inet.qwest.net [207.108.177.81] 
  4    33 ms    31 ms    46 ms  207-108-179-2.slkc.qwest.net [207.108.179.2] 
  5     *        *        *     Request timed out.
  6    44 ms    44 ms    45 ms  BLIZZARD-EN.ear3.LosAngeles1.Level3.net [4.71.135.106] 
  7    83 ms    76 ms    80 ms  ae1-br01-eqla1.as57976.net [137.221.68.33] 
  8    76 ms    76 ms   103 ms  et-0-0-2-br01-swlv10.as57976.net [137.221.65.69] 
  9    77 ms     *        *     137.221.65.133 
 10    77 ms    79 ms    78 ms  be1-pe01-eqch2.as57976.net [137.221.69.67] 
 11    85 ms    77 ms    77 ms  24.105.62.129 

Trace complete.