Marathon error codes: meanings, causes, and how to fix Tapir
Marathon uses Bungie's familiar error-code style: Tapir, Weasel, Marmot, Basil, Broccoli, and more. This guide explains what the codes mean in plain language, why they appear, and what to do when Marathon will not let you sign in, drops you from matchmaking, or shows Error Code: TAPIR.
Quick answer
If Marathon shows Tapir, check Bungie server status and maintenance first. Tapir usually means the service is down or unavailable, but if servers are green and the error persists for hours, the cause may be authentication, routing to Bungie, account region, IP-range access, or an ISP issue.
What to check first
Do not start by reinstalling the game. Most Marathon errors fall into three groups: Bungie service status, unstable user network, or a local PC/console problem.
The fastest diagnosis takes a few minutes: check official status, fully restart the game, rule out Wi-Fi instability, confirm that the game is updated, and then diagnose the exact code.
Checklist
- ✓Check Bungie Server Status and Bungie Help posts for Marathon maintenance.
- ✓Fully close Marathon and the launcher, then start the game again.
- ✓Restart your router and PC/console if the error repeats after a fresh sign-in.
- ✓On PC, update your GPU driver, Windows, and the launcher used to start the game.
- ✓Temporarily use Ethernet instead of Wi-Fi when possible.
- ✓If the game shows an extra numeric code, save it for a support ticket.
Marathon error-code table: meaning, cause, and fix
This table covers publicly known and commonly reported Marathon/Bungie codes. Bungie may change meanings or add numeric variants, so always compare persistent errors with official status and the Marathon Help forum.
The animal name is not the technical cause. The useful part is where the chain broke: server status, authentication, network route, game files, video driver, or a fireteam member.
| Code | Plain meaning | Likely cause | How to fix |
|---|---|---|---|
| TAPIR | Service unavailable | Servers are down for maintenance or outage. If no maintenance is active, authentication, routing, region, or access to Bungie IP ranges may be failing. | Check Bungie status, wait for maintenance to finish, restart the game. If it is not widespread, test VPN/routing, DNS, account region, and post in Marathon Help. |
| WEASEL | General network break | Connection drop, unstable Wi-Fi, ISP route, simultaneous login on multiple platforms. Rarely, account restrictions can return the player to title with Weasel. | Sign out on other platforms, use Ethernet, restart router, check NAT/UPnP, and retry. |
| MARMOT | Corrupted or unreadable files | The game cannot read local files or believes they are corrupted. | Verify files on Steam/Epic. On console, clear cache, restart, and reinstall only if needed. |
| BROCCOLI | GPU/driver failure | PC video driver crashed, the GPU stopped responding, or Marathon lost access to the graphics device. | Update NVIDIA/AMD/Intel drivers, remove overclocks, restart PC, check temperature, and disable overlays. |
| BASIL | Basic disconnect | A simple disconnect from Marathon servers. | Log in again, check server status, restart the game, and save any numeric code for support. |
| PAPRIKA / OREGANO | Connection interruption | Network timeout, service load, or temporary backend unavailability similar to Basil. | Retry after a few minutes, check maintenance, switch Wi-Fi to Ethernet, and save the numeric code. |
| GINGER | Fireteam member disconnected | Someone in the fireteam disconnected during matchmaking, preventing the group from entering. | Have the disconnected player restart and rejoin. If it repeats for one player, diagnose that player's network. |
| STINGRAY | Platform or account sign-in issue | Platform sign-in, account service, or authentication may be unavailable. | Check Steam/PSN/Xbox Live, sign out and back in, and confirm platform network services are working. |
| W:8:80090305 | Handshake timeout | The client did not complete authentication before the server timeout, often during peak traffic. | Fully quit Marathon, wait 30-60 seconds, launch again. On PC, run ipconfig /flushdns and try Ethernet. |
| BUZZARD | Server stopped responding | The backend stopped responding or the route to it became unstable. | Check server status, restart the game, disable unstable VPNs temporarily, change DNS, and test wired networking. |
| CURRANT | Network timeout | Packet loss or a timeout between your client and Bungie services. | Restart router, check packet loss, pause background downloads, try another DNS or another network. |
| NIGHTINGALE | Cache or local data issue | Client data, cache, or local configuration failed to load correctly. | Restart the game, clear platform cache, verify files, update the client, and retry. |
| BEE / BABOON | Packet loss or short disconnect | Brief internet drop, packet loss, or congested ISP route. | Use Ethernet, stop background downloads, check the router, and contact the ISP if packet loss appears outside the game. |
Tapir explained: why Error Code: TAPIR appears
Bungie's official Tapir wording has historically pointed to maintenance or service unavailability. For Marathon, that means the client reached the sign-in stage but the service did not allow authentication to continue.
In practice, Tapir does not always mean your home internet is bad. If friends in another region can sign in while you keep seeing Tapir with green server status, suspect routing, regional availability, blocked IP ranges, account state, or third-party platform authentication.
- Tapir for everyone usually means maintenance, outage, or server overload.
- Tapir only on one network points to ISP routing, DNS, firewall, or an unstable VPN/proxy.
- Tapir only on one account means you should check account region, platform links, account restrictions, and Marathon Help.
- Tapir disappearing through another route means the problem is between your network and Bungie services, not local game files.
How to fix Tapir in Marathon
Start with actions that do not change your account: service status, restarts, updates, and a cleaner network path. If Tapir is maintenance-related, local changes will not help and you need to wait.
If no maintenance is active, the goal is to find where sign-in breaks: Bungie, the platform, your ISP, DNS/routing, or regional access.
Checklist
- ✓Open Bungie Server Status and check Marathon maintenance.
- ✓Fully close Marathon, wait one minute, and launch again to get a fresh auth token.
- ✓Restart Steam/PSN/Xbox app and sign in again.
- ✓On PC, run ipconfig /flushdns from an administrator Command Prompt.
- ✓Switch from Wi-Fi to Ethernet or test sign-in through another network such as a mobile hotspot.
- ✓Temporarily disable unstable free VPNs/proxies. If you use VPN for routing, choose a stable low-loss server.
- ✓Confirm the same Marathon account is not active on another platform.
- ✓If Tapir persists only in your region, create a Marathon Help ticket with country, ISP, platform, time, and the result of testing another network.
How to tell Tapir, Weasel, and Marmot apart
Tapir usually appears before a complete sign-in and is tied to service availability or authentication. Weasel is more often a network disconnect: unstable link, multi-platform login, NAT, or reset connection. Marmot is usually local: game files are corrupted or unreadable.
If you see Tapir, file verification is not the first step. If you see Marmot, file verification is the main step and changing DNS is unlikely to help.
| Situation | Most likely code | First action |
|---|---|---|
| The game will not pass the sign-in screen | Tapir | Check service status and authentication |
| The game drops you from a match or connection breaks | Weasel, Bee, Baboon, Currant | Check network stability and Ethernet |
| The game complains about files or fails after an update | Marmot, Nightingale | Verify files and clear cache |
| The game crashes with a graphics error on PC | Broccoli | Update GPU driver |
What to include in a Marathon Help ticket
If the error repeats after basic checks, support needs reproducible data. The clearer your code, platform, and timing are, the easier it is to separate a service outage from a local route.
The exact time matters because Bungie can compare it with backend logs, maintenance windows, and regional spikes.
Checklist
- ✓Exact code, such as TAPIR, WEASEL, MARMOT, or W:8:80090305.
- ✓Platform: PC Steam/Epic, PS5, or Xbox Series X|S.
- ✓Country, ISP, and connection type: Wi-Fi, Ethernet, or mobile hotspot.
- ✓Time of the error with time zone.
- ✓Screenshot and any additional numeric code.
- ✓Checks already completed: server status, restart, Ethernet, DNS flush, another account, or another network.
FAQ
What does Tapir mean in Marathon?
Tapir usually means Marathon or Bungie services are unavailable because of maintenance, outage, or authentication failure. If servers are online, Tapir can point to routing, regional access, platform authentication, or account restrictions.
Can reinstalling Marathon fix Tapir?
Usually no. Reinstalling helps with Marmot or Nightingale, but Tapir is more often server, authentication, or network-route related. Check Bungie status, restart the game, and test another route first.
Why does Tapir appear only in some countries or regions?
For some players, Tapir may be caused by routing, IP-range reachability, regional restrictions, or platform policy rather than home internet. Only Bungie or Marathon Help can confirm the exact reason.
How do I fix Weasel in Marathon?
Weasel is a broad networking error. Sign out on other platforms, restart your router, use Ethernet, check NAT/UPnP, and make sure the same account is not active on another device.