The login queue blinked from green to red in under a minute. I watched the counter climb past 110,000 and then the servers answered with a chorus of Weasel errors. For a few breathless minutes, the evening felt like a dam breaking.
I’ve followed big launches long enough to read the signs: sudden peaks, crash chatter on X, and that familiar mix of awe and anger. You and I both know what a final update means to a live service — it’s a last call, and thousands of Guardians showed up to answer.
Launch-night queue numbers spiked faster than anyone expected
The Monument of Triumph update went live and Steam reported more than 110,000 concurrent players shortly after launch.
That surge pushed Bungie’s systems into chaos: Weasel errors appeared across games, Bungie.net, and the Destiny 2 API, and many players found themselves bounced from servers or placed into long queues. I watched SteamDB wobble, then go offline for a spell — a second signal that this wasn’t just a local hiccup but a global rush to the servers.
Live chat and social channels filled up with protest and pride
Within minutes, Summer Game Fest and State of Play streams were peppered with Destiny messages and clips of disconnections.
You could see the sentiment split: some Guardians were there to protest the end of Destiny 2 and the shift toward Marathon, others simply wanted to spend a final night in the game they loved. The passion spilled onto X/Twitter, Reddit threads, and the in-game chat — the kind of organized chaos that looks a lot like a traffic jam of ghosts.
Why are Destiny 2 servers showing Weasel errors?
Bungie’s official status post on X said engineers were investigating “a rise in login and error codes affecting all Bungie games, Bungie.net, and the Destiny 2 API,” and that errors were dropping but queues could appear. In plain terms: infrastructure hit a concurrency wall as tens of thousands of players attempted to log in at once.
SteamDB and third-party telemetry mirrored player behavior
SteamDB briefly went down after the initial spike, which told me the visible player numbers were just the start.
Tools like SteamDB and in-house telemetry are blunt instruments: they show peaks fast and they show outages faster. The Monument of Triumph launch outpaced the player numbers seen at The Edge of Fate expansion last June, which explains why outages were more pronounced tonight than many recent launches.
How many players were online for the Monument of Triumph launch?
Steam listed over 110,000 concurrent players at the update’s launch. That figure surpassed Marathon’s launch peak on Steam and made clear this final update brought many Guardians back for one last look — and a few to make a point.
There’s a message behind the numbers and the errors
Players aren’t just logging in to raid or grind — they’re staging a farewell that doubles as a protest.
Some community members believe Destiny 2 is being phased out so Marathon can get more attention and resources. Whether that’s true, the optics are vivid: a huge, coordinated presence at launch night, long queues, and social feeds filled with anger and nostalgia. Bungie’s patch notes for Update 9.7.0 are massive — full of quality-of-life work, the Director map’s return, and buildcrafting changes — but tonight the headline was the crowd itself.
Patch Notes for Update 9.7.0, the one about Monument of Triumph and more, are now available:https://t.co/H64dowAXRo pic.twitter.com/0CI9tjPV6l
— Destiny 2 Team (@Destiny2Team) June 9, 2026
I keep returning to one fact: this was a coordinated, visible act. It doesn’t just register on server graphs — it rewrites the conversation around the game’s end. Bungie posted status updates and said they were monitoring; players posted clips and screenshot evidence; streamers counted crashes live. You can call it grief, protest, or celebration, but it’s a message delivered with numbers.
What this means for you and the wider community
Servers stabilize, patch notes will be read, and people will keep playing tonight and through the weekend.
If you were hoping to log in and avoid the queues, expect rolling access as Bungie clears the backlog. If you’re part of the crowd making noise — celebrating or protesting — your presence mattered. The final update drew a peak that will be a talking point for months: it’s both a goodbye and a public vote of emotion.
I’m keeping an eye on Bungie.net, SteamDB, and the official X feed, and I’ll be watching how Bungie responds technically and rhetorically. Are we watching a franchise close and a new one open, or is this the start of a bargaining moment between studio and fans?