7 Fast Marathon Error Code Fixes: Weasel, Marmot & Server Issues

Marathon has officially arrived, and as with any massive Bungie release, the servers are under heavy fire. If you are in the middle of a high-stakes run and suddenly get booted to the main menu with a weird error code named after a vegetable or an animal, you are not alone.

Because Marathon is an extraction shooter, disconnecting can mean losing all of your hard-earned loot and your Runner’s gear. Here is the complete breakdown of every known Marathon error code, what they mean, and exactly how to fix them so you can get back into the game.

Basic Connection Fixes to Try First

Before you start troubleshooting specific Marathon error codes, run through this quick day-one checklist.

• Check the Official Status: Always check the Bungie Help account on X (Twitter) or the Bungie Server Status page to ensure the game isn’t down for emergency maintenance.
• Restart the Game: Completely close the Marathon application and relaunch it.
• Go Wired: If you are playing on Wi-Fi, switch to a wired Ethernet connection. Extraction shooters require incredibly stable packet transfers, and a wired connection prevents many common Marathon error codes.
• Update Everything: Ensure your console has the latest system update, or if you are on PC, make sure your Windows OS and GPU drivers are fully up to date.

Complete List of Marathon Error Codes

Error Code Basil & Error Code Paprika

These are your standard, run-of-the-mill Marathon error codes caused by network disconnects. If you see Basil or Paprika, your connection to the Marathon servers simply timed out.

• The Fix: Try logging back in immediately. If you are repeatedly getting hit with Basil or Paprika, the Marathon servers are likely experiencing heavy load or localized outages.

Error Code Broccoli

This error is specific to PC players. Error Code Broccoli means that Marathon has lost connection to your GPU (Graphics Processing Unit), usually caused by a driver crash.

• The Fix: Ensure that your GPU drivers (Nvidia or AMD) are fully updated. Double-check that your GPU is seated properly. If you have aggressive overclocks applied to your graphics card, try reverting them to default speeds.

Error Code Ginger

You will usually see this during matchmaking before you even drop into a zone. Error Code Ginger means that a player in your current crew has disconnected.

• The Fix: Marathon prevents you from loading into a match without a full squad if you queued for one, so it halts the process. Wait for your teammate to resolve their own connection error and rejoin your lobby.

Error Code Marmot

Marmot is one of the most severe Marathon error codes, indicating your game files have become corrupted or are unreadable by your system.

• The Fix (PC): Open Steam, right-click Marathon in your library, select ‘Properties’, navigate to ‘Local Files’, and click ‘Verify integrity of game files’. Wait for it to finish and restart.
• The Fix (PS5): Turn off your console completely. Hold the power button until it beeps twice to boot into Safe Mode. Select ‘Clear Cache and Rebuild Database’, then choose ‘Clear System Software Cache’.
• The Fix (Xbox Series X|S): Hold the power button on the console until it completely shuts down. Unplug the power cable from the back for one to two minutes, plug it back in, and restart the game.

Error Code Tapir

If you receive Error Code Tapir, stop trying to fix your internet because this is one of the few Marathon error codes entirely out of your control. Tapir is Bungie’s dedicated code for server maintenance.

• The Fix: The servers are offline. You simply have to wait until Bungie concludes their scheduled (or emergency) maintenance window.

Error Code Weasel

A classic Bungie error returning from Destiny. Weasel is a broad networking error indicating a severe break in your connection to the servers.

• The Fix: Reset your router and check your ISP for local outages. Important: Weasel can also be triggered if you are trying to log into your Marathon account on multiple platforms (like PC and PS5) at the exact same time. Make sure you are only logged into one device.

What Happens to Your Loot if You Disconnect in Marathon?

The biggest fear in any extraction shooter is losing your gear to a server crash. If your game crashes or you are hit by any of these Marathon error codes, your Runner stays in the match. You will just be standing perfectly still.

If you boot the game back up quickly enough, Marathon will attempt to reconnect you to your match so you can finish your run. However, while you are disconnected, you are entirely vulnerable. If another player or an AI enemy kills your stationary Runner while you are trying to reconnect, your loadout and inventory are wiped. If the disconnect was caused by a massive server crash on Bungie’s end, the game will attempt to return your starting gear to you, though Bungie notes this is not guaranteed.