8/19 - Stuck at Logging in to game server

There is an expectation of some this level of support for a 24 hour a day service.

Hi Jambrix, these are the results:

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1     2 ms     3 ms     1 ms  router.asus.com [192.168.1.1] 
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    26 ms    14 ms    16 ms  250-165-89-200.fibertel.com.ar [200.89.165.250] 
  6    15 ms    16 ms    14 ms  221-165-89-200.fibertel.com.ar [200.89.165.221] 
  7    15 ms    15 ms    15 ms  129-165-89-200.fibertel.com.ar [200.89.165.129] 
  8    19 ms    16 ms    14 ms  150-165-89-200.fibertel.com.ar [200.89.165.150] 
  9    17 ms    18 ms    12 ms  ae6.baires3.bai.seabone.net [185.70.203.22] 
 10   145 ms   136 ms   136 ms  et0-3-0.miami19.mia.seabone.net [89.221.41.161] 
 11   140 ms   140 ms   139 ms  be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17] 
 12   141 ms   138 ms   147 ms  be3400.ccr21.mia01.atlas.cogentco.com [154.54.47.17] 
 13   141 ms   139 ms   138 ms  be3410.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.6.86] 
 14   139 ms   140 ms   139 ms  te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42] 
 15   134 ms   133 ms   135 ms  gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5] 
 16   179 ms   178 ms   182 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33] 
 17   177 ms   191 ms   177 ms  xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62] 
 18   178 ms   179 ms   178 ms  et-0-0-2-br02-swlv10.as57976.net [137.221.65.67] 
 19   179 ms   178 ms   178 ms  137.221.65.122 
 20   179 ms   205 ms   360 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68] 
 21   180 ms   177 ms   179 ms  be1-pe02-eqla1.as57976.net [137.221.68.69] 
 22   178 ms   177 ms   181 ms  lax-eqla1-ia-bons-03.as57976.net [137.221.66.7] 
 23   177 ms   177 ms   177 ms  24.105.30.129 

Trace complete.

Bliz has entire NOC centers that monitor Battlenet constantly; however, they aren’t public facing. Once information on an issue is approved for release, then you hear about it.

Investigations don’t necessarily start with the first public acknowledgement.

No you don’t, Delaiya. The fees to play this game take into account both expected and unexpected down times. Never has Battlenet been advertised as 100% up time.

9 Likes
Traza a 24.105.62.129 sobre caminos de 30 saltos como máximo.

  1     9 ms     7 ms     7 ms  Docsis-Gateway.utopia.net [192.168.0.1]
  2    17 ms    15 ms    17 ms  10.16.128.1
  3    18 ms    17 ms    19 ms  10.101.197.1
  4    36 ms    22 ms    21 ms  10.100.5.1
  5    33 ms    30 ms    34 ms  86-165-89-200.fibertel.com.ar [200.89.165.86]
  6    23 ms    23 ms    22 ms  ae6.baires3.bai.seabone.net [185.70.203.22]
  7   146 ms   150 ms   144 ms  et2-1-0.miami19.mia.seabone.net [89.221.41.181]
  8   153 ms   153 ms   154 ms  be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17]
  9   157 ms   157 ms   152 ms  be3401.ccr22.mia01.atlas.cogentco.com [154.54.47.29]
 10   160 ms   153 ms   154 ms  be3411.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.26.42]
 11   153 ms   155 ms   153 ms  te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42]
 12   153 ms   152 ms   153 ms  gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
 13     *        *        *     Tiempo de espera agotado para esta solicitud.
 14     *        *        *     Tiempo de espera agotado para esta solicitud.
 15     *      182 ms   181 ms  et-0-0-4-br02-eqch2.as57976.net [137.221.65.46]
 16   181 ms   181 ms   184 ms  be2-pe02-eqch2.as57976.net [137.221.69.73]
 17   184 ms   182 ms   181 ms  24.105.62.129

