Bungie explains why Destiny 2 servers have been on fire for months and why it can't be put out anytime soon

gamesradar.com:

Destiny 2 has been struggling with mounting error codes and regular server outages for months, frequently preventing players from playing the game at all on what feels like a weekly basis. Now, developer Bungie has finally addressed the state of the game's stability and what it's doing to fix it. Spoilers: it's good news and bad. 

Let's start with the obvious question: why are the servers on fire? The main culprit, Bungie explains in its latest blog post, is a part of the infrastructure called Claims, which tracks moment-to-moment gameplay and therefore "handles a tremendous amount of volume, routing every single kill, orb, or unit of Glimmer in Destiny 2 to the correct recipient." 

Before the release of Lightfall, Bungie made changes to Claims that helped improve stability during high-traffic moments, like an expansion or raid launch. Unfortunately, these changes hurt overall stability by way of "issues around the service's error recovery functionality."

This leads us to the error codes and server outages Destiny 2's been seeing. Due to the nature of these issues, Bungie says its new system "is not always recovering as expected," contributing to infamous error codes like Weasel and Baboon, and forcing hard restarts of either the Claims service itself or the entire Destiny 2 infrastructure. This in turn leads to downtime, which Bungie says it's "rapidly working to correct." 

As it works on fixes, Bungie's quick to stress that "this is not a process that can happen overnight," in part because hasty changes could make things worse. The team says "the improvements we are making are a crucial step in both addressing the immediate issues players are experiencing as well as better equipping us to deal with any potential future