Destiny 2 Error Codes
Destiny 2 names its errors after animals and objects instead of numbers. Most are network problems between you and Bungie's servers. Here's what each one means and how to clear it.
Error codes
WEASEL
General account / connection error
Cause: You were disconnected from Bungie's servers — often after being signed out, an account issue, or network instability. Common during maintenance.
- Check @BungieHelp and the Bungie server status for maintenance.
- Fully close and restart the game.
- Restart your router; use a wired connection if possible.
CURRANT
Connection lost to Bungie servers
Cause: A general disconnect, frequently seen during rolling maintenance or heavy load.
- Wait if maintenance is in progress.
- Restart the game and your network hardware.
BEAVER / FLATWORM / LEOPARD
Network connection / NAT problem
Cause: A peer-to-peer or NAT issue — your router is blocking the ports Destiny needs, common on strict/Type 3 NAT.
- Set your NAT to Open (enable UPnP or port-forward Bungie's ports).
- Use a wired connection instead of Wi-Fi.
- Restart your router.
CENTIPEDE
General networking error
Cause: A connection problem between you and Bungie, sometimes ISP routing or a firewall.
- Restart your router and console/PC.
- Enable UPnP or port-forward the recommended ports.
- Contact your ISP if it persists on one connection only.
BABOON
Packet loss / connection drops
Cause: Your connection is dropping packets — unstable Wi-Fi, congested network, or a failing router.
- Switch to a wired Ethernet connection.
- Restart your router; replace it if packet loss continues.
- Stop other heavy downloads on the network.
MARIONBERRY
Connection interrupted (usually your side)
Cause: A temporary loss of connection to Bungie, often local network instability.
- Restart your router and reconnect.
- Move closer to the router or go wired.
- Retry after a minute.
GUITAR / CHICKEN
Can't connect to Bungie servers
Cause: Your connection to Destiny servers failed to establish — network, NAT, or maintenance.
- Check for maintenance on the Bungie status page.
- Restart the game and router.
- Open your NAT type.
BROCCOLI
Hardware/driver crash on PC
Cause: On PC this points to a GPU driver or overheating/overclock issue rather than a network problem.
- Update your GPU drivers.
- Remove any GPU overclock and check temperatures.
- Verify game files on Steam/Epic.
ANTEATER
General networking error
Cause: A general network fault dropped your connection to Bungie mid-session. Bungie logs these but offers no single home fix.
- Fully close and relaunch the game, then retry.
- Restart your router and modem; prefer a wired (ethernet) connection.
- Check @BungieHelp for wider server issues.
BEAN
Activity launched with too many players
Cause: The game tried to start an activity with more than the allowed six players in the fireteam.
- Relaunch the same activity with an appropriate number of players (max six).
- Have extra members leave the fireteam before starting.
BEE
Connection interrupted (bandwidth)
Cause: Your connection was interrupted, usually from internet congestion, low bandwidth, or a home-network fault.
- Stop file-sharing, downloads, or heavy streaming on your network.
- Use a wired connection instead of Wi-Fi.
- Restart your router to clear congestion.
BOAR
Network connection interrupted
Cause: Your network connection dropped briefly. Frequent boar errors usually point to an unstable wireless link.
- Switch from Wi-Fi to a wired ethernet cable.
- Restart your router and modem.
- Move closer to the router if you must use Wi-Fi.
CABBAGE
Router/firewall blocking Destiny 2
Cause: Your router or firewall is blocking data from the Destiny 2 servers.
- Add a firewall exception (or open NAT) for Destiny 2 in your router settings.
- Enable UPnP or set your NAT type to Open.
- Temporarily disable strict firewall/parental filters to test.
CALABRESE
Trouble reaching Bungie servers
Cause: You are having difficulty connecting to Bungie servers, usually due to testing or maintenance on Bungie’s end.
- Check @BungieHelp and the server status page for maintenance windows.
- Wait and retry once maintenance ends.
- Restart the game after the servers are back up.
CAT
Update released while in-game
Cause: Bungie pushed a patch or hotfix while you were already in the game.
- Close the game fully.
- Install the pending update.
- Relaunch Destiny 2.
CHICKPEA
Crossplay disabled mid-activity
Cause: A player in your fireteam turned off crossplay while you were in an activity together.
- Have that player re-enable crossplay in Settings.
- Reform the fireteam after crossplay is on for everyone.
ENDIVE
Servers down for maintenance
Cause: The Destiny 2 servers are down for scheduled maintenance.
- Wait for maintenance to finish — nothing to fix on your side.
- Watch @BungieHelp and the server status page for the all-clear.
Fixes that work for most Destiny 2 errors
- Check the game's official server status page or its X/Twitter — if servers are down or under maintenance, no local fix will help; wait it out.
- Fully close and restart the game and its launcher (Steam / Epic / EA App / Battle.net).
- Restart your router and, on PC, flush DNS (open Command Prompt and run: ipconfig /flushdns).
- Verify or repair the game files in your launcher so a corrupted update is re-downloaded.
- Make sure the game and your OS are fully updated — most 'version mismatch' errors are an out-of-date client.
FAQ
What does the Weasel error mean in Destiny 2?
Weasel is a general account/connection error — you've been disconnected from Bungie's servers, often after a sign-out or during maintenance. Restart the game, check the Bungie status page, and restart your router.
How do I fix Destiny 2 Beaver error?
Beaver is a NAT/network problem. Set your NAT type to Open by enabling UPnP or port-forwarding Bungie's ports, use a wired connection, and restart your router.
Other games
- Borderlands 4 Error Codes — LowLevelFatalError, Unhandled Exception, GPU Crash Dump & Fixes
- Path of Exile 2 Errors — Unexpected Disconnection, Patching Server & Login Queue Fixes
- The First Descendant Error Codes — Disconnected, Login Failed, Matchmaking & Crash Fixes
- Warframe Error Codes & Errors — Update Failed, Login Failed, Network Not Responding & More
- World of Warcraft Error Codes — WOW51900319, WOW51900323, BLZBNTAGT & Battle.net Errors
- EA App Error Codes — EC:10000, EC:100, EC:10005, Login Loop & More (PC & Mac)
- Epic Games Launcher Error Codes — LS-0006, LS-0013, LS-0014, IS-0009, DP-01 & EOS-ERR
- Steam Client Error Codes — Error -101, -105, -118, Error 51, Disk Write Error & More