8/19 - Stuck at Logging in to game server

Yeah, I’m able to get to the character selection screen now, but freezes up after that.

Unfortunately I studied neuroscience and cosmology. There the structures are the same. Is this how the internet would look? I had a picture of the brain and universe that looked identical, but it won’t let me post links.

I’ve occasionally been able to access the character screen but beyond that, when i load i only get to 95%. Bandemon, its practically been doing the same thing for the past 4 hours

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     5 ms     2 ms     1 ms  24.105.30.129 

Trace complete.

Yup. I’ve been periodically checking between twitter and the actual game for a few hours Red. Saw some people had success using a VPN, but don’t know if that’s still working.

Seems to be happening for all of the Battlenet games. First noticed it in OW, then tried to open up both versions of WoW. Uninstalled and reinstalled battlenet, OW and the problem is still there. Verizon Fios customer here.

tcp traceroute as final attempt to get further;
both UDP trace and the default ICMP trace stop getting
responses past hop 9.

Verizon FIOS; normal latency to World of Warcraft is around 27 ms for me.

traceroute -T 24.105.30.129
traceroute to 24.105.30.129 (24.105.30.129), 30 hops max, 60 byte packets
1 frontdoor (192.168.1.1) 0.540 ms 0.672 ms 0.821 ms
2 * * *
3 b3351.phlapa-lcr-22.verizon-gni (dot net) (100.41.2.206) 5.056 ms 5.205 ms 5.292 ms
4 * * *
5 * * *
6 0.et-5-0-5.br2.nyc4.alter (dot net) (140.222.1.59) 7.662 ms
0.et-10-0-2.br2.nyc4.alter (dot net) (140.222.1.61) 5.007 ms
0.et-5-0-5.br2.nyc4.alter (dot net) (140.222.1.59) 6.848 ms
7 192.205.34.49 (192.205.34.49) 8.763 ms 8.735 ms 8.695 ms
8 cr2.n54ny.ip.att (dot net) (12.122.130.170) 10.522 ms 9.866 ms 10.054 ms
9 12.122.115.113 (12.122.115.113) 5.849 ms 6.681 ms 5.117 ms
10 * * *
11 * * *
12 * * *
… no further responses until trace ends at 30 attempted hops

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1     3 ms     3 ms     3 ms  hitronhub.home [192.168.0.1]
  2    24 ms    20 ms    18 ms  cblmdm72-241-48-2.buckeyecom.net [72.241.48.2]
  3    85 ms    13 ms    16 ms  24.53.168.73
  4     *        *        *     Request timed out.
  5    17 ms    18 ms    15 ms  24.53.168.1
  6    22 ms    25 ms    22 ms  10ge14-14.core1.chi1.he.net [184.105.63.89]
  7    22 ms    23 ms    23 ms  100ge2-2.core2.chi1.he.net [184.104.192.118]
  8     *        *        *     Request timed out.
  9    78 ms    78 ms    77 ms  ae1-br01-eqch2.as57976.net [137.221.69.33]
 10    80 ms    82 ms    79 ms  137.221.65.132
 11    80 ms   110 ms    94 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]

 12    82 ms    89 ms    81 ms  be1-pe01-eqla1.as57976.net [137.221.68.67]
 13    89 ms    83 ms    80 ms  lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]

 14    81 ms    82 ms    75 ms  24.105.30.129

Trace complete.

When I couldn’t get into WOW I tried Diablo and that wasn’t working either.

cant log in to game

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 3 ms 3 ms 3 ms 10.131.0.46
4 7 ms 8 ms 7 ms et-1-0-20.edge4.Atlanta2.Level3. net [4.14.249.89]
5 6 ms 7 ms 6 ms ae-1-3514.edge2.Atlanta4.Level3. net [4.69.150.197]
6 29 ms 8 ms 7 ms BLIZZARD-EN.edge2.Atlanta4.Level3. net [4.53.238.70]
7 56 ms 55 ms 55 ms ae1-br01-eqat2.as57976. net [137.221.75.33]
8 57 ms 57 ms 56 ms xe-0-0-0-0-br01-eqda6.as57976. net [137.221.65.48]
9 57 ms 57 ms 56 ms et-0-0-29-br02-eqda6.as57976. net [137.221.65.101]
10 60 ms 56 ms 55 ms et-0-0-2-br02-swlv10.as57976. net [137.221.65.67]
11 57 ms 56 ms 55 ms 137.221.65.122
12 102 ms 115 ms 115 ms et-0-0-2-br01-eqla1.as57976. net [137.221.65.68]
13 56 ms 57 ms 57 ms be1-pe01-eqla1.as57976. net [137.221.68.67]
14 57 ms 56 ms 55 ms 24.105.30.129

