All Marathon Error Codes: What They Mean and How to Fix Them

You’re mid-extraction. Suddenly you’re booted, and a strange word sits on the screen instead of a normal error message.

Here’s the fast answer. Bungie names Marathon error codes after animals and plants instead of plain numbers. Most of them share the same handful of fixes. This guide covers the most common ones in real depth, explains the official code system, and points you to Bungie’s own page for anything not covered here.

We’re not going to pretend this list covers every single code Bungie has ever documented. Nobody honestly can, and we’ll explain why below.

Try This First, Before Looking Up a Specific Code

Most Marathon errors share the same first-response fixes. Work through this before diving into a specific code.

Step	Why It Helps
Check Bungie’s server status page or @BungieHelp	Confirms whether it’s a known, wider outage
Fully close and relaunch Marathon	Clears temporary session issues
Restart your router and modem, wait 60 seconds	Resets your connection to Bungie’s servers
Restart your PC or console	Clears background conflicts
Switch from Wi-Fi to wired Ethernet	Reportedly resolves the issue for a significant number of players
Flush your DNS or try alternate DNS servers	Fixes connection routing issues
Temporarily disable VPN or firewall	Removes a common source of blocked connections
Wait 10 to 15 minutes during peak traffic	Server load often resolves itself with time

If none of that helps, move on to the specific code you’re seeing.

The Two Official Error Code Categories

Bungie splits Marathon errors into two categories. Knowing which one you’re dealing with points you toward the right kind of help.

Platform Error Codes come from your specific platform, like PlayStation, Xbox, or Steam, rather than Marathon itself.

Marathon Error Codes come from the game and Bungie’s servers directly.

The type of error determines where you’ll find the best troubleshooting support. Platform-specific issues are often better addressed through your platform’s own support channels alongside Bungie’s guidance.

Common Marathon Error Codes

Here’s what the most frequently reported codes actually mean, and how to fix each one.

Code	What It Means	Fix
Weasel	A significant break in your connection to Bungie’s servers	Reset your router, check for local ISP outages. Also check if you’re logged in on two platforms at once
Marmot	Corrupted game files	Steam: verify integrity of game files. PS5: boot into safe mode with a wired controller
Tapir	Scheduled or emergency server maintenance	No user fix. Check server status and wait
Basil	A simple server disconnect	Log back in, check for scheduled maintenance
Ginger	Disconnect during matchmaking	Can prevent your whole crew from entering a match
Currant	Server-load issue, closely related to Ginger	If your own setup checks out, waiting is usually the fix
Paprika	Sometimes paired with a numeric code	If it persists, post on the Bungie Help forum
Nightingale (Xbox)	Connection issue specific to Xbox	Full power cycle, or clear the alternate MAC address in Network settings
Buzzard	Server-side connection failure during high traffic	Usually resolves with a restart and retry
Oregano	No specific cause published by Bungie	Retry, restart, check your network, report if it persists

Weasel: The Multi-Platform Trap

This one deserves a closer look. Weasel usually means a real break in your connection.

But it can also fire simply because you’re logged into your Marathon account on two platforms at the same time, like PC and PS5 together. If you’ve recently switched devices, make sure you’re fully signed out on the other one.

Marmot: Corrupted Files, Not a Connection Problem

Marmot isn’t network-related at all. It means something in your local game files got corrupted.

On Steam, right-click Marathon in your library, choose Properties, then Local files, then Verify integrity of game files. On PS5, hold the power button until you hear two beeps to enter safe mode. You’ll need a wired controller to navigate it.

Tapir: Nothing You Can Do

Tapir is Bungie’s own maintenance code. There’s no fix on your end.

Check the server status page, confirm maintenance is underway, and wait it out.

The Numeric Code: W:8:80090305

This one shows up differently from the named codes. It’s a server handshake timeout, meaning your connection request took too long to reach the server.

It’s especially common during high-traffic periods. Restarting the app generates a fresh authentication token, which often clears it. Flushing your DNS and switching to wired Ethernet help too.

Platform-Specific and Technical Issues

Some Marathon problems aren’t about connection at all.

Black or Missing Textures on AMD Cards

Players on AMD RX 560, 570, 580, and 590 graphics cards, all using the Polaris architecture, have reported black or missing textures. Bungie has acknowledged this as a widespread issue and was investigating it.

The current workaround is a clean install of the latest AMD Adrenalin drivers, beta or stable.

Missing Files or Tutorial Crashes on Xbox

If Xbox throws missing files errors or crashes during the tutorial, a hard reset usually clears it. Fully unplug the console’s power supply, then delete and reinstall the game from the dashboard.

BattlEye Issues

BattlEye is Marathon’s anti-cheat system. Issues tied to it form their own category, separate from general connection errors.

The Cross-Platform Play Trick

Here’s a tip worth trying if matchmaking keeps failing. Disable cross-platform play under Settings, then Network.

Multiple players have reported this getting them into matches when nothing else worked.

PS Plus Requirement

Online play on PS5 requires PlayStation Plus, even during periods when the base game or a specific access window is free. Missing this requirement can look like a connection problem when it isn’t.

What This Guide Doesn’t Cover

Bungie’s official Marathon Help page documents an extensive, alphabetical list of named error codes, and it keeps growing.

We’ve focused on the codes reported most often and documented clearly enough to explain properly. Codes like Centipede, Stingray, and CAT exist in Bungie’s system, but their specific causes aren’t clearly documented yet, so we won’t guess at them here.

If you hit a code that isn’t covered above, check Bungie’s official Marathon Help error code section directly. It’s the most reliable place to confirm anything new.

Frequently Asked Questions

What’s the difference between a Platform Error Code and a Marathon Error Code?

Platform Error Codes come from your specific platform, like PlayStation, Xbox, or Steam. Marathon Error Codes come from the game and Bungie’s servers directly.

What should I try first before looking up a specific error code?

Check Bungie’s server status, restart the game, restart your router, and switch to wired Ethernet if possible. Most codes share these same first-response fixes.

What does the Weasel error mean, and can logging in on two devices cause it?

Weasel usually means a broken server connection, but it can also trigger from being logged into your account on two platforms simultaneously.

What does the Marmot error mean, and how do I fix it on my platform?

It means corrupted game files. On Steam, verify the integrity of game files. On PS5, boot into safe mode using a wired controller.

Is the Tapir error something I can fix myself?

No. It’s Bungie’s dedicated maintenance code. Check the server status page and wait.

Why do I keep getting error W:8:80090305?

It’s a server handshake timeout, most common during high-traffic periods. Restart the app, flush your DNS, or switch to wired Ethernet.

Why are my textures black or missing, and is this a known issue?

Yes, for AMD RX 560, 570, 580, and 590 cards specifically. Bungie has acknowledged it. A clean AMD Adrenalin driver install is the current workaround.

Does this guide cover every possible Marathon error code?

No. Bungie’s official list is large and still growing. We’ve covered the most commonly reported codes in depth and point you to Bungie’s own page for anything else.

Quick Reference Summary

Question	Answer
Two official error categories	Platform Error Codes and Marathon Error Codes
First step for any error	Check server status, then restart everything
Weasel’s hidden trigger	Being logged in on two platforms at once
Is Tapir fixable by you	No, wait for maintenance to end
Where to check codes not covered here	Bungie’s official Marathon Help page