8/19 - Stuck at Logging in to game server

Astae-durotan · August 19, 2019, 9:17pm

Been awhile since I’ve run into this problem. It’s probably a pipeline issue somewhere, as Blizzard doesn’t own the entire connection between the servers and each of us. The question needing to be asked is if there are any outages or service problems with other providers along the route. It could also be a communications or protocol issue between providers, for all I know, however.

The thing is, this isn’t the first time I’ve seen this or had this happen to me, and it’s not unique to Fios, but other providers at various times.

Fähëd-azralon · August 19, 2019, 9:18pm

Same issue here. From Brazil.

Eyenstein-azshara · August 19, 2019, 9:19pm

East Coast, South Eastern US … issue persists

Azelda-area-52 · August 19, 2019, 9:19pm

Yay I can log in and play… somewhat laggy but working - Area 52

Brodee-hyjal · August 19, 2019, 9:19pm

was getting stuck at 75 percent load in i closed and retried got server selection and pick alt server and got in

Bellivia-area-52 · August 19, 2019, 9:19pm

I have not been able to log in since like 1 p.m Eastern time, still cannot

Fancyfix-dentarg · August 19, 2019, 9:20pm

So, I quit b/net, and started up again. Was able to login, but not able to do anything, couldn’t mount, couldn’t interact, no players moving, etc.
So then tried again, now stuck back at the loading screen …
STILL DEAD!

Elibourne-sargeras · August 19, 2019, 9:20pm

Ya I did a whois on it also…
inetnum: 137.221.64.0 - 137.221.95.255
netname: BLIZZARD
country: NL
admin-c: BP5978-RIPE
tech-c: BP5978-RIPE
status: ASSIGNED PA
mnt-by: MNT-BLIZZARD
created: 2018-08-27T19:57:32Z
last-modified: 2018-08-27T19:57:32Z
source: RIPE

Zephyy-thunderlord · August 19, 2019, 9:20pm

Yar. /10chars

Foosaka-ragnaros · August 19, 2019, 9:21pm

uuf, my trace is going from Buenos Aires to Miami, then across seas to the Netherlands and back to the US. Really effective route, what’s 14000 Km of useless jumping right?

 Traza a 24.105.62.129 sobre caminos de 30 saltos como máximo.

1     1 ms     1 ms     1 ms  192.168.0.1
2     *        *        *     Tiempo de espera agotado para esta solicitud.
3     *        *        *     Tiempo de espera agotado para esta solicitud.
4     *        *        *     Tiempo de espera agotado para esta solicitud.
5    26 ms    29 ms    29 ms  150-165-89-200.fibertel.com.ar [200.89.165.150]
6    23 ms    23 ms    23 ms  ae6.baires3.bai.seabone.net [185.70.203.22]
7   151 ms   151 ms   152 ms  et0-1-0.miami19.mia.seabone.net [89.221.41.171]
8   152 ms   152 ms   154 ms  be6762.ccr21.mia03.atlas.cogentco.com [ 154.54.9.17]
9   155 ms   154 ms   159 ms  be3401.ccr22.mia01.atlas.cogentco.com [154.54.47.29]
10   159 ms   154 ms   152 ms  be3411.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.26.42]
11   154 ms   153 ms   153 ms  te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42]
12   149 ms   150 ms   151 ms  gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
13     *        *        *     Tiempo de espera agotado para esta solicitud.
14     *        *        *     Tiempo de espera agotado para esta solicitud.
15     *      183 ms   182 ms  et-0-0-4-br02-eqch2.as57976.net [137.221.65.46]
16   185 ms   181 ms   183 ms  be2-pe02-eqch2.as57976.net [137.221.69.73]
17   182 ms   181 ms   179 ms  chi-eqch2-ia-bons-04.as57976.net [137.221.66.15]
18   184 ms   183 ms   185 ms  24.105.62.129

