8/19 - Stuck at Logging in to game server

[Turnberry-illidan (Turnberry)]

@Wastedwizard-kelthuzad

Not all vpns are working, which one are you using?

I have PrivateInternetAccess VPN

[Threewolves-dentarg (Threewolves)]

I wouldn’t post tracing route info even if I have to play some other mmo. Hackers can glean info from too many sources.

[Maliciousmal-sargeras]

Insert cookie cutter response “here”

[Betalucecita-ragnaros]

VPN free is a risk. A high risk at least if you have credit cards, home banking, etc. in your PC.

[Stalwartdino-dalaran]

Also can confirm my connection is working with vpn, but damn this latency

[anon24643563]

I just want my 1000 pets back when i can log back in…Keep up the fight Blizz!

[Fairladyz-destromath]

@Mirasol-mannoroth

So how long are you guys gonna keep pushing “it’s a routing issue” lie?

You seem very put out that you can’t play. I am sorry for that. I will stop saying that routing is probably a part of the issue when turning on VPNs does not work. A VPN is a detour around a bad section of “road” on the way to and end destination. The detour does not work if the end server is down/not functional. It does work though, which means the servers themselves are accepting connections and playable - if you can get to them.

I was able to log in after turning on my VPN. Switch them on boys.

He’s just mad he can’t login and boost his gear and ilvl so he can fulfill his insecurities that he doesn’t have irl.

[Wastedwizard-kelthuzad]

what vpns are working? I tried using Psiphon 3, but im getting the same issue.

[Healgasm-gilneas]

I’m not sure if this will help anyone else, but I changed my DNS server to 1.1.1.1 from google’s (8.8.8.8) and rebooted and the issue was resolved(Centurylink DSL) Might be worth a try
Scratch that about to be lagged off, never mind

[Aurabelle-exodar]

  Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  modem.domain [192.168.0.1] 
  2    23 ms    23 ms    23 ms  slcy-dsl-gw12.slcy.qwest.net [207.108.176.12] 
  3    23 ms    23 ms    23 ms  slcy-agw1.inet.qwest.net [207.108.177.89] 
  4    23 ms    24 ms    24 ms  207-108-179-2.slkc.qwest.net [207.108.179.2] 
  5     *        *        *     Request timed out.
  6    37 ms    37 ms    37 ms  BLIZZARD-EN.ear3.LosAngeles1.Level3.net 
[4.71.135.106] 
 7  1420 ms   218 ms   111 ms  ae1-br01-eqla1.as57976.net [137.221.68.33] 
 8    69 ms    72 ms    69 ms  et-0-0-2-br01-swlv10.as57976.net [137.221.65.69] 
 9    90 ms    70 ms    69 ms  137.221.65.133 
10    69 ms    69 ms    69 ms  be1-pe01-eqch2.as57976.net [137.221.69.67] 
11    70 ms    70 ms    69 ms  24.105.62.129 

Trace complete.

[Groneta-area-52]

I use cyberghost and it worked logged out again and reloaded

[Laithus-bleeding-hollow]

This is clearly a blizz issue all my blizzard games all the sudden are going crazy. Not login in or working properly. I"ve done all the troubleshooting there is and nothing fixes it. And the game was working fine at 6am East time. After the morning hours mad people started getting the issue so it has to be something on their end.

[Rambam-jaedenar]

Verizon’s fibre optic network, available to business and residential customers in certain urban and surrounding suburban areas in the US.

[Graar-icecrown (Graar)]

@Mirasol-mannoroth

@Maliciousmal-sargeras

So how long are you guys gonna keep pushing “it’s a routing issue” lie?

You seem very put out that you can’t play. I am sorry for that. I will stop saying that routing is probably a part of the issue when turning on VPNs does not work. A VPN is a detour around a bad section of “road” on the way to and end destination. The detour does not work if the end server is down/not functional. It does work though, which means the servers themselves are accepting connections and playable - if you can get to them.

@Turnberry-illidan

I was able to log in after turning on my VPN. Switch them on boys.

Mirasol is absolutely correct. Even if they did steal the analogy I was going to use.

When you force a route change by using a VPN and the issue goes away, you have definitively proven that this is not a server issue. They need the traces to identify the bad segment. Unfortunately traffic doesn’t stop entirely, just become erratic which is much more difficult to locate. I have done systems and networking admin for 25 years, and issues like this were not uncommon in the late 90s. There is a good chance that a fiber line got clipped by a backhoe or something.

[Kiltrine-dalaran]

Adding my Tracert to the mix from the DC area.

Tracing route to 24.105.62.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     7 ms     9 ms     6 ms  24.105.62.129 

Trace complete.

