8/19 - Stuck at Logging in to game server

I have had trouble all day long logging in or getting stuck at 80% loading, out of curiosity did any of you update elvui to version 11.21 that is when my login started happening, could be coincidence but I disabled all addons and logged in first try.

1 Like

lol. No, the ISPs don’t have direct connections to every site. It is a decentralized network. Meaning, one network connects to another, that connects to another, and so on. Only one needs to have an issue in the chain. Because the link isn’t actually down, the routers haven’t changed their route to bypass the bad segment. Traffic gets through, it’s just not a good enough connection for the game to work reliably.

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

  1     7 ms     1 ms     1 ms  192.168.100.1
  2     5 ms     5 ms     5 ms  225.4.46.186.static.anycast.cnt-grms.ec [186.46.4.225]
  3    12 ms     6 ms     6 ms  190.152.252.153
  4    61 ms    63 ms    61 ms  10.9.2.29
  5    61 ms    61 ms    61 ms  10.9.2.29
  6   103 ms    97 ms    95 ms  mai-b1-link.telia.net [62.115.58.177]
  7    99 ms    98 ms     *     atl-b24-link.telia.net [62.115.113.48]
  8     *      101 ms    96 ms  atl-b22-link.telia.net [62.115.113.24]
  9   109 ms   109 ms   109 ms  chi-b21-link.telia.net [62.115.113.19]
 10   108 ms   109 ms   108 ms  blizzard-ic-348622-chi-b21.c.telia.net [62.115.178.249]
 11   108 ms   108 ms   110 ms  ae1-br02-eqch2.as57976.net [137.221.69.35]
 12    96 ms    97 ms    97 ms  be2-pe02-eqch2.as57976.net [137.221.69.73]
 13   108 ms   108 ms   109 ms  chi-eqch2-ia-bons-04.as57976.net [137.221.66.15]
 14   103 ms   108 ms   110 ms  24.105.62.129

Trace complete.
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     1 ms     1 ms    <1 ms  192.168.0.1
  3     4 ms     4 ms     4 ms  hlrn-dsl-gw05.hlrn.qwest.net [207.225.112.5]
  4     4 ms     4 ms     5 ms  63-225-124-33.hlrn.qwest.net [63.225.124.33]
  5     4 ms     5 ms     5 ms  dvr3-brdr-01.inet.qwest.net [208.168.152.134]
  6     5 ms     5 ms     5 ms  63-235-41-90.dia.static.qwest.net [63.235.41.90]
  7     *        *        *     Request timed out.
  8    22 ms    21 ms    25 ms  BLIZZARD-EN.ear3.Dallas1.Level3.net [4.15.45.54]
  9    32 ms    31 ms    31 ms  ae1-br01-eqda6.as57976.net [137.221.74.33]
 10    32 ms    32 ms    32 ms  et-0-0-4-br01-eqch2.as57976.net [137.221.65.38]
 11    31 ms    32 ms    31 ms  be1-pe01-eqch2.as57976.net [137.221.69.67]
 12    39 ms    32 ms    33 ms  24.105.62.129

Trace complete.

Everything is working normally as it should now for me. I believe the issue is fixed for ME at the least.

yay i was able to get on again!! big thanks!!!

I have successfully connected, a bit laggy but was able to use my hearthstone

good, I can turn on my addons again lol what timing…

Just got in and everything seems to be working so far… I guess blizz finally reset the router. lol

Listen, it’s pretty obvious this was a Blizz issue. I use Sprint mobile hotspot and was kicked earlier this morning from the game. I have been offline for every bit of 9 hours and it JUST came back online so I got in. Simple…Blizz found the issue and fixed it. Easy.

I just got in too, seems like everything is ok for now.

Yes, its back to normal i guess, cheers

Seems to be back to normal…SLC, UTAH…Centurylink

Thank You Blizzard, for your diligence with this situation. Even though it has been 10 hours since the beginning of the down time, I can now log in and interact with things - for now that is. gg

From a loyal Blizz fan since 1994, I have the Original box 10ft away from me right now.

JOY! Thanks Blizz, I’m in and all is working as normal :smiley:

Just an update.

My ISP Centurylink has fixed the issue as of 3PM PST. Idk if it helps to know that but the more info the better right?

Thanks, Blizz!

1 Like

As Graar pointed out in his post, the pointing to the ISP does not necessarily mean it will be on your end, but on their end where they may not have much control other than they have a connection.

A degraded internet connection can happen anywhere and whether or not there are redundant routes to get to the point in question.

The current internet protocol is about packets being sent with some data, wait for acknowledgement, send more or doing a request, receive, acknowledge receipt and request for more.

Think of it like taking Dictation over the phone. If someone is saying something and you are writing/typing it down, but suddenly, there are bursts of sounds or distractions, you will not get everything that was said. Now normally, you would tell the person “Can you repeat what you said here?” But if that person didn’t hear that and kept going on, you are going to have problems getting the statement down properly.

So in the case of Blizzard, if their ISP for one of their data centers is acting up, it is basically that case, except the internet is not just a 1 to 1 connection. When you look at the traceroute requests, there are ‘hops’ or ‘relays’. Hops near you won’t be affected, but hops closer to where they are maybe, which can cause problems with your connection to them, but not with other places.

1 Like

Oregon > Seattle > Netherlands > Kansas
¿¿¿Netherlands why???
(137.221.73.33 is NL)

Hey all,

We made another modification a few minutes ago to try to get affected players off of the overloaded backbone provider that was causing the issue. How are things for you all now? If it’s not immediately improved, sit tight for a few minutes - sometimes when we make a change like this it takes a bit for ISPs to pick up the modification.

2 Likes