Destiny 2 Error Codes Explained: What They Mean and Fixes
The most common Destiny 2 error codes and what to do about each one, from BEAVER and CAT to network errors
Destiny 2 throws error codes instead of plain messages, and most of them look scarier than they are. The list below covers the codes players actually hit, what each one means, and the first thing to try.
Crash and platform errors
- BEAVER: a PC crash, usually tied to your GPU or a conflicting overlay. Update your graphics driver and close any overlay software.
- CAT: a PlayStation error. Restart the game, then rebuild the database if it repeats.
- MARIONBERRY: a PlayStation Network error. Check the PSN status page.
- PLUM: a Battle.net error. Restart the Battle.net app, then verify the game files.
- BROCOLI: an unexpected game error. Restart the game first, then verify files if it keeps happening.
Network errors
- CHICKEN: a connection problem between you and the servers. Reset your router or switch to a wired connection.
- CURL: a network error during a request. It usually clears with a game restart.
- DUCK and WEASEL: connection drops, often from Wi-Fi or a strict NAT. Wired internet fixes most cases.
- BABOON: you disconnected from the activity. Rejoin from the roster if the fireteam still has a slot.
- MOON: the servers are busy or down. Nothing on your end will fix it.
What to do first, every time
- Restart the game. A large share of codes clear on their own.
- Check the Bungie Help page and the official status channels for a known issue.
- Restart your router if the code mentions your connection.
- Verify game files on PC if the code repeats after restarts.
Error code responses that waste an evening
- Reinstalling the whole game for a network error.
- Ignoring the status page during a server outage.
- Assuming every code is a ban. Most are connection or driver issues.
Read the code before you search it
Codes narrow the fault faster than any symptom description, because Bungie groups them by subsystem: platform, network, and crash each have their own families. Before searching, decide which family your code belongs to — a BEAVER is a client crash and will never be fixed by router settings, while a WEASEL is a connection drop no driver update will touch. That one classification prevents the most common wasted evening, which is reinstalling the game over a network code. If the code is new to you, check whether the servers are up before touching your machine. The server status guide and the crash fix list are the two ends of that decision.
Related guides
Sources & References
This guide is verified against the game's own data and official communications. For patch notes, current balance, and authoritative specifics, consult the references below. Where a precise number cannot be verified, we explain the mechanic rather than invent a figure.
- Destiny 2 on Bungie.net — patch notes, current season, and authoritative game data.
- Destiny 2 Wiki — community-maintained mechanics, maps, and item data.