8/19 - Stuck at Logging in to game server

Support Technical Support
1547

Just got in.

1548 
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    44 ms    57 ms    43 ms  71-50-192-254.crls.centurylink.net [71.50.192.254] 
  3    43 ms    43 ms    47 ms  75.160.220.233 
  4   139 ms   101 ms   100 ms  184-102-48-2.crls.qwest.net [184.102.48.2] 
  5     *        *        *     Request timed out.
  6    52 ms    52 ms    52 ms  BLIZZARD-EN.ear3.Washington1.Level3.net [4.16.70.182] 
  7     *        *        *     Request timed out.
  8     *       71 ms     *     et-0-0-2-br01-eqch2.as57976.net [137.221.65.13] 
  9    68 ms    73 ms    68 ms  be1-pe01-eqch2.as57976.net [137.221.69.67] 
 10   127 ms   125 ms   115 ms  chi-eqch2-ia-bons-02.as57976.net [137.221.66.11] 
 11   208 ms   210 ms   139 ms  24.105.62.129 

Trace complete.
1549

Thanks for the tip… Wont be Qing for a while

1550

still stuck in “logging into game server” new Hampshire here

1551 
Tracing route to 24.105.62.129 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms  192.168.1.1 
2     5 ms     8 ms    10 ms  24.105.62.129 

Trace complete.
1552

East coast here, near DC…just got online, everything is working fine!

1553

after almost 5 hours it finally let me login

1554

Guys I think the game is working fine now, let me know if I’m wrong but try logging in.

1555

It is not just WoW. Overwatch and some other Blizz games too. The internet is like a network of roads. You take different ones to get to different cities. The trip to NY might be fine but the traffic to San Fran is at a stand still.

Same thing happens when you connect to different websites. They are physically in very different places and take different routing paths.

The good news for you, is that those other websites working means it is not something specific to your local house network or your local ISP. It is farther down the line.

Greymane is in Chicago which was seeming to have issues and Bonechewer is in Los Angeles. Two very different routing paths.

2 Likes
1556

OMG I’M IN !!!
Dam … nothing moving
/sadface

1557

Wonder if now that it’s fixed we will get the real reason for the outage?

1558

Blizz seems to have finally fixed whatever was causing he issue.

1559

not fixed in my area

1 Like
1560

oh yeah Im really raging lmao

1561 
Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Linksys25375 [192.168.1.1] 
  2     1 ms     1 ms    <1 ms  192.168.254.254 
  3     *        *        *     Request timed out.
  4     6 ms     7 ms     8 ms  172.99.44.6 
  5    13 ms    11 ms    11 ms  ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73] 
  6    14 ms    12 ms    11 ms  ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126] 
  7     *        *        *     Request timed out.
  8     *        *       14 ms  ae-1-51.ear2.Miami1.Level3.net [4.69.207.21] 
  9    12 ms    11 ms    11 ms  BLIZZARD-EN.ear2.Miami1.Level3.net [4.16.176.198] 
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    45 ms    47 ms     *     et-0-0-4-br02-eqch2.as57976.net [137.221.65.46] 
 13    49 ms    48 ms    46 ms  be2-pe01-eqch2.as57976.net [137.221.69.71] 
 14    49 ms    47 ms    47 ms  24.105.62.129 

Trace complete.
1562

whois appears to tell me that it’s a Blizzard IP (leased from Ripenet?). Country does show as NL, though.

1563

still nothing for lil ole me

1564

Still unable to log in - NJ

1565

I logged out of battle net then tried again and it worked!

1566

I am now able to log in and play normally.