Shadowkeep expansion launch marred by major server problems that left Guardians floating adrift

Destiny 2 players were left floating adrift in space, dogged only by 'Weasel' error codes, as they tried to load into Bungie's next major expansion release Shadowkeep, following a host of server issues knocking the game's main engine offline. Bungie responded nearly immediately, running "emergency maintenance" to fix the problems.

Bungie's first tweet read: "Destiny 1 and Destiny 2 are being taken offline for emergency maintenance. Please standby for updates," and another update was sent out at 2:46pm PT which read, "Emergency maintenance for Destiny 1 and Destiny 2 is still ongoing. We apologize for the continued delay. Please stay tuned for updates on our progress."

Destiny 1 and Destiny 2 are being taken offline for emergency maintenance. Please standby for updates.

— Bungie Help (@BungieHelp) October 1, 2019

During the peak of the issues, Guardians were left in queues of more than 10,000 players, and when they finally reached the head of the line they were punted straight to the back. As issues lessened, some Guardians found their way onto the haunted Moon only to again be sent back to the queue after barely cracking the surface of the new expansion.

Bungie also revealed that Destiny 2's players were experiencing a host of 'Beaver' and 'Weasel' errors, which mainly relate to issues logging into multiple platforms while cross-save functionality is enabled. A “Beaver” error is “a failure to connect your console to another player’s console via the internet,” most likely because of internet connection issues.

Despite the issues, Destiny also raced straight to the top of Steam’s best selling games list on its first day on Valve's program. This swap marks the first time in 2019 that Destiny 2 has been available outside of the Battle.net client for PC players.

Amidst the problems, Bungie also found that the purchase of Silver - Destiny's in-game currency - was also locked for some Guardians. Bungie disabled Silver for an hour on Tuesday, before re-enabling it soon after during the middle of the shutdown.

At around 10pm ET, Bungie reported their maintenance was complete.