Hey Zoey,
Your commander levels are covered under this thread: [Main Thread] - Commander Levels Reset - #131 by Kaldraydis
I too work in IT, and if a service is down for days on end, people’s asses are on the line.
Doesn’t seem to be the case here, so I think normal IT practices don’t apply to Blizzard.
2 Likes
Can’t disagree with you on outages being big trouble. I’d be very surprised, tho, if there’s not a major incident report within Blizzard that has executive visibility.
It’s also worth considering that, in typical IT circles, you can escalate to a vendor when you’re having trouble getting things fixed. Often, this escalation provides your engineers with access to a global pool of knowledge that includes a fix for what you’re experiencing. In this case, the Battle.net platform has no outside vendor they can escalate to–they wrote it themselves–so sometimes issues will come up that they have to dig into the weeds to truly understand.
Hey everyone, just for a bit of an update. I was able to get in about an hour ago.
No idea what did it. I just kind of set a macro to keep putting in my sign in, went to work out, and it got me in. So I think the best choice is to just brute force it maybe?
Unless they did something behind the scenes that they didn’t tell me about. So that’s the best advice I can give.
1 Like
I’ve been monitoring several threads for the last few days and this morning I’ve seen a spike in people (not a huge spike) saying they’ve been able to get in.
I find it terribly odd, that after 10 years - I come back to starcraft 2, re-install it, to find out I can’t play it because battle.net is down. I had no idea beforehand either.
2 Likes
Was still giving me the message it was down, but I got it to work for me somehow.
- Login, but hit cancel on authentication
- Login again. For whatever reason, it let me in for a second, but then kicked me because ‘I was logged in on another computer’
- Login again, and this time it stuck.
Strangest thing.
2 Likes
I tried this, but it didn’t work for me. Any ideas of anything else to try?
Holy crap, this worked! I literally just tried about 30m ago and was still getting the error. But hitting cancel and logging in again actually worked.
What is an “Authenticator”?
Why do I need it?
OldHermit:
The authenticator provides additional protection for your account to prevent hackers from being able to steal it.
Hello everyone
This issue does look to resolved. You should be able to log in now. If you continue to have issues continue to reply to this thread.
5 Likes
I can confirm I’m able to log in now.
Confirmed I can log in! Thank you Blizzard for your help and support!
Here’s a solution that worked for me.
Disclaimer: I tried this at around the same time that the issue was “resolved” so it’s probably not actually the solution. i’m going to leave this reply here just in case it happens again and I can try this solution again in the future.
The problem is in C:\Program Files (x86)\.build.info. I assumed there was a bad connection to one of the servers that are linked in there, so I began my troubleshooting process by connecting to EU and looking at the file. Connecting to EU (my home server is the US) gave me the following CDN Host URLs (in the cdn host url column) in .build.info:
(hyperlinks removed to allow post)
- http:/ /eu.cdn.blizzard.com/?maxhosts=4
- http:/ /level3.blizzard.com/?maxhosts=4
- https:/ /blzddist1-a.akamaihd.net/?fallback=1&maxhosts=4
- https:/ /eu.cdn.blizzard.com/?fallback=1&maxhosts=4
- https:/ /level3.ssl.blizzard.com/?fallback=1&maxhosts=4
It turns out that it may be very important they are in the correct order. When I swap back to my region (US), it swaps the order to the following (the state I cannot log into):
- http:/ /level3.blizzard.com/?maxhosts=4
- http:/ /us.cdn.blizzard.com/?maxhosts=4
- https:/ /blzddist1-a.akamaihd.net/?fallback=1&maxhosts=4
- https:/ /level3.ssl.blizzard.com/?fallback=1&maxhosts=4
- https:/ /us.cdn.blizzard.com/?fallback=1&maxhosts=4
See how the first two urls and the last two urls are swapped? I think Starcraft executable may be launched with these args and probably expects them to be in a certain order. So, what I did was change the order of the args in my US .build.info file to the same order that it was when i had selected EU:
From:
... level3.blizzard.com us.cdn.blizzard.com|http://level3.blizzard.com/?maxhosts=4 http://us.cdn.blizzard.com/?maxhosts=4 https://blzddist1-a.akamaihd.net/?fallback=1&maxhosts=4 https://level3.ssl.blizzard.com/?fallback=1&maxhosts=4 https://us.cdn.blizzard.com/?fallback=1&maxhosts=4|Windows...
…to:
... level3.blizzard.com us.cdn.blizzard.com|http://us.cdn.blizzard.com/?maxhosts=4 http://level3.blizzard.com/?maxhosts=4 https://blzddist1-a.akamaihd.net/?fallback=1&maxhosts=4 https://us.cdn.blizzard.com/?fallback=1&maxhosts=4 https://level3.ssl.blizzard.com/?fallback=1&maxhosts=4|Windows ...
Here’s the specific order I did the steps in:
Launch SC2 in another region. Close the game. This updates .build.info to the other region’s URLs (which is how i got the steps). Take note of the order of the urls
Re-launch SC2 in the home region (US for me). Close the game.
Re-order your home region’s urls to match the non-home region.
Thanks for getting the issue under wraps @Zayssie, any chance we could get some insight into the bug 
I’m curious.
2 Likes
reporting: Now i can log in US servers.
Servers now work for me. Thank you for that
I do though still have an issue with the coop commanders. free coop commanders being reset to level 5. Not sure if I can level them up at all
1 Like
A little bit late, but can confirm that I’m able to connect to US server(s).
Thanks for the support.
Out of curiosity, any advice on how long can an user be offline (without connecting into the game) without incrementing the chances of having further issues when attempting to get online again?
(I tend to go offline for long periods of time, but if a “ping” (to servers) every now and then is required to avoid issue, I would like to know it)
Thanks in advance.
30 days is required to be able to play in offline mode. I don’t know how long it is to avoid something like this but once every 29 days I’m guessing you’re good. And if you run into server trouble you can at least play offline
Hello Saber,
The co-op commanders level issue is currently being looked into. We do currently have a main thread that you can keep an eye on updates here.