Comic relief…
hxxps://imgur.com/PaVjBtr
Unable to login due to this error, wow51900328, since yesterday, 9-9-19. Any ideas?
theres a ton of ideas…spent all day trying everyones input. i still cant get in and its on blizz’s end to fix. but gl!
you getting the same error?
yes, i can get to realm selection screen, click my realm and a min or so i DC with (WOW51900328)…I can like many others get on an oceanic server but, that doesnt help me at all and im sure doesnt answer anything for ya, im lost as everyone else on this one
I resigned to attempt to get into my chosen server about 70 times tonight. I wanted to do 100 if necessary but am getting so sleepy, it’s been a long day at work. You know the tune, i’m sure.
Around the 13th attempt I actually got into my character selection but each time I tried to go into the realm the loading would freeze about 70% of the way and then I’d be put back into the character selection. A message came up saying “World Server Down”. On my fourth attempt to get the character into the game I was kicked out to the log in window again. I thought maybe I’d get back in if I was patient enough but after the 70th attempt I need sleep. I never did get back to the character screen.
Country: Singapore
ISP: Starhub
Connection to Oceanic Servers are fine.
Connection to US servers 137.221.105.2 (US West) & 24.105.62.129 (US Central) are not since the DDOS attacks.
It also appears Blizzard are now rerouting connections from US to netherlands and then back to the US based on the WinMTR tests performed when the connections have reached Blizzard from my ISP.
If so, this is not something my ISP can help with and you need to fix whatever routing changes you have made internally since the DDOS attacks.
That was 3 days ago…how long am I supposed to wait and try again later?
Since it started Saturday this is now Day 5 of not being able to play.
Blizz needs to get their poop together on this one.
i agree i still cant get into game.
If you have tried the VPN…it works for me…but does it not seem stupid that I can not connect to a server in CA directly…but if i send my signal to Brasil first and then there…it works…
And it has been five days now and even from day one Blizzard has been so absent…they had their little tweets but not much else…and still not much else…
The Customer Service and Tech Support has always been horrible and absent…
yet again still getting the same error code after being disconnected trying to get into my server. for a company that keeps claiming they have fixed everything and alot of people have had this same issue im not overly sure what u have fixed. i have done all your silly suggestions and no change. please explain to me what exactly you have fixed??
Care to explain why everyone can log in?
You’ll wish to follow through with troubleshooting in Tech Support. This isn’t a CS issue
1 Like
Still having this issue. Can get through login server fine. Cannot log in to an ACTUAL SERVER.
I haven’t been able to log in since sunday
tried today and im in!
Under rules I bypass PPTP Sessions, Destination 1723, Protocol TCP.
The VPN runs over OpenVpn version 2.4.7 using TCP and SHA256 for encryption on both incoming and outgoing channel, and 2048 bit RSA for the control channel using TLS V1.2
I do not see any bypassed sessions in Untangle, so I doubt it is bypassing the rules, and I only have 4 rules set as bypass. It should not be able to bypass application processing in Untangle.
I should add under Untangle I use fair/flow queueing + Codel (fq_codel) to minimize bufferbloat.
But I DO have unlimited data and AM trying to tether to connect. That’s how I generally play because I travel to work and don’t want to pay for a home ISP when I’m only there 7 days out of a month.
I am able to connect via a vpn, but don’t feel like paying for one and free ones I’ve found have anywhere from 600ms-1800ms latency. 600 is doable for questing and whatnot in classic, 800+ starts to really cut in and anything that’s GCD or longer and I may as well just auto-attack or wand everything to death.
Sounds to me like they banhammered every IP that was connected during DDoS and are SLOOWLY removing legit players from their lists. This is what makes sense with reports that GMs were able to temporarily restore players with nothing more than a character and realm name.
I WILL GLADLY PERFORM SEXUAL FAVORS (IN-GAME OR ELSE THIS WOULD PROBABLY BE ILLEGAL IN SOME CAPACITY) AS PAYMENT FOR THIS INFORMATION! THANK YOU GOOD SIR, YOU DESERVE THE GM’s SALARIES FOR HAVING DONE THEIR JOB MORE EFFECTIVELY THAN THEY ARE DEMONSTRABLY CAPABLE!
AT&T is failing a LOT of packets with World of warcraft. It has nothing to do with WoW themselves. Not only are they failing via wireless, they’re failing via Uverse/DSL and any of the above, it’s something on their server end that a lot of people are having issues with. This isn’t a WoW issue per sae…more so AT&T dropping world of warcraft data packets at an obscene rate.
Also to not stray off topic: this is my WinMTR
Internet provider: AT&T Wireless through Cricket
Locale: Eastern Tennessee
VPN: Yes, running through Proton VPN. (Express VPN was having the same issues so i changed VPN services)
No ability to use a standard broadband
Server type: WoW Classic - US Westfall
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 10.8.0.1 | 4 | 29 | 28 | 130 | 1331 | 4170 | 304 |
| 66.115.173.174 | 4 | 29 | 28 | 129 | 1345 | 4170 | 305 |
| 216.201.90.106 | 4 | 29 | 28 | 133 | 1333 | 4170 | 305 |
| hu0-12-0-7.ccr41.atl04.atlas.cogentco.com | 4 | 29 | 28 | 117 | 1349 | 4170 | 305 |
| be2788.ccr22.atl02.atlas.cogentco.com | 4 | 29 | 28 | 116 | 1352 | 4170 | 306 |
| 192.205.36.237 | 8 | 25 | 23 | 184 | 1573 | 4155 | 305 |
| cr1.attga.ip.att.net | 0 | 31 | 31 | 206 | 1389 | 4245 | 317 |
| nsvtn22crs.ip.att.net | 0 | 31 | 31 | 222 | 1388 | 4205 | 316 |
| cl2oh21crs.ip.att.net | 4 | 29 | 28 | 206 | 1372 | 4248 | 334 |
| cgcil21crs.ip.att.net | 4 | 29 | 28 | 206 | 1371 | 4244 | 334 |
| cr1.cgcil.ip.att.net | 8 | 25 | 23 | 221 | 1499 | 4202 | 323 |
| 32.130.248.132 | 4 | 29 | 28 | 221 | 1365 | 4202 | 334 |
| 32.130.248.163 | 8 | 25 | 23 | 221 | 1505 | 4202 | 323 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 11 | 0 | 0 | 0 | 0 | 0 |
I found success by fully uninstalling and reinstalling battlenet