[Ugluck-bleeding-hollow]

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  modem.domain [192.168.0.1]
  2     2 ms     2 ms     2 ms  hlrn-dsl-gw02.hlrn.qwest.net [207.225.112.2]
  3     3 ms     3 ms     1 ms  63-225-124-9.hlrn.qwest.net [63.225.124.9]
  4     3 ms     2 ms     3 ms  dvr3-brdr-01.inet.qwest.net [208.168.152.134]
  5     2 ms     2 ms     4 ms  63-235-41-90.dia.static.qwest.net [63.235.41.90]
  **_6    20 ms    17 ms    19 ms  ae-7-0.ear3.Dallas1.Level3.net [4.69.210.149]_**
  7    18 ms    18 ms    18 ms  BLIZZARD-EN.ear3.Dallas1.Level3.net [4.15.45.54]
  8    40 ms    38 ms    38 ms  ae1-br02-eqda6.as57976.net [137.221.74.35]
  9    37 ms    38 ms    39 ms  et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
 10    37 ms    37 ms    38 ms  137.221.65.122
 11   273 ms   219 ms   173 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
 12    38 ms    36 ms    37 ms  be1-pe02-eqla1.as57976.net [137.221.68.69]
 13    37 ms    38 ms    39 ms  24.105.30.129

The IP 4.69.210.149 router seems to be the issue. Seems to have been a previous issue back in 2018

[Eyenstein-azshara]

For what it’s worth, I have also been watching YouTube all day with no issues. My email, social media, and regular connectivity are not effected. Only WoW.

[Graar-icecrown (Graar)]

I’m using the one built in to Dashlane. Not sure about others tested. You could try changing your datacenter endpoint if you have that option. That could help.

[Mybübbles-zuluhed]

Used a private VPN from a work office a couple cities over, but in the same state (WA), and it worked. Here’s a tracert from that:

1 * * * Request timed out.
2 * * * Request timed out.
3 12 ms 15 ms 11 ms ae9—0.car01.evrt.wa.frontiernet. net [74.40.70.61]
4 13 ms 12 ms 13 ms ae3—0.cor02.sttl.wa.frontiernet. net [74.40.1.101]
5 11 ms 15 ms 10 ms ae1—0.cbr01.sttl.wa.frontiernet. net [74.40.5.126]
6 12 ms 11 ms 12 ms eqix-se2.blizzardentertainment. com [198.32.134.68]
7 59 ms 78 ms 59 ms ae1-br02-eqse2.as57976. net [137.221.73.35]
8 57 ms 56 ms 57 ms xe-0-0-1-1-br02-eqch2.as57976. net [137.221.65.42]
9 58 ms 58 ms 57 ms be2-pe02-eqch2.as57976. net [137.221.69.73]
10 61 ms 61 ms 61 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
11 59 ms 63 ms 59 ms 24.105.62.129

Alternatively, here was the tracert again from my other office:

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 3 ms 3 ms 4 ms [redacted]
2 2 ms 3 ms 2 ms [redacted]
3 4 ms 6 ms 6 ms sea-brdr-03.inet.qwest. net [67.14.41.150]
4 6 ms 6 ms 4 ms 4.68.75.121
5 5 ms 4 ms 6 ms ae-2-3613.edge1.seattle3.level3. net [4.69.160.73]
6 5 ms 6 ms 4 ms blizzard-en.edge1.seattle3.level3. net [4.59.232.146]
7 * * * Request timed out.
8 * * 52 ms xe-0-0-1-1-br02-eqch2.as57976. net [137.221.65.42]
9 53 ms 51 ms 52 ms be2-pe02-eqch2.as57976. net [137.221.69.73]
10 54 ms 53 ms 53 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
11 53 ms 54 ms 56 ms 24.105.62.129

Edit: There are a lot of tracert’s that involve Level3 - worth investigating. Seattle router uses CenturyLink and routes through the Level3 Blizzard server, Bellevue router (via VPN to that office) uses Frontier and does not go through Level3. In searching the posts on here, hundreds appear to be routing through Level3. Not all of them, but a large chunk.

[Cntrldfision-borean-tundra (Cntrldfision)]

traceroute to 24.105.62.129 (24.105.62.129), 64 hops max, 52 byte packets
1  192.168.1.1 (192.168.1.1)  1.333 ms  0.916 ms  1.603 ms
2  10.1.240.1 (10.1.240.1)  10.178 ms  6.857 ms  8.109 ms
3  host-24-246-128-77.com.morrisbb.com (24.246.128.77)  7.856 ms  8.133 ms  7.372 ms
4  207.144.87.33 (207.144.87.33)  9.891 ms  19.330 ms  8.068 ms
5  bldw-mlx-sprt-mlxe8-roadm-ss.skybest.com (69.77.128.233)  8.790 ms  10.309 ms  9.066 ms
6  xe-8-3-2.bar2.raleigh1.level3.net (4.71.162.193)  13.177 ms  13.216 ms *
7  ae-1-3514.edge2.atlanta4.level3.net (4.69.150.197)  18.067 ms  18.292 ms  16.740 ms
8  * * *
9  * * *
10  * * *

and it goes on from there