This issue still persists since around April 6 for me. Seems that some days and times are better than others when trying to log into USWest.
I found some software that automates the entire login process. Since then, I’ve been able to actually play instead of trying to log in over and over and over manually.
Monday, 24 May, 11:45am Chicago time:
Was able to get on to USWest on first attempt (after verifying my account was good by logging on to USEast).
The usual bot and park games were playing, not much else. Exited D2/LOD after about ten minutes of looking for an interesting game.
Yea recently i have started playing diablo 2 again and i have not had a lot of luck getting on battle net uswest its the only realm i ever played on and its where i am located so naturally its the only fit for me. so far have been trying 2 hours to login to battlenet i was able to login last night for a bit then got disconnected. I have 2 copies of the game and have the laptop on beside the main computer and trying to login on both accounts. one gets on the other one still cant. so i just play on whichever one was able to get on. yes the problem is a serious one. they really need to update their negotiation protocol. It is possible this is a tactic to get you to upgrade to the new Resurrected version of the game. im banking 99% on that tactic otherwise they would just fix this.
Thursday, 27 May, 1:30pm Chicago time:
Tried to log in 10+ times (including doing the realm-switch three times). Other three reams were sub-5 seconds to get to acct. USWest was sit-and-hang at “Connecting…” or “Checking Versions”. Let game sit at picking realm screen (not attempting to log in) and took a break for about 10 minutes. Came back, selected USWest, and got on fairly quickly. Verified there was no official announcement of a new ladder starting in the next 3-4 days, checked for any interesting games, and logged off.
Stuck at “Checking Version” here on US West, same as other folks.
“Checking Version” forever!
If sitting at “Checking Versions”, give it 25+ seconds, then disconnect and try again. Waiting longer is just a waste of time, as the system seems to drop any char waiting longer than 25 seconds (it just does not tell you).
Same issue here for my brother and I and I’m logging into two accounts on two computers and one can get on sometimes much faster than the other - doesn’t seem to be much rhyme or reason…
Can’t tell what the problem might be, but it is likely there is a problem with one or more of the access paths (software problem). If you get one of the “bad” ones, you can never get on. So, you try again–and hope to get a “good” one this time.
Saw something similar 15+ yrs ago on a major online job site. Every now and then, I would get a problem where I could not log on, or do anything. Exit and retry usually worked. Turned out, one of their routers had a bad port. If you got that bad port when you tried to log in, you never could. Got lucky with that problem. The person checking it out also hit that same issue early in her review (trying to replicate the reported problem), so it was found and they knew it was real. They were happy I had reported it and they got it fixed almost immediately.
This problem is effecting me as well… been playing for years and never had this issue so its obviously on the blizzard side
Fresh install, I haven’t been on diablo 2 in quite some time (around 2016 last i believe) I remember back then this was an occasional issue, not as bad as it is now, but at the same time it wasn’t uncommon to have to try the “gateway switch” in order to login to USWEST. Anyways… I tried to login for the first time off a fresh install, patch 1.14b, to gateway USWEST. It would not go past checking versions, I let it sit for approximately 10 minutes without any change, it didnt go to can’t connect, or any of that other nonsense, keep in mind this original post started mid april, it is now June 6, and this has been an ongoing issue for YEARS. I am not attacking blizz or any MVP’s, but at the same time this is ridiculous, This was made public back then that this was an issue, and I am sure if Blizz archives forum posts I could probably find the one I saw before. I play mostly other games, D3, WoW, etc. Even PoE which is known for being incredibly buggy and crashy, never actually fails to connect, and it is almost nearly as old as D2…
I have played blizzard games extensively since 1998.
I have learned four things over the years about blizzard.
Early on Blizz Customer support was actually decent, you could call their CS team and get your issues fixed (I had accounts on WoW and D2 respectably that got hacked and was able to get the issue resolved in usually an hour or two depending on call wait times. Now if that happens I would have to wait anywhere from 48 hours to 2 weeks. I cannot call blizz anymore, I cant get through to CS and even when I have had tech issues with WoW WHICH IS THEIR FLAGSHIP GAME, I get ignored after their first response. Which brings me to my next point.
Blizz CS has become complete and utter garbage. The fact I still even bother to play these games is because most of the time, it is worth it regardless of the fact that Acti-Sh*t’s idea of customer service is ignore them, there are plenty of fish in the sea. This is a common feeling across all of the battle net community @blizzard. STOP IGNORING US.
This is an older game, I fully expect it to have issues, blizz canceled support, even sold the BNET servers to AT&T if I remember correctly, I don’t know if this ever changed or if it actually happened and I was fed misinformation, but I do know they stopped with the regular updates years ago. D2 has been paid for, they got what they wanted out of it, why would they bother to continue to help the D2 community with a login issue, when typically speaking, they drop support on a game roughly 3-4 years after they release its latest content without any new updates, often sooner?
The only way I see Blizz actually improving, is if they get their heads out of Acti-Sh*ts Butt and actually end the contract with them. I have no idea how that would happen, I’m not a lawyer, but activision to my knowledge hasn’t really been much of an issue until roughly 5-6 years ago.
I am not trying to swear, I know its against forum policy, if you need to edit the words go for it, thats why I used the *.
But my point remains the same, Why should blizzard care about any of us, so long as they continue to abide by activisions ruling that money is greater than anything else? If I continue to play I will be on USEAST, but I might just go back to PoE, at least there my opinion is validated and taken into consideration.
Yep. Also have this issue. Hangs at Checking Versions, I press Cancel, the entire game freezes and I have to reload to try again (multiple times).
Also know for a fact that people are running farming bots (not exactly a huge secret to anyone that plays the game but apparently to Blizzard it is)…
Update: still happening to me.
When it hangs at “Checking Versions”, let it sit for 25+ seconds from when it starts (I usually count to 27). Then it drops almost immediately when you hit the cancel button.
2 months no blue post. lol
Yeah, I guess they just gave up on fixing this. It’s clearly some issue with only some of the servers in the server pool. When you connect you hit a dns pool that assigns you a random server to connect to. Hence why reconnecting a few times eventually works because you eventually bypass the bad ones and hit a good one. How they haven’t managed to fix the bad servers by now is the question. Surely this can’t be that difficult to solve if someone knowledgeable spends some time looking through the state of the servers or looking at any firewall rules that might be affecting some but not others.
That’s about as long as it takes me to reload the entire game… or longer tbh (depending on how long you want to wait for “when it hangs”). Not like this actually fixes the issue in the slightest but appreciate the suggestion all the same.
They have about 1 and a half interns working on this, and that’s a generous estimate.
was hoping this issue would be resolved at ladder reset, but its not… thanks blizzard.
A few days later:
Now I am seeing delays of 5 minutes and more. Can’t say why it is happening, but it has happened several times after the first 4-5 days of the new ladder. A formal ticket has been submitted, which was allegedly “resolved” as this is all old hardware, etc. Obvious nonsense, and I replied to that claim as such. I reopened the ticket (or tried to, any way), so we will see what happens. Most likely, nothing will happen because there are no real consequences if Blizzard/Activision does nothing.