Traza completa.
1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2    12 ms     4 ms     9 ms  loop0.17w.ba05.mtpr.nf.aliant.net [142.163.63.6]
  3    <1 ms     7 ms     8 ms  ae15-182.dr02.mtpr.nf.aliant.net [142.166.242.169]
  4    23 ms    16 ms    25 ms  ae4.cr02.hlfx.ns.aliant.net [142.166.185.94]
  5    17 ms    17 ms    27 ms  hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net [142.166.149.93]
  6    34 ms    35 ms    35 ms  be19.bx01.nycm.ny.aliant.net [207.231.227.110]
  7    37 ms    34 ms    34 ms  lag-197.ear3.NewYork1.Level3.net [4.71.230.101]
  8     *       40 ms    36 ms  4.69.216.226
  9    43 ms    44 ms    34 ms  BLIZZARD-EN.ear1.NewYork5.Level3.net [4.35.72.34]
 10   115 ms   117 ms   118 ms  ae1-br01-eqny8.as57976.net [137.221.71.33]
 11   116 ms   118 ms   118 ms  et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
 12   116 ms   118 ms   117 ms  et-0-0-29-br01-eqch2.as57976.net [137.221.65.2]
 13   122 ms   118 ms   120 ms  137.221.65.132
 14   298 ms   219 ms   221 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
 15   119 ms   117 ms   117 ms  be1-pe01-eqla1.as57976.net [137.221.68.67]
 16   115 ms   118 ms   116 ms  lax-eqla1-ia-bons-01.as57976.net [137.221.66.1]
 17     *        *        *     Request timed out.
 18   118 ms   118 ms   117 ms  24.105.29.60
Tracing route to 24.105.30.129 over a maximum of 30 hops

1 4 ms 4 ms 4 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 5 ms 10 ms 5 ms 24.105.30.129

Trace complete.

I can log into WoW on my other NA account from the same computer, but everything is bugged in game and can’t do anything.

Look, if y’all seem to think all technical issues would be solved the minute they appear and that none should actually occur go play a board game.
Systems this big have issues sometimes and we deal with it. Blizzard has only a certain amount of capacity to deal with any issue at a given time so chill out. Real people are working on this and they don’t need crap from you, especially not on a thread hoping to SOLVE the issue.

4 Likes

There you have…

Traza a 24.105.30.129 sobre caminos de 30 saltos como máximo.

1 2 ms 1 ms 1 ms 192.168.0.1
2 2 ms 1 ms 1 ms 192.168.1.1
3 8 ms 3 ms 43 ms 192.168.182.249
4 * * * Tiempo de espera agotado para esta solicitud.
5 15 ms 13 ms 13 ms 172.31.241.157
6 * * 11 ms 192.168.69.18
7 11 ms 10 ms 10 ms 84.16.7.132
8 110 ms 110 ms 111 ms 94.142.99.41
9 129 ms 130 ms 220 ms 94.142.125.233
10 135 ms 136 ms 151 ms 81.173.106.21
11 274 ms 171 ms 233 ms ae1-br01-eqdc2.as57976net [137.221.72.33]
12 242 ms 202 ms 196 ms et-0-0-2-br01-eqch2.as57976net [137.221.65.13]
13 206 ms 201 ms 202 ms 137.221.65.132
14 221 ms 172 ms 260 ms et-0-0-2-br01-eqla1.as57976net [137.221.65.68]
15 172 ms 193 ms 201 ms be1-pe02-eqla1.as57976net [137.221.68.69]
16 235 ms 202 ms 174 ms lax-eqla1-ia-bons-03.as57976net [137.221.66.7]
17 188 ms 201 ms 204 ms 24.105.30.129

Theyre going to get the crap anyway you put it we pay for the services on this game. Just Solve the issue and were all be on our happy way

Below is my tracert. Notes about my connection:

Tethered from an iPhone on Verizon Wireless.
I can connect, view characters, and login to the MDI tournament realm - without issue. Only live realms are having this issue.

  1    <1 ms    <1 ms    <1 ms  172.20.10.1
  2    62 ms    58 ms    69 ms  185.sub-66-174-30.myvzw.com [66.174.30.185]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    60 ms    50 ms    57 ms  51.sub-69-83-175.myvzw.com [69.83.175.51]
  7    60 ms    56 ms    56 ms  195.sub-69-83-175.myvzw.com [69.83.175.195]
  8    83 ms    52 ms    67 ms  82.sub-69-83-162.myvzw.com [69.83.162.82]
  9    66 ms    48 ms    59 ms  67.sub-66-174-29.myvzw.com [66.174.29.67]
 10    66 ms    56 ms    57 ms  152.179.42.113
 11    72 ms    78 ms    70 ms  0.ae1.BR1.LAX15.ALTER.NET [140.222.229.163]
 12    55 ms    69 ms    54 ms  ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
 13    75 ms    58 ms    67 ms  BLIZZARD-EN.ear3.LosAngeles1.Level3.net [4.71.135.106]
 14    77 ms    61 ms    57 ms  ae1-br02-eqla1.as57976.net [137.221.68.35]
 15    69 ms    70 ms    69 ms  be2-pe02-eqla1.as57976.net [137.221.68.73]
 16    80 ms    79 ms    60 ms  24.105.30.129
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 7 ms 6 ms 6 ms 24.105.30.129

