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.

Updated OP. oQueue 1.9.0 has made changes to hopefully reduce any part it may be playing in this issues.

Hi, there.

I haven't experienced any more disconnects in the last two versions (since 1.8.9).

Great job everyone involved and thanks!

I have solved this issue by changing dns.

I've experienced this issue and it doesn't seem to matter where I launch the wow game from. Later oqueue versions haven't made a difference, but it seems to me that the fewer b.net friends I have the less often it happens. I am led to wonder if it isn't b.net booting me on purpose due to the amount of network chat going out across the app. Most often for me though the glitch occurs when I logout from one character and into another without fully exiting the game.

Hello.I have arrived at this forum in good time. I have been using OQ since the beginning. I have noticed that the MB usage for this addon climbs out of control as more raids or events are listed in the que. It rapidly starts from 3MB to over 8-9 MB very fast during high OQ pop times. This has of late prevented me from casting more than 1 spell during a 25 man raid without a 15-20 second lockup lag spike. Late in the wee hours of the low pop times (OQ Lisitngs) The memory usage is not as bad. The event of batlenet disconnects are rapidly increasing if I log from one toon to another, and must restart the game to reconnect to battlenet. It appears (and I mean appears) as though the memory usage during a raid consumes MB usage as though more players are actually in the raid when the OQ list is wacko scrolling in high usage times. I noticed ( I have several toons) the logging from one toon to the next...Oq retains connections and the list remains without a refresh and restart of the list. This spikes Bnet connections hard and seems to cause alot of bnet disconnects. Wehn Oq was first becomming popular the high volumes times require you bedg your raid leader to allow you to not kick you from the group untill you relog and unload addon and log back in. ( became standard practice with many of us in the same situation.) The last update however I try I cannot run while actually in a raid or lockup city. As usual Bliz will incorporate an ingame addon to squash OQ as it does with all the others that people have been using eventualy. In the meantime.... I have also tried to go dark to prevent the traffic problems and its not quite the fix. I would ask that a kill addon option completely ( that would releive memory) While still ingame and a refresh or restart list when relogging to a new toon be inserted into the addon. Once you are added to a set number of Ques to raid this would allow the system to be freed up and prevent the need to log out and kill addon. ......just my thoughts ..and hope all goes well...


Edit....
I have found that inside of a raid with OQ running..If you change a talent ..wow kills the addon due to error.....I am using this technique as an addon killer..

Nothing fixed for me. A fresh install of oQueue seems to work fine. I can use it once or twice, then the next time I log in it CONSTANTLY spams me with a message "Battle.net is down. oQueue will not function properly until Battle.net is restored."

I have tried not using the Battle.net client and directly opening WoW, but same issue. While I AM using the client I am successfully signed into Battle.net and can message friends from the Battle.net client no problem (but not from within WoW.) The minute I uninstall oQueue the problem disappears.

I can delete my oQueue folder, reinstall it, and then it works fine for 1-2 more uses before the issue comes back. This is definitely an oQueue issue or it wouldn't be resolved by uninstalling. Wondering if it has to do with the mass delete friends button? I use this almost every time I raid via oQueue cause I don't want people I don't know IRL on my list. (This is just a pure speculation suggestion I have no real evidence to back that up, just happens to be a piece of my puzzle.)

If there are logs or anything we can do to help report bugs let me know. On a side note, you need to make it not spam us so much when battle.net goes down. It is seriously like the last 50 things in my chat log. Once every 30 minutes would be fine.

Forgot to add that the addon also cause sporadic screen stuttering that is also resolved by uninstalling. Never a full freeze up, but almost like the camera is shaking. But maybe if it wasn't pinging battle.net every 10 seconds blizzard wouldnt boot us. That seems excessive

@polaarbear

turn off all addons except oQueue and see if you still have the stuttering issue.

as for battle.net, if you pop up oQueue and see the 'battle.net is down' message, check your friends list. if you see your battle.net friends online, then hit the 'check again' button in the lower right of the 'battle.net is down' message. if you do not see any friends on your friend's list, log out to the password and log in (this is how you get another battle.net connection)

issues with battle.net are beyond my control and are strictly managed by blizzard.

I understand that issues with battle.net are beyond your control in the sense that you have no power to influence battle.net as you are not a blizzard employee. But the fact that it hasn't happened a single time without oqueue installed seems to me that oqueue is somehow the cause of the battle.net disconnects. I don't know if you are requesting data in a way that blizzard doesn't like, or if there is data being routed in a way that the servers determine as suspicious or what. But it is 100% that oqueue is the cause. I have confirmed 3 times today alone that it works on fresh install, breaks after a couple uses, and is fixed by removing it.

The only other addons I use is DBM, and my UI ElvUI but I have turned ElvUI off with no change, and DBM would cause basically every wow player to stutter so I doubt thats it. Running an i5 with 8GB of ram. Even changing the res to 800x600 doesn't help. I can be getting 200+ fps and the camera "bounces" occasionally. It isn't constant, just every now and then I notice it being weird. Doesn't really hurt gameplay but is annoying.

I notice if I fly from zone to zone, about every 10 ingame meters, oQueue memory usage goes up and up and up. After flying around a whole continent it goes from ~3Mb to over 20Mb. Don't see why it should be grabbing any world data that would do that, but I'm not an expert on the code side of things.

Eventually I just DC but the game client never recognizes that I am DC'd. I can fly around the entire world, and NPC's don't spawn in any city but I can travel for as long as I want, with alt + f4 the only way to exit.

I am on Comcast with a 30MBps connection and a sub 15ms ping at all times