8/19 - Stuck at Logging in to game server

Support Technical Support
82

vpn got me in.

83

tengo el mismo problema

84

9:18am EST: I have FiOS & wasn’t able to get past the ‘Logging into game server’ screen. After a few attempts, I managed to get to the character select screen & upon making my selection, got stuck on the loading screen about 80% of the way through. Closed out & tried again only to find myself stuck on the ‘Logging into game server’ screen again.

85

Can confirm turning on vpn worked

86

VPN worked for me as well. Thank you for the suggestion.

87

Hey all,

Thanks for the reports, we are looking into this now. Please feel free to post a traceroute ran to 24.105.30.129 to help us gather info. When posting the traceroute please select the entire post and hit the Preformatted text button (looks like </>) which should allow links.

We will post updates as they’re available.

Thanks!

Update: New Blizzard post requesting new traceroutes

8 Likes
89

Look at this dude

91

Same. Been having issues all weekend. Now I am unable to get past the login screen, or if I do everything is black. I’ve tried all the troubleshooting steps, and nothing has worked. When I DO get in, everything is frozen and cannot hearth/portal out of Orgrimmar. Even the portals in Pathfinder’s Den disappeared, so I could not get out that way either.

EDIT: realized I’m logged in under a different character but the realm I was having issues with is Anvilmar.

1 Like
92

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 13 ms 14 ms 12 ms 10.84.10.1
2 16 ms 19 ms 16 ms 126.0.32.70.hosted.by.gigenetcom [70.32.0.126]
3 14 ms 12 ms 12 ms po-10.csr1.iad.Servernapnet [66.252.6.64]
4 13 ms 15 ms 14 ms be4620.ccr41.iad02.atlas.cogentcocom [38.122.62.1]
5 14 ms 13 ms 14 ms 38.88.214.129
6 71 ms 103 ms 71 ms ae1-br01-eqdc2.as57976net [137.221.72.33]
7 71 ms 71 ms 70 ms et-0-0-2-br01-eqch2.as57976net [137.221.65.13]
8 77 ms 72 ms 70 ms 137.221.65.132
9 71 ms 71 ms 70 ms et-0-0-2-br01-eqla1.as57976net [137.221.65.68]
10 71 ms 71 ms 71 ms be1-pe02-eqla1.as57976net [137.221.68.69]
11 70 ms 70 ms 71 ms 24.105.30.129

Trace complete.

93

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 9 ms 10 ms 8 ms 24.105.30.129

Trace complete.

94

if you have had problems all weekend you might need to look into it further I have played at least a little everyday and have zero issues so you may have some computer issues as well or provider conflicts

95

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 4 ms 2 ms 2 ms 24.105.30.129

Trace complete.

96

Traceroute has started…

traceroute to 24.105.30.129 (24.105.30.129), 64 hops max, 72 byte packets
1 fios_quantum_gateway (192.168.1.1) 3.618 ms 6.114 ms 1.464 ms
2 24.105.30.129 (24.105.30.129) 8.287 ms 6.029 ms 6.612 ms

97

There were many in my guild having issues as well. I’ve never had this issue before, but I completed everything possible as far as troubleshooting. Some people in general chat were also having lag issues. It’s definitely not my computer…

3 Likes
98

Good to know it’s not just me that is experiencing this issue. Over the weekend, I had some major lag but so did everyone else. Lets hope Blizz can fix this. Maybe they are too excited bout classic and distracted from retail. Haha!

4 Likes
100

This is with CenturyLink/Embarq/whatever the DSL provider is called now…

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.0.1
2 28 ms 27 ms 28 ms 71-38-128-254.lsv2.qwest .net [71.38.128.254]
3 27 ms 27 ms 28 ms lsv2-agw1.inet.qwest .net [75.160.224.25]
4 29 ms 28 ms 28 ms 75-163-31-254.lsv2.qwest .net [75.163.31.254]
5 * * * Request timed out.
6 59 ms 34 ms 34 ms BLIZZARD-EN.ear3.LosAngeles1.Level3 .net [4.71.135.106]
7 38 ms 34 ms 34 ms ae1-br02-eqla1.as57976 .net [137.221.68.35]
8 37 ms 35 ms 33 ms be2-pe02-eqla1.as57976 .net [137.221.68.73]
9 35 ms 40 ms 34 ms 24.105.30.129

Trace complete.

1 Like
101 
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    <1 ms    <1 ms    <1 ms  10.250.1.1 
  3     1 ms     1 ms     1 ms  100.119.16.1 
  4     *        *        *     Request timed out.
  5     1 ms    <1 ms    <1 ms  100.100.1.99 
  6     1 ms     1 ms     1 ms  100.100.0.2 
  7     1 ms     1 ms     1 ms  208.95.183.254 
  8     1 ms     1 ms     1 ms  208.95.183.245 
  9    10 ms    11 ms    10 ms  10-2-4.ear1.Atlanta1.Level3.net [4.71.20.205]
102

Syracuse, NY - FiOS

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 4 ms 2 ms 2 ms 24.105.30.129

Trace complete.

I’m guessing for us Syracuse gamers that there is some MPLS in the way for the trace and it’s not stripping TTL from the packet

1 Like
103 
Aiken, SC
    
Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1 
  2     7 ms     7 ms     7 ms  10.158.0.1 
  3     8 ms     7 ms     7 ms  172.23.64.41 
  4    38 ms    45 ms    38 ms  24.105.62.129 

Trace complete.
1 Like
104

Tracing route to 137.221.105.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 1 ms 2 ms 1 ms 137.221.105.2