clock menu more-arrow no yes mobile

Filed under:

Destiny 2 is down, Bungie investigating stork errors

Hold tight, says Bungie

Destiny 2 - Fallen enemies in Weapons Exchange Public Event Bungie/Activision
Ryan Gilliam (he/him) has worked at Polygon for nearly seven years. He primarily spends his time writing guides for massively popular games like Diablo 4 & Destiny 2.

Since about 7:30 a.m. EST, both the original Destiny and Destiny 2 players are unable to log into the games. Upon sign-in, a stork error code greets players, as well as a message indicating the servers are down.

On Twitter, Bungie says it’s investigating the issue. Via its Bungie Help account, the studio thanks players for their patience, and asks them to standby while the developers find a fix.

This downtime is unusual for a Friday morning in Destiny — or any day without a major content update. As usual, Bungie will continue to update players with any breaking updates on the game’s stability via the Bungie Help Twitter account.

It’s unclear if this server downtime could have anything to do with the launch of Destiny 2 on Google Stadia earlier this week. Prior to release, Stadia offered the complete Destiny 2 collection — including the game and all of its expansions — for pre-ordering the founder’s edition of the new service.

Update (4:15 p.m. EST): Players are now able to log in to Destiny 2. However, Bungie tweeted that server maintenance is still ongoing, and that players will likely still run into server issues (especially the weasel error).

In our own experience, we could land on a planet for a few minutes before the game booted us out to the login page again.

Sign up for the newsletter Sign up for Patch Notes

A weekly roundup of the best things from Polygon