Trace complete.

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 1 ms <1 ms 1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
3 4 ms 2 ms 3 ms 24.105.62.129

Trace complete.

stuck in log in screen long time
when logged in running in city with no NPCs
what up?
I use Verizon is it some provider issue?

Trace 1: On VPN, Service Works

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 10 ms 9 ms 9 ms 10.102.0.1
2 10 ms 9 ms 11 ms 5.181.234.37
3 229 ms 163 ms 21 ms 83.97.21.12
4 9 ms 8 ms 9 ms 193.9.115.242
5 10 ms 65 ms 10 ms 206.82.104.192
6 202 ms 161 ms 143 ms 137.221.71.33
7 72 ms 72 ms 72 ms 137.221.65.8
8 72 ms 72 ms 71 ms 137.221.65.2
9 167 ms 143 ms 150 ms 137.221.65.132
10 74 ms 73 ms 72 ms 137.221.65.68
11 73 ms 73 ms 72 ms 137.221.68.67
12 162 ms 150 ms 142 ms 24.105.30.129

Trace complete.

Trace 2: VPN Off, Service doesn’t work

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 6 ms 10 ms 24.105.30.129

Trace complete.

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 4 ms 3 ms 3 ms 24.105.30.129

Trace complete.

From the Washington DC area - same as other East Coast users.

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 33 ms 5 ms 6 ms fios_router
2 7 ms 5 ms 6 ms 24.105.30.129

Playing from Japan. I get disconnected trying to enter a battleground.

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 1 ms <1 ms <1 ms router.asuscom [192.168.1.1]
2 37 ms 42 ms 44 ms 153.153.217.252
3 32 ms 42 ms 46 ms 153.153.217.217
4 34 ms 40 ms 41 ms 153.153.223.145
5 31 ms 44 ms 36 ms 180.8.126.45
6 34 ms 30 ms 30 ms 122.1.245.213
7 167 ms 21 ms 141 ms ae-6.r03.tokyjp05.jp.bb.gin.nttnet [120.88.53.29]
8 * 34 ms 39 ms ae-0.level3.tokyjp05.jp.bb.gin.nttnet [129.250.8.202]
9 107 ms 121 ms 111 ms ae-2-3613.edge1.Seattle3.Level3net [4.69.160.73]
10 123 ms 123 ms 117 ms BLIZZARD-EN.edge1.Seattle3.Level3net [4.59.232.146]
11 144 ms 141 ms 139 ms ae1-br01-eqse2.as57976net [137.221.73.33]
12 129 ms 159 ms 140 ms xe-0-0-0-1-br01-eqsv5.as57976net [137.221.65.40]
13 156 ms 126 ms 124 ms et-0-0-29-br02-eqsv5.as57976net [137.221.65.117]
14 141 ms 146 ms 144 ms xe-0-0-1-1-br02-eqla1.as57976net [137.221.65.6]

Been dealing with the same issue since 6.30am its now 9.53 am Says Logging into Game server but that’s it … tried logging into classic same thing., fix this and make a note about it or something . I for one am frustrated that you aren’t making a notice letting people know… its not my computer or anything else its YOUR END

1 Like

A blue has indeed posted on this thread telling people to post their respective tracert. They are aware of it & are working on resolving the issue. You could help out & post your tracert as well. The more information we give them that they request, the better it will be for us all.

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 10 ms 8 ms 9 ms [58.162.26.200]
3 37 ms 42 ms 39 ms [203.50.62.242]
4 9 ms 12 ms 10 ms [203.50.61.144]
5 22 ms 29 ms 27 ms [203.50.11.122]
6 25 ms 23 ms 22 ms [203.50.6.61]
7 56 ms 67 ms 64 ms [203.50.13.90]
8 198 ms 198 ms 205 ms [202.84.141.25]
9 197 ms 199 ms 198 ms [202.84.247.17]
10 197 ms 197 ms 197 ms [154.54.11.45]
11 242 ms 246 ms 247 ms 38.88.224.5
12 305 ms 310 ms 295 ms [137.221.70.33]
13 271 ms * * [137.221.65.10]
14 262 ms 262 ms 262 ms [137.221.69.69]
15 264 ms 264 ms 264 ms 24.105.62.129

Trace complete.

frozen character models with names “unknown”, skills not functioning, unable to logout or exit game through the menu, infinite loading screens is all what happens if I’m even able to get into the game

1 Like