I just tried logging into B.net to access HearthStone and I got this generic message ''Its a busy day for Blizzard services ... blahblahblah .. estimated wait time 170 minutes'' ...
Is there a special event or something going on or is Battle.net Client/Server simply down?
Edit : By the time I was done with the post - no time at all - my estimate went up to 208min
Hearthstone
•
Posted by
Horus
•
Created 6 years, 5 months ago
•
Updated 6 years, 5 months ago
•
Discussion
17 comments
814 views
Comments
I just tried logging into B.net to access HearthStone and I got this generic message ''Its a busy day for Blizzard services ... blahblahblah .. estimated wait time 170 minutes'' ...
Is there a special event or something going on or is Battle.net Client/Server simply down?
Edit : By the time I was done with the post - no time at all - my estimate went up to 208min
I can't get in on the Android app for hearthstone. Says wait time is 15 minutes but it never changes.
20 minutes later, I'm now up to an estimate wait time of 295 min ...
And here goes my game time ..!
I cant get in, wait time 230 minutes. I wish they would announce something.
They just did announce something on twitter :
https://twitter.com/BlizzardCS/status/1137046311117762560
540 here, LUL.
There is a message up on the launcher, they know of the issue.
This is a weird place to put this comment, but it's the first time I've noticed: your sig identifies you as the site founder. You need to change your user tag from, "Admin" to, "Founder"! Or perhaps, "Lord of No Cards," or something.
Am I supposed to work at work or something? WTF
LMFAO same here Geist.
Just made it a step further ; now logged on B.net, but B.net doesn't recognize any connection ...
Offline and attempting to reconnect every 60 sec
#Classiclaunchfeels
How can I poop without HS. Guess I’m stuck in this stall at work until Blizzard fixes this
This going to be a looooong day ^^
wow the League of Evil has taken it too far with going after a takeover of Blizzard's servers. Flavor win though blizzard.
This is one hella long server issue. Blizzard move your ass get it fixed.
Meanwhile, at Blizz HQ : ''This is fine ...oh, not just yet... how about now? ... ''
7 1/2 billion people on Earth. Odds are some of them are going to be shitty. Damn DDOS attack.
So it only took 4 hours before things were figured and the client was responsive again.
This thread is now obsolete (until next server's crash)