We don’t have time for conspiracy theories, it’s BG week!
When next year? this is a joke sorry and a embarrassment to Blizzard pathetic to be honest.
You’re customer support? Really? Looks like Blizz needs to rethink that.
13 Likes
Blizzard… I cannot get past your message, “Logging in to game server”…
Isn’t that spelled wrong, shouldn’t that be “Logging INTO game server”?
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 9 ms 7 ms 7 ms 24.105.30.129
Trace complete.
This classic experience is going to be extremely authentic.
7 Likes
Depends whether the verb is “log” or “login” - but you can’t “logining to game server”. I don’t think there is a good grammar rule ;).
East coast here, haven’t been able to log in since 10am. Finally my loading screen finished but now that I’m in, everything is broken. Action bars aren’t right, no one around, can’t move, latency at 0, even screen resolution is wack.
The EST servers had information that could lead to the arrest of the Clintons.
5 Likes
It’s a backbone problem. Blizz’s servers connect to the Level3 backbone, and there’s a problem with connections between Level3 and various ISP’s. A VPN will get you on to play by bypassing the trouble spot, but I’d be cautious of any free offerings. I personally use NordVPN, and it works quite well.
1 172.16.1.1 (172.16.1.1) 1.861 ms 1.078 ms 1.019 ms
2 * * *
3 ae1323-21.phlapalo-mse01-aa-ie1.verizon-gni.net (100.41.20.62) 10.235 ms 8.318 ms
ae1323-20.ftwspafw-mse01-aa-ie1.verizon-gni.net (100.41.20.64) 9.414 ms
4 0.et-10-1-2.br2.nyc4.alter.net (140.222.235.119) 12.267 ms 8.472 ms 26.471 ms
5 192.205.34.49 (192.205.34.49) 12.863 ms 17.527 ms 7.964 ms
6 cr1.n54ny.ip.att.net (12.122.131.102) 8.244 ms
cr2.n54ny.ip.att.net (12.122.130.170) 14.920 ms 12.343 ms
7 12.122.115.113 (12.122.115.113) 7.379 ms 8.733 ms
12.122.115.85 (12.122.115.85) 8.029 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 *Imagine this for classic lmao! logging into Classic WoW YES! Disconnected from server SCREAMS INTERNALLY
Fake News!
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 5 ms 2 ms 2 ms my.jetpack [192.168.1.1]
2 42 ms 26 ms 27 ms 225.sub-66-174-43.myvzw.com [66.174.43.225]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 34 ms 37 ms 31 ms 242.sub-69-83-107.myvzw.com [69.83.107.242]
7 30 ms 29 ms 30 ms 138.sub-69-83-107.myvzw.com [69.83.107.138]
8 44 ms 37 ms 41 ms 28.sub-69-83-99.myvzw.com [69.83.99.28]
9 36 ms 26 ms 31 ms 28.sub-69-83-99.myvzw.com [69.83.99.28]
10 35 ms 32 ms 27 ms 21.sub-69-83-98.myvzw.com [69.83.98.21]
11 36 ms 30 ms 30 ms et-2-0-0.GW1.MEM3.ALTER.NET [204.148.39.1]
12 55 ms 45 ms 34 ms 0.ae1.BR3.ATL4.ALTER.NET [140.222.225.165]
13 48 ms 39 ms 41 ms 204.255.168.254
14 49 ms 47 ms 47 ms cr1.attga.ip.att.net [12.122.141.182]
15 49 ms 39 ms 40 ms gar18.attga.ip.att.net [12.122.96.89]
16 55 ms 42 ms 39 ms 12.247.68.74
17 * * * Request timed out.
18 * 62 ms * et-0-0-4-br02-eqch2.as57976.net [137.221.65.46]
19 55 ms 53 ms 50 ms be2-pe02-eqch2.as57976.net [137.221.69.73]
20 61 ms 47 ms 51 ms 24.105.62.129
Trace complete.I just got in!
I think you may have missed where my use “incompetent” came from.
It wasn’t referring to Delaiya’s conclusion itself. It was referring Delaiya’s assertion of Bliz’s incompetentance
See the post I replied to.
1 Like
Its Spinal?!
1 Like
Been happening since 8:00 A.M. Must be more major than we know. Still no post from Blizzard for over 2 hours on Twitter.
I’m fairly certain that it used to be “into” I just noticed the difference today, due to the fact that I’ve been staring at that message most of this morning.
1 Like
Here’s another hypothetical
WHY am I able to log in to blizzard battlenet then open the PTR and play on that ?
I’m using the same internet.
Seems to me its a problem with blizzard.
5 Likes