Battle.net accounts unable to login yet again
by Alex Ziebart 
Mar 29th 2009 at 9:28PM
Now, I've been one of the louder advocates about switching to Battle.net account amongst my guildmates and the other WoW Insider writers, I absolutely think it's a great concept. Just as I fully support Steam, I support any Steam-esque services of a decent quality. This here? Quickly losing my favor. If the error message above is truly what it implies, that the login server is failing due to heavy traffic, I must repeat what we've said the last dozen times something on Blizzard's end has fallen apart due to too much traffic: Come on, really? You underestimated your service's popularity? Again?
If there are any further chapters to this story before it's fixed this evening, we'll be sure to let you know.
Update: The error is getting more sporadic as the night wears on, so I'm personally going to assume that it is, indeed, a traffic issue. None of us know that for a fact, of course. Still, if you try now, you'll have better luck getting in than you did a short while ago.
Filed under: Realm News, Analysis / Opinion, Realm Status, Blizzard, Account Security
Reader Comments (Page 1 of 3)
danawhitaker Mar 29th 2009 9:32PM
I have a merged Battle.net account, and I was just able to get in after two errors, and then a failed attempt to use my old login. So hopefully whatever happened is either fixed or is more sporadic than it appeared.
RipeTomatoe Mar 29th 2009 9:38PM
Mine works fine. Maybe it's just a server error no matter what your account status is (merged or non-merged)
danawhitaker Mar 29th 2009 9:39PM
Something weird is going on. None of my guild has transitioned to battle.net accounts, and many of them have been getting huge lag spikes/problems and have also been booted on hearthing and using portals. When I went from Dalaran to Shattrath just now upon logging in the game froze and booted me. I'm not convinced this is specifically related only to battle.net in any way.
Warbutcher Mar 29th 2009 11:40PM
NARC!!
shibumi Mar 29th 2009 9:43PM
yep, same here - battle.net account. constant error. tried on my mac, which hadn't been updated, but also hadn't been patched. by the time I patched and tried again,the battle.net access failed.
there's always been a noticable delay in authentication after battle.net. as if the other server were slow/longer reach/whatever.
and, after one failure, I'm back in.
Redski Mar 29th 2009 9:48PM
I have a regular account and have been having pretty terrible luck logging in during these times, so it's either an unfortunate coincidence or I think that the problem is not strictly limited to battle.net accounts.
Quitius Mar 29th 2009 9:55PM
I FINALLY GOT ON! but now i cant even switch servers ... WTF BLIZZ
Icepuck Mar 29th 2009 9:58PM
The first guinea pigs always have the most problems, the delay from when we first heard these accounts were coming (wotlk beta) to now is a long period of little or no word or testing on the player ends.
I think in many cases Battle.net just adds more connections your computer needs to make, that can potentially fail, and being as its new systems the chance of connection failures is higher.
necroholic Mar 29th 2009 10:02PM
my raid group was taking kelthazad down for the first time tonight, and I missed it, because i got disconnected and could not reconnect because of this, and got my spot filled. I am super Ticked because of this.
araquen Mar 29th 2009 10:05PM
Odd, I've been on and off all night with nary an issue.
I have the iPhone authenticator, and I found that if you try an input the umber a little too early (when the number just changes), the login field doesn't recognize the number. Maybe it's a sync issue.
So I usually wait for the timer to be about half-way and I get in just fine.
My work also uses an authenticator (one similar to the WoW authenticator), and I find with that one, if the number is close to expiring, I can fail to log in to my VPN.
Aside from that, I guess I've been lucky.
pilage Mar 29th 2009 10:06PM
For over a week now i have had these issues, ive checked the forums and there is alot of people complaining. I have told every one i know who plays not to switch. its 100% trash currently. I had to wait 30 mins to log on yesterday.
if blizz is wanting to have people convert to this system they should have had these issues worked out. or atleast posted soemthing on the "alert-news" thing when you open the game to tell people there has been issues. its just something some one who is providing a service should do. I hope they get this figured out soon, dont want to dc during a raid and have to wait to log on and have people pissed im dced.
fatsephy Mar 30th 2009 10:19AM
I'm not sure if you folks have trouble reading or not, but if you spend a few moments *reading* the comments you will see that there is a very simple fix for the problem.
I merged my accounts the first day and had login issues for a couple of hours one day last week. I modified my realmlist the way it's described on the wow support site and was able to login immediately and have not had a single problem since.
Plastic Rat Mar 29th 2009 10:15PM
So glad I didn't switch to Battle-Net yet. I'll just quietly hang on until everyone else is done testing their system for them.
Oddly though there seems to be a weird increase in traffic. I logged on tonight to find a queue for the first time in months. Maybe it's just my server, or is there a sudden increase in traffic again like we had post patch?
Jack Mar 29th 2009 10:21PM
I have a battle.net account and an iPod Touch authenticator, and I just logged in with no issues whatsoever.
Jack Mar 29th 2009 10:25PM
I'd also like to add that I haven't had any problems since switching over, either.
G Mar 30th 2009 3:32AM
Same here. Merged my account on 3/21 and haven't had a single problem yet.
Cephas Mar 29th 2009 10:42PM
I feel like maybe someone should point out that Blizzard has a support page on Battle.net account connection issues. Not sure if it'll help anyone, but it's worth a shot: http://us.blizzard.com/support/article.xml?articleId=26433&categoryId=2316&parentCategoryId=&pageNumber=1
PhoenixStorm Mar 29th 2009 10:43PM
I'll wait until all the stupid bugs are worked out, thanks. Let me know when that happens and I'll switch over :)
SaintStryfe Mar 29th 2009 10:43PM
no problem with my battle.net account or my iPhone activator.
Chris T. Mar 29th 2009 10:45PM
There is a way to fix it.
Open TCP Port 4000. This was an old Battle.net connection port that still seems to be in use.
I was having these issues, found someone saying to open up TCP 4000, fixed it immediately, and my latency was sub-100 for the first time ever, once I got in game.