8/19 - Stuck at Logging in to game server


Tracing route to 23.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     4 ms     4 ms  47.197.128.1 
  3     5 ms     7 ms     4 ms  172.99.45.216 
  4     9 ms     9 ms     9 ms  ae7---0.scr01.mias.fl.frontiernet.net [74.40.3.69] 
  5    12 ms    12 ms    13 ms  ae0---0.cbr01.mias.fl.frontiernet.net [74.40.1.22] 
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    10 ms     9 ms     9 ms  be3356.ccr21.mia03.atlas.cogentco.com [154.54.10.57] 
  9    12 ms     9 ms    10 ms  be3400.ccr21.mia01.atlas.cogentco.com [154.54.47.17] 
 10    38 ms    40 ms    39 ms  be3569.ccr41.iah01.atlas.cogentco.com [154.54.82.241] 
 11    70 ms    69 ms    69 ms  be2927.ccr21.elp01.atlas.cogentco.com [154.54.29.222] 
 12    70 ms    72 ms    72 ms  be2930.ccr32.phx01.atlas.cogentco.com [154.54.42.77] 
 13    73 ms    77 ms    72 ms  be2932.ccr42.lax01.atlas.cogentco.com [154.54.45.162] 
 14    80 ms    82 ms    85 ms  be3177.ccr22.sjc01.atlas.cogentco.com [154.54.40.146] 
 15    81 ms    82 ms    82 ms  be3103.agr22.sjc01.atlas.cogentco.com [154.54.42.154] 
 16    82 ms    82 ms    83 ms  be3574.nr51.b007366-1.sjc01.atlas.cogentco.com [154.24.33.166] 
 17    82 ms    81 ms    84 ms  38.142.10.250 
 18    82 ms    82 ms    82 ms  po-1.ce01.sfo-12.us.leaseweb.net [173.208.122.1] 
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

The issue with this argument is that changing the path by running a VPN would have no impact on the issue. This is a backbone issue, something Blizzard has no control over.

1 Like

For dumb dumbs like me, what is that Tracing Route info people are posting?

1 Like

It allows one to check the pathway back to a specific IP address (ie blizz servers) to see if there are any delays along the way. As you can see many are dying at the blizzard servers…ie level3.net etc. This is the issue.

1 Like

I was able to play fine this morning till almost 2 am but ya I can’t login to any of my characters like everyone else…

1 Like

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 25 ms 1 ms <1 ms 24.105.30.129

Trace complete.

Seems this is likely more account specific than anything else, it seems many people aren’t having a problem at all while others are completely stuck.

They are just taking us back in interwebs time with the imminent launch of Classic, they wanted us to remember the outages they used to have with greater frequency! That being said, how about a blue update?

1 Like

Don’t think it has anything to do with trace routes at all. I have two wow accounts. One I can log into fine, the other gets stuck on logging into game server / constant disconnects.

If it matters to the folks troubleshooting this mess, the character I am posting the message on is the account I am unable unable to log into the game on. The second account on my battle.net account has no issues.

2 Likes

Quite simply, a traceroute procedure allows you to find out precisely how a data transmission (like a Google search) traveled from your computer to another. Essentially, the traceroute compiles a list of the computers on the network that are involved with a specific Internet activity.

The traceroute identifies each computer/server on that list and the amount of time it took the data to get from one computer to the next. If there was a hiccup or interruption in the transfer of data, the traceroute will show where along the chain the problem occurred.

Aside from being somewhat interesting, performing a traceroute also has a very practical use: If someone is having difficulty accessing a particular website or computer, performing a traceroute can help find out where the problem is occurring along the network. (from whatsmyip.com/traceroute)

1 Like

7ish hours ago, reply #68, but first (and only?) one from a blue:

It looks like Google is recovering from it.

that’s really interesting

2 Likes

I got home from the dentist at 3 and cant log on 40 minutes later. You should post and update or at least mention server issues.

Thanks.

Now I know. And knowing is half the battle! G.I JOE!

2 Likes

how many are we and what do we have in common? why are some ppl able to play? are we that special?

I would expect at least to see a message on bnet screen but nothing

same issue, sometimes I can log on but can't do anything....

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.

Alright I’ve taken a nap with my cat I’d like to kill some nagas now please

7 Likes

We are the people who support this game through the years, the addicts. We are going wild because we cant play on a Monday.

4 Likes