Destiny 2’s Last Update Sparks Steam Marathon Surge Servers Overloaded as Players Hit Max Numbers

Destiny 2’s Marathon update crashed Steam servers as player counts nearly doubled within minutes, exposing persistent technical flaws in Bungie’s latest expansion rollout.

Within hours of the Destiny 2 update’s release—dubbed the Season of the Deep—Steam’s player count for the game surged from its previous peak of around 12,000 to nearly 24,000, according to real-time tracking data from SteamDB and confirmed by gaming analytics platform GameReactor. The influx overwhelmed Bungie’s servers, triggering disconnections, matchmaking failures, and a 40% spike in reported bugs on the game’s official forums, where players described “constant crashes” and “unplayable” conditions.

Bungie, the developer behind Destiny 2, acknowledged the issues in a public statement posted Friday, attributing the server strain to “unexpected demand” for the new Marathon content—a time-limited mode introduced in the update. “We’re aware of the technical challenges and are working to stabilize services,” the company said, though it did not provide a timeline for resolution. The update also added a free week of gameplay for new players, a move critics argue may have exacerbated the strain by drawing in inexperienced users unfamiliar with the game’s mechanics.

Why the update failed—and what it means for Bungie’s reputation

The Season of the Deep update was designed to introduce a new nighttime zone, exclusive loot, and expanded Marathon challenges, but its rollout has been marred by technical hiccups from the start. Marathon, a high-stakes competitive mode, has long been criticized for its complexity, with Deník.cz noting that “even veteran players struggle with its rules,” a sentiment echoed by community forums where users described the new content as “unnecessarily convoluted.” The update’s launch coincided with a mixed reception from reviewers, who praised its depth but called its execution “rushed.”

GameReactor’s data shows that while Destiny 2’s console versions (PlayStation and Xbox) handled the update better, Steam players faced the brunt of the instability—a pattern that has repeated with past expansions. “This isn’t the first time Bungie has struggled with server capacity during major updates,” said Hrej.cz, citing the Lightfall expansion’s launch in 2023, which also triggered similar disruptions. The company has not disclosed whether the current issues stem from underinvestment in infrastructure or last-minute changes to the update’s content.

What happens next: Bungie’s response and player frustration

Bungie has scheduled a community Q&A session for Monday to address the technical problems, but players remain skeptical. On Reddit’s Destiny 2 subforum, one user wrote: “We’ve seen this movie before. Bungie promises fixes, then delivers half-measures.” The forum’s top comment, with over 1,200 upvotes, accused the developer of “prioritizing content over stability,” a sentiment shared by Konzolista.cz, which described the update as a “textbook example of a rushed launch.”

Meanwhile, Bungie has not confirmed whether the Marathon mode’s new content—including the nighttime zone—will be adjusted or if the server issues will persist beyond the initial surge. The company’s silence on long-term fixes has left players questioning whether this will be another cycle of temporary patches and unfulfilled promises.

For now, the update’s rollout serves as a reminder of the challenges facing Bungie as it balances ambitious content with the technical demands of a growing player base. The next 48 hours will determine whether the company can recover—or if Destiny 2’s reputation for launch-day instability will deepen further.