Official explanations only · checked 18 October 2026
tools/error-codes Error Codes
More on Destiny 2: requirements, patch notes and more.
Destiny 2: 30 error codes explained by Bungie, including BEAVER, WEASEL, BABOON, CENTIPEDE, BROCCOLI and MARIONBERRY. Each line gives what Bungie says the code means, what it says to do, and a link to its page.
| Code | What it means | What Bungie says to do | Source |
|---|---|---|---|
BEAVER |
Caused by a failure to connect your console to another player's console over the internet (shared with FLATWORM and LEOPARD). | Enable UPnP and open your NAT; if on WiFi, switch to a wired connection. | Official page updated 9 Oct 2026 |
WEASEL |
An all-encompassing error that is usually an indicator of a general networking issue. | Switch from WiFi to wired at least temporarily and follow the Network Troubleshooting Guide; power cycle the console if Destiny no longer launches. | Official page updated 16 Oct 2026 |
BABOON |
A general networking error that Bungie is actively tracking; the disconnect is reported automatically. | Switch from WiFi to a wired connection at least temporarily; if you can't log in, force quit and relaunch Destiny. | Official page updated 12 Oct 2026 |
CENTIPEDE |
A general networking error that can be caused by a loss of connection to Bungie's servers. | Switch to a wired connection and get a Strict/Type 3 NAT into an Open/Type 1 state. | Official page updated 15 Oct 2026 |
BROCCOLI |
An issue detecting the player's GPU, commonly caused by a driver crash. | Keep your operating system and graphics drivers up to date. | Official page updated 12 Oct 2026 |
MARIONBERRY |
Indicates a problem with your networking setup. | Exit Destiny, shut down your console or PC, unplug your networking hardware for at least 30 seconds, then check the connection and Parental Controls if it continues. | Official page updated 18 Oct 2026 |
ANTEATER |
A general networking error that Bungie is actively tracking; the disconnect is reported automatically. | If it keeps happening, follow the Network Troubleshooting Guide. | Official page updated 16 Oct 2026 |
BEE |
General disconnections between you and Bungie, such as packet loss or ISP/internet congestion (grouped with FLY and LION). | Use a wired connection, avoid bandwidth-heavy tasks while playing, follow the Network Troubleshooting Guide, and contact your ISP if it continues. | Official page updated 8 Oct 2026 |
FLY |
General disconnections between you and the routes your traffic takes across the internet. | Avoid bandwidth-heavy tasks while playing, follow the Network Troubleshooting Guide (including trying wired), and contact your ISP if it persists. | Official page updated 21 Dec 2023 |
LION |
Can be caused by general disconnections between you and the routes your traffic takes to Bungie. | Follow the Network Troubleshooting Guide and avoid file-sharing, video streaming or other bandwidth-intensive tasks. | Official page updated 22 Dec 2023 |
CABBAGE |
Router settings are blocking communications to or from Destiny services. | On Technicolor/Thomson routers, create a new firewall level, enable UPnP, and disable Extended Security and any assigned games and applications settings. | Official page updated 18 Oct 2026 |
OLIVE |
Likely caused by testing Bungie is doing on its end. | Retry the activity; if it happens again, exit Destiny and relaunch. | Official page updated 7 Aug 2026 |
CALABRESE |
A general networking error Bungie tracks, which can occur due to testing or maintenance on Bungie's end. | If it continues, follow the Network Troubleshooting Guide and watch help.bungie.net and @BungieHelp for updates. | Official page updated 9 Apr 2024 |
CAT |
A new update to Destiny is available. | Exit the game and apply the update before relaunching; on Steam, fully restart the Steam app. | Official page updated 7 Oct 2026 |
CHICKEN |
The player is having connection issues to Destiny 2. | Use a wired connection and power cycle the main router/modem. | Official page updated 18 Jul 2026 |
BUFFALO |
The player is not signed in with their platform account, or the platform service is undergoing maintenance. | Check your platform's service status; on PC, log out of Destiny 2 on other PCs and restart your launcher; if it persists, post in the #Help forums. | Official page updated 6 Oct 2026 |
CURRANT |
Usually caused by interruptions between host and client connections, often from factors outside Bungie's network. | Make sure your own connection is working, then follow the Network Troubleshooting Guide. | Official page updated 15 Oct 2026 |
NEWT |
listed without explanation | Retry the activity; if it happens again, exit Destiny and relaunch. | Official page updated 20 Jul 2026 |
PLUM |
BattlEye has detected a problem with your computer that may violate Bungie's Terms of Service. | PC players should make sure they have the latest Windows update; see the BattlEye FAQ and support page. | Official page updated 16 Oct 2026 |
CHIVE |
Bungie is investigating reports of this error when launching Destiny 2 on PC. | Update graphics drivers, reinstall them if errors continue, and use Scan and Repair to check the install. | Official page updated 28 Aug 2026 |
SHEEP |
You tried to join a Fireteam in which a member has not updated to the latest version. | Close and restart Destiny to start your update. | Official page updated 26 Jan 2024 |
TAPIR |
Destiny is likely down for maintenance. | Watch @Bungiehelp; if no maintenance is under way, create a new topic in the #Help forums. | Official page updated 16 Oct 2026 |
BAT |
A general networking error that Bungie is actively tracking; the disconnect is reported automatically. | If it keeps happening, follow the Network Troubleshooting Guide. | Official page updated 30 Sep 2026 |
CANARY |
Destiny cannot detect a connection to your home network. | Switch from WiFi to wired at least temporarily and cold-reboot your console and networking hardware. | Official page updated 16 Oct 2026 |
BEETLE |
A general networking error that Bungie is actively tracking; the disconnect is reported automatically. | If it keeps happening, follow the Network Troubleshooting Guide. | Official page updated 14 Oct 2026 |
CATTLE |
Trouble connecting to, or staying connected to, Destiny matchmaking servers. | Retry; if it repeats, exit and relaunch Destiny and make sure your network isn't blocking the connection. | Official page updated 7 Jul 2026 |
GUITAR |
Too many items are left on the ground (not picked up) in an activity such as Gambit. | Make sure items are picked up off the ground in those activities. | Official page updated 10 Jun 2026 |
BOAR |
The player's network may be having issues connecting to their console. | Use a wired connection; if it continues, a reinstall of Destiny may be needed. | Official page updated 11 Aug 2026 |
BANJO |
Trouble connecting to, or staying connected to, Destiny matchmaking servers. | Retry; if it happens again, exit and relaunch; on WiFi, try a wired connection. | Official page updated 13 Apr 2024 |
BADGER |
A general networking error that Bungie is actively tracking; the disconnect is reported automatically. | If it keeps happening, follow the Network Troubleshooting Guide. | Official page updated 4 Sep 2026 |
Quick answers
tools/error-codes error questions
What is Destiny 2 error BEAVER?
Caused by a failure to connect your console to another player's console over the internet (shared with FLATWORM and LEOPARD). Bungie says: Enable UPnP and open your NAT; if on WiFi, switch to a wired connection.
What is Destiny 2 error WEASEL?
An all-encompassing error that is usually an indicator of a general networking issue. Bungie says: Switch from WiFi to wired at least temporarily and follow the Network Troubleshooting Guide; power cycle the console if Destiny no longer launches.
What is Destiny 2 error BABOON?
A general networking error that Bungie is actively tracking; the disconnect is reported automatically. Bungie says: Switch from WiFi to a wired connection at least temporarily; if you can't log in, force quit and relaunch Destiny.
What is Destiny 2 error CENTIPEDE?
A general networking error that can be caused by a loss of connection to Bungie's servers. Bungie says: Switch to a wired connection and get a Strict/Type 3 NAT into an Open/Type 1 state.
What is Destiny 2 error BROCCOLI?
An issue detecting the player's GPU, commonly caused by a driver crash. Bungie says: Keep your operating system and graphics drivers up to date.
What is Destiny 2 error MARIONBERRY?
Indicates a problem with your networking setup. Bungie says: Exit Destiny, shut down your console or PC, unplug your networking hardware for at least 30 seconds, then check the connection and Parental Controls if it continues.
What is Destiny 2 error ANTEATER?
A general networking error that Bungie is actively tracking; the disconnect is reported automatically. Bungie says: If it keeps happening, follow the Network Troubleshooting Guide.
What is Destiny 2 error BEE?
General disconnections between you and Bungie, such as packet loss or ISP/internet congestion (grouped with FLY and LION). Bungie says: Use a wired connection, avoid bandwidth-heavy tasks while playing, follow the Network Troubleshooting Guide, and contact your ISP if it continues.
Each meaning and fix is a one-line summary of the publisher's own page, linked on its row. Publishers update these pages; we re-check monthly. All games.