8/19 - Stuck at Logging in to game server

Someone with the VPN app do a tracert and see what it shows…

2 Likes

well…this does not bode well for the release of classic. blizzard is not responding to outage…just called ISP…this is blizzard problem. not very happy with them due to zero response. outages happen. but no response is not blizzards fault it is activisions fault. starting to see what happens when they get rid of long time blizzard employees.

Guys,

Lets calm down a bit.

I am also frustrated that I cannot play, even more today which is the only free day from work I get.

But complaining and busting this thread wont fix it.

If you are so desperate, download a VPN and play until issue gets resolved…

Have better understanding, we all pay for the game, but as Forum Admin said, Blizz doesnt advertise 100% uptime.

Ggs!

2 Likes

See Blue post above?

1 Like

What the hell is this !? Again with blizzard being happy to take my money and not monitor the quality of connection ? CON ARTISTS ! Why do i never get game time credited back but you are all more than happy to make me unable to play with your constant networking failures… JESUS BLIZZARD, GET IT TOGETHER ! DO SOMETHING RIGHT AND STOP SCREWING YOUR PLAYERS…

Been playing since vanilla. There’s been issues like these from time to time. Will likely not have any bigger an impact on classic than live.

1 Like
Tracing route to 24.105.62.129 over a maximum of 30 hops

  1     6 ms     6 ms     6 ms  testwifi.here [192.168.86.1] 
  2     7 ms     8 ms    10 ms  CAMDEN-NETWORK [192.168.1.1] 
  3    12 ms    10 ms     9 ms  swr.7750r1.lusfiber.net [76.72.8.2] 
  4    12 ms    22 ms    25 ms  10.128.0.2 
  5    35 ms    43 ms    32 ms  5-1-11.ear1.Atlanta1.Level3.net [4.14.253.117] 
  6    40 ms    32 ms    21 ms  ae-2-3514.edge2.Atlanta4.Level3.net [4.69.150.165] 
  7    62 ms    32 ms    36 ms  BLIZZARD-EN.edge2.Atlanta4.Level3.net [4.53.238.70] 
  8    58 ms    57 ms    62 ms  ae1-br01-eqat2.as57976.net [137.221.75.33] 
  9    56 ms     *        *     et-0-0-4-br02-eqch2.as57976.net [137.221.65.46] 
 10    69 ms    58 ms    53 ms  be2-pe02-eqch2.as57976.net [137.221.69.73] 
 11    53 ms    58 ms    61 ms  chi-eqch2-ia-bons-04.as57976.net [137.221.66.15] 
 12    55 ms    63 ms    56 ms  24.105.62.129 

Trace complete.

I'm in Louisiana, attempting to connect to Alleria US (realm status is up).

There is far, far more to the internet than you/your ISP and Blizzard/Blizzard’s ISP. Those parts constitute only a fraction of the overall connection.

Meaning, it can be both not you and not Blizzard.

Couldn’t get it. Connected thru VPN to Europe- worked right away.

    C:\Users\maggi>tracert 24.105.30.129

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    10 ms     8 ms    17 ms  192.168.0.1
  2    21 ms    28 ms    27 ms  192.252.192.3
  3    50 ms    27 ms    48 ms  24.53.168.93
  4     *        *        *     Request timed out.
  5    31 ms    35 ms    27 ms  24.53.168.17
  6    32 ms    38 ms    38 ms  10ge14-14.core1.chi1.he.net [184.105.63.89]
  7    31 ms    37 ms    48 ms  100ge2-2.core2.chi1.he.net [184.104.192.118]
  8     *        *        *     Request timed out.
  9    97 ms    98 ms    83 ms  ae1-br01-eqch2.as57976.net [137.221.69.33]
 10    87 ms   108 ms   118 ms  137.221.65.132
 11     *        *        *     Request timed out.
 12    88 ms    98 ms    97 ms  be1-pe01-eqla1.as57976.net [137.221.68.67]
 13   101 ms    93 ms   102 ms  lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
 14    96 ms    97 ms    87 ms  24.105.30.129

Trace complete.

Was just able to log into game server, select my character and log into Org. Folks just running in place and could not interract with any NPCs. No in game commands worked and had to force close the game.

Not sure how this is an issue with ISP connections.

1 Like

btw tht free VPN has had past compaints of it stealing and selling WoW players data, even log in info and such as it passes all ur info thru it. idk if the guy tht started advertising the vpn knew that and was trolling to get all ur accounts hacked or didn’t bother looking it its security risks

Vpn plus changing my internet to my satellite got me in… wtf is going on

You clearly do not understand what you are talking about, look at any of these trace routes, it is very clear that when you try to connect to blizz servers you are routed though many third parties that are not affiliated with blizzard. If there is an issue anywhere along the way your connection is interrupted and you cant play.

This is not blizzards issue, this isnt your ISPs issue, its a third party routing service, this is how the internet works.

If you use a VPN you may be forced to route differently and avoid this interruption.

For example if there is a car crash on a major highway, is it your cars problem that you are late to your lunch at mcdonalds, or mcdonalds fault? Its neither, its the crash on the highway and youd be better off using a different route that avoids this accident.

Please continue to act like you know more about this than the people hired by blizzard to handle their network traffic.

6 Likes

there are people on without any issues… guess they are trying to sort problems into categories

Someone with a VPN yeah do a tracert and post it up…

19/08/2019 15:37:43 UTC

PING:
PING 173.127.212.205 (173.127.212.205) 56(84) bytes of data.

— 173.127.212.205 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

This is from your test so its you not us…

>tracert 24.105.30.129
Tracing route to 24.105.30.129 over a maximum of 30 hops
  1    81 ms     6 ms     7 ms  static-47-180-11-1.lsan.ca.frontiernet.net [47.180.11.1]
  2     8 ms     7 ms    11 ms  172.102.106.210
  3     7 ms     8 ms     5 ms  ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
  4     7 ms     6 ms     9 ms  ae1---0.cbr01.lsan.ca.frontiernet.net [74.40.3.214]
  5     6 ms     6 ms     6 ms  lag-101.ear2.losangeles1.level3.net [4.16.30.129]
  6     *        *        *     Request timed out.
  7    12 ms     6 ms     5 ms  blizzard-en.ear3.losangeles1.level3.net [4.71.135.106]
  8    13 ms     6 ms     9 ms  ae1-br01-eqla1.as57976.net [137.221.68.33]
  9     7 ms     5 ms     6 ms  be1-pe02-eqla1.as57976.net [137.221.68.69]
 10     8 ms    12 ms     6 ms  lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
 11     6 ms     6 ms     7 ms  24.105.30.129

Trace complete.

Years down the road:

Yessir, I was there for the 2019 WoW outage. Sure ‘nough lotta complainin and routes posted up and down the thread. Each side blamin’ the other one.

4 Likes

Like yourself. After that player connected to Blizzard, they were able to log in per usual, but when they weren’t using a VPN, then they couldn’t means that the VPN found a right path through the internet, and the other way didn’t. There are many different pathways through the internet simp-ly because its a self routing network.