May or may not be related, but Diablo doesn’t run for me either. Gets as far as loading the final playable game screen, then freezes, with only the mouse pointer being movable. Nothing clickable though, had to use task manager to quit.

The same issue here. Verizon Fios. PA
Tracing route to 24.105.30.129 over a maximum of 30 hops

1 2 ms 2 ms 1 ms 192.168.1.1
2 7 ms 11 ms 6 ms 24.105.30.129

Trace complete.

I’m in Bucks cty and thanks for the VPN idea. Connecting from elsewhere in the US now and got in right away.

1 Like

Did you all buy Blizzards new vpn that went live today?

1 Like
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    13 ms     9 ms     9 ms  24.105.30.129 

Trace complete.

Blockquote

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

1 31 ms 9 ms 2 ms 192.168.1.1 [192.168.1.1]
2 37 ms 35 ms 35 ms 190-207-64-1.dyn.dsl.cantv .net [190.207.64.1]
3 83 ms 82 ms 144 ms 172.26.29.1 [172.26.29.1]
4 * * * Tiempo de espera agotado para esta solicitud.
5 1307 ms 75 ms 60 ms 10.82.1.33 [10.82.1.33]
6 86 ms 122 ms 101 ms 10.82.1.1 [10.82.1.1]
7 260 ms 101 ms 106 ms globenet-177.as52320 .net [200.16.71.177]
8 * * * Tiempo de espera agotado para esta solicitud.
9 177 ms 181 ms 180 ms ae1-br01-eqmi2.as57976 .net [137.221.76.33]
10 271 ms * 199 ms 137.221.65.62
11 172 ms 138 ms 191 ms et-0-0-2-br02-swlv10.as57976 .net [137.221.65.67]
12 * 146 ms 139 ms 137.221.65.122
13 219 ms 159 ms 145 ms et-0-0-2-br01-eqla1.as57976 .net [137.221.65.68]
14 187 ms 218 ms 208 ms be1-pe02-eqla1.as57976 .net [137.221.68.69]
15 217 ms 209 ms 214 ms lax-eqla1-ia-bons-03.as57976 .net [137.221.66.7]
16 220 ms 145 ms 169 ms 24.105.30.129

Traza completa.

Blockquote

Would be great to get some traceroutes from people using VPNs and getting in just fine to see if there are obvious differences in the route.

Not true. I am using a US VPN to connect just fine.

same EPB and cant log in

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1     2 ms     2 ms     1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    19 ms    14 ms    14 ms  86-165-89-200.fibertel.com.ar [200.89.165.86]
  6    10 ms     9 ms    10 ms  ae6.baires3.bai.seabone.net [185.70.203.22]
  7   132 ms   128 ms   130 ms  et0-1-0.miami19.mia.seabone.net [89.221.41.171]
  8   135 ms   135 ms   132 ms  be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17]
  9   134 ms   135 ms   135 ms  be3400.ccr21.mia01.atlas.cogentco.com [154.54.47.17]
 10   134 ms   134 ms   135 ms  be3410.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.6.86]
 11   136 ms   135 ms   135 ms  te0-0-2-0.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.46]
 12   132 ms   131 ms   130 ms  gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
 13   176 ms   177 ms   175 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33]
 14   175 ms   177 ms   176 ms  xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
 15   189 ms   186 ms   204 ms  et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
 16   175 ms   175 ms   176 ms  137.221.65.122
 17   178 ms   177 ms   175 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
 18   177 ms   176 ms   177 ms  be1-pe02-eqla1.as57976.net [137.221.68.69]
 19   177 ms   188 ms   177 ms  24.105.30.129

Trace complete.