8/19 - Stuck at Logging in to game server

I’m on West coast nothing working

Microsoft Windows [Version 10.0.18362.295]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert 24.105.30.129

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     6 ms     6 ms  24.105.30.129

Trace complete.

C:\Windows\system32>

I am unsure if it’s related but I enabled IPv6 in game AND on my router(previously disabled) as soon as I did this I was able to log in no problem and am in game now.

Can someone else try testing this to see if it works?

Hello everyone,

Our network engineers continue to investigate the connectivity issues and we would like to request some fresh traceroutes using a different IP address.

Please feel free to run a new traceroute to 24.105.62.129 and post the results.

The more information we gather here the better, so it is very much appreciated. Thanks to everyone who has already helped out so far.

4 Likes

I posted the 137.221.105.2 tracer/path bc I’m west coast so it seemed more relevant.

Here’s the 24.105.30.129 one.

Tracert
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 32 ms 86 ms 69 ms boid-dsl-gw13.boid.qwest [184.99.64.13]
3 86 ms 68 ms 70 ms boid-agw1.inet.qwest [184.99.65.97]
4 37 ms 34 ms 46 ms sea-brdr-03.inet.qwest [67.14.41.154]
5 * * * Request timed out.
6 118 ms 86 ms 85 ms ae-2-3613.edge1.Seattle3.Level3 [4.69.160.73]
7 93 ms 120 ms 109 ms BLIZZARD-EN.edge1.Seattle3.Level3 [4.59.232.146]
8 103 ms 63 ms 53 ms ae1-br01-eqse2.as57976 [137.221.73.33]
9 106 ms 187 ms 93 ms xe-0-0-0-1-br01-eqsv5.as57976 [137.221.65.40]
10 * 47 ms 46 ms et-0-0-29-br02-eqsv5.as57976 [137.221.65.117]
11 69 ms 55 ms 118 ms xe-0-0-1-1-br02-eqla1.as57976 [137.221.65.6]
12 74 ms 93 ms 125 ms be2-pe01-eqla1.as57976[137.221.68.71]
13 122 ms 146 ms 101 ms 24.105.30.129

Trace complete.

Pathping
Tracing route to 24.105.30.129 over a maximum of 30 hops

0 StarPhish-PC.Home [192.168.0.2]
1 192.168.0.1
2 boid-dsl-gw13.boid.qwest [184.99.64.13]
3 boid-agw1.inet.qwest [184.99.65.97]
4 * sea-brdr-03.inet.qwest [67.14.41.154]
5 * 4.68.75.121
6 ae-2-3613.edge1.Seattle3.Level3 [4.69.160.73]
7 BLIZZARD-EN.edge1.Seattle3.Level3 [4.59.232.146]
8 ae1-br01-eqse2.as57976 [137.221.73.33]
9 xe-0-0-0-1-br01-eqsv5.as57976 [137.221.65.40]
10 et-0-0-29-br02-eqsv5.as57976 [137.221.65.117]
11 xe-0-0-1-1-br02-eqla1.as57976 [137.221.65.6]
12 be2-pe01-eqla1.as57976 [137.221.68.71]
13 24.105.30.129

Computing statistics for 325 seconds…

Go.
Outside.
:stuck_out_tongue:

how about no

4 Likes

It’s storming here, so no.

Okay I actually tested this a little more, if I disable IPv6 I can’t log in, but if it’s enabled I have no problem whatsoever.

Anyone else?

Hmm, that was supposed to be a reply to Kindheals and their bad lizard pun…

EDIT: I am also and have not been a blood elf in over a month… MUH IDENTITY!!!

Ok, I’m going outside.

This may not be a proper solution for everyone, as not everyone has IPv6 provisioned by their ISP.

1 Like

Outside WILL NOT LOAD… I get the message, “Transfer Aborted: instance not found”…and IT’S BAT COUNTRY OUTSIDE

5 Likes

When I copy the traceroute results it tells me that I can’t post links, any suggestions?

Thanks for (kind of) an update. Please don’t wait 7 hours before coming back to this thread with the next one, ok?

Representing the same issue in Syracuse as well with FiOS.

Nope didn’t work for me.

    Tracing route to 24.105.62.129 over a maximum of 30 hops

1 28 ms 1 ms 2 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 15 ms 16 ms 8 ms 24.105.62.129

Trace complete.

12 hours later…

4 Likes