Ryanherald-zuljin · August 19, 2019, 9:21pm

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.43.1
2 24 ms 18 ms 18 ms 129.sub-66-174-15.myvzw. com [66.174.15.129]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 25 ms 20 ms 19 ms 50.sub-69-83-25.myvzw. com [69.83.25.50]
7 25 ms 31 ms 18 ms 194.sub-69-83-25.myvzw. com [69.83.25.194]
8 28 ms 23 ms 24 ms 172.sub-69-83-18.myvzw. com [69.83.18.172]
9 33 ms 24 ms 22 ms 172.sub-69-83-18.myvzw. com [69.83.18.172]
10 25 ms 17 ms 19 ms 101.sub-66-174-9.myvzw. com [66.174.9.101]
11 25 ms 28 ms 29 ms et-1-0-0.GW1.PHL24.ALTER. NET [204.148.66.1]
12 35 ms 28 ms 28 ms 0.et-10-0-2.BR2.NYC4.ALTER. NET [140.222.1.61]
13 27 ms 26 ms 30 ms 192.205.34.49
14 38 ms 27 ms 35 ms cr2.n54ny.ip.att. net [12.122.130.170]
15 34 ms 28 ms 32 ms 12.122.115.113
16 37 ms 88 ms 30 ms 12.246.51.34
17 52 ms 44 ms 55 ms ae1-br01-eqny8.as57976. net [137.221.71.33]
18 * 81 ms 47 ms et-0-0-2-br02-eqch2.as57976. net [137.221.65.8]
19 51 ms 48 ms 48 ms be2-pe02-eqch2.as57976. net [137.221.69.73]
20 57 ms 48 ms 47 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
21 51 ms 48 ms 48 ms 24.105.62.129

Trace complete.

Pennsylvania here

Rambam-jaedenar · August 19, 2019, 9:21pm

[goodgulf six:~] gurman% traceroute 24-105-62-129
traceroute to 24-105-62-129 (24-105-62-129), 64 hops max, 52 byte packets
1 192-168-2-254 (192-168-2-254) 0-844 ms 0-515 ms 0-539 ms
2 * * *
3 b3330-washdc-lcr-21-verizon-gni-net (130-81-27-0) 9-245 ms
b3330-washdc-lcr-22-verizon-gni-net (130-81-27-2) 9-236 ms 10-092 ms
4 * * *
5 0-ae1-br1-iad8-alter-net (140-222-239-77) 10-210 ms 9-131 ms
0-ae2-br1-iad8-alter-net (140-222-239-79) 10-388 ms
6 192-205-36-137 (192-205-36-137) 12-096 ms 12-450 ms 11-819 ms
7 cr81-wshdc-ip-att-net (12-122-134-150) 12-446 ms 12-197 ms
cr82-wshdc-ip-att-net (12-122-135-182) 15-019 ms
8 cr2-wswdc-ip-att-net (12-122-134-94) 19-525 ms
cr82-wshdc-ip-att-net (12-122-135-174) 12-128 ms 12-203 ms
9 12-122-135-230 (12-122-135-230) 20-111 ms
cr1-cl2oh-ip-att-net (12-122-116-2) 12-304 ms
12-122-135-230 (12-122-135-230) 19-485 ms
10 12-122-135-237 (12-122-135-237) 10-126 ms 9-150 ms
12-122-135-241 (12-122-135-241) 10-267 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *

----and so on (all “.” characters replaced by “-” because the forum + my browser evidently think anything with a “.” is a URL)

Taeldoriàn-stormrage · August 19, 2019, 9:22pm

Still unable to log in. From Vermont, Verizon is my provider

Matrixwolf-dalaran · August 19, 2019, 9:22pm

California still dead

Tieriana-ysera · August 19, 2019, 9:22pm

Utah still dead

Ilkarnu-fizzcrank · August 19, 2019, 9:23pm

Thank you for resolving

anon24643563 · August 19, 2019, 9:23pm

Thought it was just east coast… West coast has been down as well?

Kielo-medivh · August 19, 2019, 9:23pm

Was unable to get past the character log-in pretty much all day. The load bar just froze at about 70-80%. Finally got a character launched in game, but I can’t interact with anything. I can see other player characters and npcs, and move. But there are no daily quest !'s , nothing is clickable, and casting spells does nothing. And even though I am running around, my character icon says I am sleeping. ZZzzzzz. I am on Verizon, but it’s old DSL, not FIOS.

Fancyfix-dentarg · August 19, 2019, 9:23pm

Problem is NOT RESOLVED

Zaarm-malganis · August 19, 2019, 9:25pm

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1] 
  2     3 ms     3 ms     3 ms  stpl-dsl-gw19.stpl.qwest.net [207.109.2.19] 
  3     3 ms     3 ms     3 ms  stpl-agw1.inet.qwest.net [207.109.3.145] 
  4     3 ms     3 ms     3 ms  216-160-19-2.mpls.qwest.net [216.160.19.2] 
  5     *       12 ms    12 ms  ae-1-3508.ear7.Chicago2.Level3.net [4.69.142.174] 
  6    31 ms    12 ms    12 ms  BLIZZARD-EN.ear7.Chicago2.Level3.net [4.7.196.134] 
  7    27 ms     *       13 ms  ae1-br02-eqch2.as57976.net [137.221.69.35] 
  8    12 ms    12 ms    12 ms  be2-pe02-eqch2.as57976.net [137.221.69.73] 
  9    14 ms    14 ms    14 ms  24.105.62.129 

Trace complete.