8/19 - Stuck at Logging in to game server

Thank you :wink:
The only thing that sticks out to me so far is that the hop right before it gets to the 137...* part of the trace isn’t in anybody else’s traceroutes.

I’m using comcast on the east coast and having the same issue.

its not the isp , its the bridges they have to cross to get to blizzard, so it might mainly be verizon but not all of it obviously

I don’t think it has anything to do with type of internets right?

well i have been trying to log on for about 2 hours .I am glad that i am not the only on

That’s bunk.

If that were the case I wouldn’t be able to log in and play PTR.

Did a Windows update this morning and started having issues after that. Wonder if there is a connection…or lack of one, in this case. PLayed fine all weekend long without any hickups.

1 Like

this is why i can’t help but think this is somthin malicious. either from people in blizzard or somthin else

Blizzard confirmed it’s NOT a DDoS.

maby not the kind you think anyway lol

yes i did the windows update this morning too and after that it stated to have problem with wow too

1 Like

As of 8/19 I’ve been having this issue. Prior to this minor lag issues but never this. This is a glaring issue! I can’t play this or OW. If this effects Classic - I’m going to scream:sob:

1 Like

more like a pending update with no option to download lol

And me too.

I was playing fine this moring around 6am ect and got DC figured maybe they got a head start on the maintenance its been 6 hours now still cant get in or still isn’t frozen in game

RIP wow today :cry:

like im hearing about this windows update , but i dont even have a button to “download” it , like wut? and it says pending lol

saw an update today when i started the launcher. updated, launched, logging into servers…indefinitely for past 6 hours for me.

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1     1 ms     2 ms     2 ms  modem.domain [192.168.0.1] 
  2     5 ms     7 ms     4 ms  ptld-dsl-gw53.ptld.qwest.net [207.225.84.53] 
  3     3 ms     3 ms     3 ms  ptld-agw1.inet.qwest.net [207.225.86.161] 
  4     4 ms     3 ms     3 ms  209-180-169-2.ptld.qwest.net [209.180.169.2] 
  5     7 ms     6 ms     6 ms  ae-1-3513.edge1.Seattle3.Level3.net [4.69.160.69] 
  6     7 ms     7 ms    27 ms  BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146] 
  7    29 ms    28 ms    28 ms  ae1-br01-eqse2.as57976.net [137.221.73.33] 
  8    28 ms    28 ms    29 ms  xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40] 
  9    29 ms    32 ms    29 ms  et-0-0-29-br02-eqsv5.as57976.net [137.221.65.117] 
 10    31 ms   100 ms   218 ms  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 
 11    29 ms    28 ms    28 ms  be2-pe01-eqla1.as57976.net [137.221.68.71] 
 12    29 ms    30 ms    31 ms  lax-eqla1-ia-bons-02.as57976.net [137.221.66.3] 
 13    29 ms    28 ms    28 ms

Nice stall tactic. In other words even Blizzards own network operation center doesn’t know what the problem is.