I have seen many of these threads, but it seems that most of the posts are just people ranting and complaining. I will say that I am quite guilty of that as well, and my patience is growing thin, but I think we should try to provide Bungie with more specific information so they can get our issues fixed as soon as possible. Please post your specific issues in here, and try to keep it short-ish, to the point, and present it in a professional manner so they don't have to comb through garbage to find what they could possibly need.
I'll start by saying:
I'm on the Xbox 360. I am on my home network. I get mostly just BEE and CENTIPEDE after entering any game zone. I can sit in orbit and stare at my ship for hours, but even entering a mission, strike, crucible match, or the tower nets me a BEE error within 2-10 minutes. I'VE HAD THESE ISSUES SINCE DAY 1. I've tried all the workarounds mentioned on this site (NAT Type, opening ports, QoS, disabling flood protection, DMZ server, static IP for router and console, hard resetting everything multiple times, deleting system cache, deleting and reinstalling the game, using a VPN, going wireless and wired, and multiple combinations of all of these)
Any help/reply would be appreciated. We must keep hammering them until we are heard.
Also, pass this around the forum:
http://arstechnica.com/gaming/2014/09/eight-days-later-bungie-leaving-disconnected-destiny-players-stranded/
^This is getting ridiculous. We are not a tiny portion of the community.
-
Playing on Xbox 360. My ISP is Pavlov media in an apartment complex near Texas A&M. Open NAT and direct wired connection to my router. Ports are forwarded per Bungie's and Xbox's demands (seemed to alleviate my issues ONLY after a day or two). Time of day doesn't seem to impact my likelihood of getting errors. Patrol seems to be the safest mode to play atm as strikes did not work for me until about 4 days ago. Crucible is 50/50 Playing Solo definitely improves my odds of not getting disconnected but it still happens. I have gotten Hawk, Bee and Anteater ONCE while Baboon and Centipede are my most common errors (about 50 times now combined) although today after 6 PM CST I have gotten the Elk error six times while playing public events Got Destiny 8 days after it came out (9/17) Played for two days with some errors (mostly centipede) Spent the weekend at a friend's house who has Verizon FIOS and no errors (Sweet Jesus I miss Verizon) Queens Wrath update hit and I was bombarded with CENTIPEDE and BABOON errors The last 4 days have been BETTER though with the occasional disconnect due to centipede