Just from looking at blue posts and the tech support forums, you can see the the Bnet disconnect issue isn't exclusive to WoW, Diablo 3 players have been experiencing the disconnect and lag spike issues as well. Not to say that oQ isn't causing a problem for some people, but there are others who don't even use oQ that are having the same problems. And from the troublehooting steps Blizzard has been asking people to perform, it doesn't sound like they have much of a clue either. There are recent tech support posts asking users about their isp's, routers, location, whether or not the connections is wired or wireless. But really, most of the disconnect issues have been happening since the changes to battlenet and the launcher, and from some of Blizzard's tech suport responses, they don't seem terribly concerned about the issue because in a recent Blue Post they stated: "We have received a number of reports, but after checking our concurrency data (= number of people playing & logins/logouts), it seems that only a small portion of the playerbase is affected by these connection issues, which means they might be based on region or ISP."
Some speculation points to the patch on Feb 13th:
"BattleTag™ or Real ID friends are now only able to send 10 chat messages every 10 seconds over Battle.net® chat. User Interface Add-Ons should use the new send function and receive events to send communications information."
I have tried several options, different router, new modem, fresh install of Windows 7 (not a repair install), updated drivers, fresh install of wow, no addons installed at all, and I still experience connection issues with battlenet. I've also tried with and without using the bnet launcher, as well as both the x86 and 64 bit versions of wow from their respective .exe files, on 2 different desktops and one laptop. In my case, I can say for certain is is NOT oQueue causing most of my disconnects from Battlenet, they're merely more frequent with oQueue turned on, but happen without it as well.
I also occasionally receive the "You are not in a Party/Raid/this Instance's Group" messages if I don't go to the Premade tab and Leave premade group before joining another group or entering a battleground, and also when I am invited to a raid group BEFORE the RL converts to raid and starts an oQueue group or after an oQueue group has been started, but I have been invited normally outside of oQueue.
Some speculation points to the patch on Feb 13th:
"BattleTag™ or Real ID friends are now only able to send 10 chat messages every 10 seconds over Battle.net® chat. User Interface Add-Ons should use the new send function and receive events to send communications information."
I have tried several options, different router, new modem, fresh install of Windows 7 (not a repair install), updated drivers, fresh install of wow, no addons installed at all, and I still experience connection issues with battlenet. I've also tried with and without using the bnet launcher, as well as both the x86 and 64 bit versions of wow from their respective .exe files, on 2 different desktops and one laptop. In my case, I can say for certain is is NOT oQueue causing most of my disconnects from Battlenet, they're merely more frequent with oQueue turned on, but happen without it as well.
I also occasionally receive the "You are not in a Party/Raid/this Instance's Group" messages if I don't go to the Premade tab and Leave premade group before joining another group or entering a battleground, and also when I am invited to a raid group BEFORE the RL converts to raid and starts an oQueue group or after an oQueue group has been started, but I have been invited normally outside of oQueue.