Let me start off by saying that I love Destiny. It's the game I always wanted to play, and I log enough hours on it that I'd be happy to pay a moderate subscription to support bug-fixes and continued development. But for me and many other, the Destiny experience has been marred by a host of unsolved and apparently unsolvable network errors. These problems manifest themselves in many ways; excessive lag in PvP, force-closing of Destiny, being kicked from PvP games, spawning into a map with no players or other content, etc. It is rare to play for an hour without observing serious network problems. Error codes provided in-game direct users to the Bunjie support site, which blames your network connection and/or network setup most of the time. Bungie's "Self Help" troubleshooting guide provides instructions for setting up your internet connection, "stabilizing" your internet connection, and configuring your NAT type. To be fair, connection issues in Destiny will often be related to network configuration, but my experience has been that Destiny is the only game that consistently fails to maintain a reliable connection. In my house of three guys, we can struggle to stay connected in Destiny for hours, and then switch to Battlefield 4 or Call of Duty and experience perfect PvP gameplay with a low-latency connection and no risk of being kicked. Back to Destiny, and the network issues return. I know that I'm not the only one. Over the past 24 hours, Destiny's network help forum (to which this is being posted) has filled with scores of complaints from similarly affected players. And this has been a problem for quite some time. Back in September, 2014, Ars Technica posted an article discussing Destiny's network issues and their failure to provide a mechanism for help (http://arstechnica.com/gaming/2014/09/eight-days-later-bungie-leaving-disconnected-destiny-players-stranded/). Bungie's response, according to Ars? [quote]Bungie issued a statement to Ars Technica that blamed "a small number of issues" on "largely the result of Internet filtering from institutions like universities. Bungie’s networking team has been working actively with those institutions and hardware providers to make sure we’re doing everything we can to keep people playing." Bungie did not respond to our questions about the company's current customer service methods. [/quote] In other words, "there aren't actually very many problems," and "this isn't actually our fault." This response is characteristic of most of Bungie's support efforts on the network connectivity front: blame the customer's network, or their ISP, and point out how complicated and scary a place the internet is. But in spite of the scariness of the internet and the apparent unreliability of most people's network connections, Destiny appears to be the ONLY major game that suffers from systemic network connectivity issues on all platforms. The fact that other AAA games (GTA, Battlefield, CoD, etc., etc.) run like a dream while Destiny trips and falls is suggestive of an architectural problem that is more deep than Bungie is willing to admit. Of course latency is unpredictable, and of course there are complications involved in developing a robust networking infrastructure to handle it. But it is clearly possible to do so, and Destiny so far fails to follow suit. I want to love Destiny. I want to keep playing, and I want to keep paying. But there are limits to the loyalty of this customer. Bungie's refusal to accept that there is a problem, and its proclivity to blame anyone but itself, is as disturbing and annoying as being unable to play the game because of its poor network performance. I may find myself crawling back to Battlefield, for a consistent experience and a consistent connection.