Destiny 2 ending Weasel errors what happened?

Destiny 2 ends, and players tried to finish on the last update

Destiny 2’s final live-service patch—its last content update, the Monument of Triumph series—rolled out as Bungie brought the game to an official close after 12 years. As the update landed, Destiny 2 players reported widespread “Weasel” server errors while attempting to access the game, which disrupted gameplay right when many Guardians were trying to wrap things up.

What players were doing

Rather than treating the final update like “business as usual,” the community response leaned emotional and event-like. Many players used the remaining time to complete activities and transition off the game, but the errors made normal logins and sessions difficult.

Why it matters

Even on a sunset title, concurrency and server stability matter: the end of a long-running MMO-style FPS is one of the rare moments when large groups often return or concentrate their final sessions. The reports also align with a broader pattern common to shutdown periods—traffic spikes as players try to participate before the lights go out.

Scale of the problem

The coverage specifically mentioned that more than 100,000 players were active on Steam during this final update window, underscoring the demand hitting the servers at the same time.

In short, Destiny 2’s shutdown was already a major moment for long-time fans, but the “Weasel” errors during the last update added friction to the goodbye, turning a planned send-off into a troubleshooting scramble.

Final takeaway

Destiny 2’s conclusion went live, but connection problems (“Weasel”) briefly marred the final-update experience for many players—right as the Steam population was unusually high.