OK, something is up with Blizzard servers. For the 3rd time in a week I got stuck in a queue. Every time it says, “<1 minute” for the expected wait time but even after 10 minutes it doesn’t put me in the game. Exiting and restarting BNet does seem to fix it but that doesn’t explain what’s going on. Are other folks having the same issue? Is it perhaps related to another Blizzard product bogging down the authentication servers?
No problem here (on UE) for me.
1 Like
I haven’t tried logging in today (I play on Americas) but I’ve noticed that I have been in a queue recently this past week. Though, it only lasted a few minutes tops. Certainly not 10.
My guess? Holiday weekend here in the States, combined with many of their games having shiny stuff going on all at the same time. Like, allegedly D4 doesn’t suck as bad now, and Immortal has a Waterbender people might be trying out. I think WoW Classic just released Cataclysm so obviously some people are now playing that until WoW Classic Classic comes out. And WoW retail (non-Classic version) also recently did a thing? Or was it Heartsthone?
Oh, and D2R! They just came out with a new season which means I get to update all my mods again the next time I want to fire that one up. And obviously, we have D3 with a great season (if you’re necro) still going on.
So yea. Saturday + Holiday + tons of games all “doing the thing” all at once = grab a snickers cuz you’re not going anywhere for a while…
3 Likes
No problem here. I’m currently playing on the Asia Region where I have the worst ping and highest latency. (I live in North America. My main Region is the Americas).
Did all three regions Challenge rifts today, a little bit before your post’s time. All worked well. You may want to check if you have some “Additional command line arguments” set regarding the prefered server to use. See:
I want to play in American server - General Discussion - Diablo 3 Forums (blizzard.com)
It has a list of all the possible servers. Another thing you can try is opening a command line with admin permissions and do the following commands one after one:
/ipconfig flushdns
/ipconfig release6
/ipconfig release
/ipconfig renew6
/ipconfig renew
release(6) / renew(6) depends on connecting to the inertnet via IP4 or IP6. If you know you only have to use the respective commands. But it is not doing anything “bad” if you use both, only that you’ll get an error message for the one you do not use. 
Good luck!
1 Like
To anyone not particularly tech savvy, this might look scary or intimidating. But I’ll vouch that this is perfectly safe and can be quite helpful. You know how when you contact tech support, and they’re like “did you try turning it off, and then back on again?” Or if your phone’s acting up and won’t connect to the internet, turning on Airplane Mode for a minute and turning it off will get it to “reset” its connection and start working again?
This is your local PC’s equivalent to that, with regards internet connection. If it’s JUST this one computer that’s wonky, you can do this instead of unplugging the entire router (which would knock out anything in your home relying on Wifi until the router reconnects).
For clarification, the commands are:
- ipconfig /release
- ipconfig /release6
- ipconfig /renew
- ipconfig /renew6
- ipconfig /flushdns
And should probably be executed in that order.
1 Like
I think it has something to do with cross network play.
Whenever I have changed those settings I have seen the OP’s issue.
Ooops. The Slash is indeed wrong in my description… 
Wrote it short before we left for a 3 weeks leave… Doesn’t really matter where one puts the “ipconfig /flushdns” - start, end, in between - the “effect” it has is the same: it flushes the (potentially corrupt(ed)) DNS cache.
@yessquire: Well, sometimes even Blizzard Support helps.
But the most important thing: is the original poster happy now?
1 Like