Isn’t it about time we got some response from a blue?
1 Like
For Singapore players, seems like only M1 is affected
Starhub not affected, not sure about Singtel
Singtel isn’t affected too.
Got a few playing with me, none of the StarHub and SingTel subscribers are getting the issue. Though, one ViewQuest subscriber seems to be getting the same issue as me.
Server: Yojamba (OCE)
Country: Singapore
ISP: M1
Error code: WOW51900319 and WOW51900328
Can’t stay connected in game for over 10 seconds… Persisting the past 24 hours
seems like i need to buy another fibre subscription from either Starhub or Singtel, if i wanna continue my classic journey with my SG pals… haiz
exactly the same for me, from indonesia here.
I know people are bummed out. Blizzard is a victim here, just like us. It was Blizzard’s ISP(s) that were attacked. Whatever broke, or happened likely happened at the ISP level. Blizzard has no reason to block ISP ranges.
Some people can reach the data center and some cannot. It might take a bit for the ISP’s to get back to normal.
same here im using M1…
Yojamba same problem
This is so frustrating 
Internet Connection: Tethered
ISP: MetroPCS
Location: Oregon
Don’t have a VPN
Live
Get to realm selection, get the dreaded code and disconnected.
ISP: Verizon FIOS
Location: PA
Tried using VPN, but no luck.
Internet Connect: Wi-Fi/Hardlined
ISP:Spectrum
Location: California
vpn does not solve issue
connecting through t-mobile hotspot solves issue
issues persisting for 28 hours
Grampaswilly,
This did work for me. I am using Lutris + Linux Mint 19.1 and sure enough I can login now! Ty! I would have not guessed TTL (Time To Live) IP parameter would have been the fix.
Internet Connection: Wireless Broadband and Wired Broadband
ISP: Spectrum
Location: Ohio
Hotspot Shield and No VPN
Gets to “Logging into Game Server”, gets disconnect error code
3000 ms ping via battle.net looking glass
1 Like
Thank you thank you thank you.
That works on Arch as well. 
forever stuck at ‘logging in to game server’
then my connection will time out
edit:
turns out
sysctl net.ipv4.ip_default_ttl=128
fixed the issue for me
Also seeing the WOW51900328 error immediately after realm selection, for both ipv4 and ipv6.
- Internet connection: wired
- ISP: Wave (Seattle residential provider), aka Broadstripe or Vanoppen
- VPN: N/A
- Live vs Classic: I do not have Live/Retail installed
Edit: Operating system is emulated Windows 10 (qemu, using vfio/passthrough) with Debian v10/Buster as the host. Changing TTL values as recommended by other posters in both Windows and Debian resulted in an immediate success, though Windows should’ve been at 128 already.