Marathon error codes are bound to pop up, particularly on and after launch day as players pile into the game and descend to Tau Ceti. In short, be prepared for the worst with server issues and disconnects being likely, but the recent server slam was reassuringly smooth for many. Either way, receiving an error code during a high-stakes run is never ideal, so you'll want to resolve any issues as quickly as possible to get back to playing Marathon or at least learn why they're happening and if they're beyond your control. Here's a list of common error codes in Marathon and some potential fixes for them.
Basic Marathon error code fixes
Many of the Marathon error codes listed below can be fixed in the same way since they can have very similar causes. So, before getting to the specific error codes, here's a quickfire list of possible solutions you can try that might fix your errors or tell you about any expected server issues:
- Restart Marathon.
- Check the Bungie Server Status and maintenance schedules for Marathon. It's also worth following the Marathon team account too.
- Check your Internet Service Provider's (ISP) service status for any network outages.
- Restart your router.
- Restart your PC, PS5, or Xbox Series X.
- Ensure your console has the latest software update or that your PC has the latest OS update and GPU drivers installed.
- Switch to a wired connection using an ethernet cable.
If none of the above or below fixes work and you keep seeing error codes in Marathon, your best bet is to create a thread in Bungie's Help forum detailing your problem and the error code you're getting. Hopefully, you'll be able to get some proper guidance on how to fix your problem or help Bungie sort a more widespread issue.
Marathon error code basil
The basil error code in Marathon appears to just be for a basic disconnect, so you should try logging back in. If you're repeatedly hit with this error, try checking the server status and for any maintenance. Bungie also recommends submitting a Help forum thread for further investigation if a numeric error code is listed as well.
Marathon error code broccoli
If you're receiving error code broccoli in Marathon, it's likely because your PC's GPU can't be detected, which can be caused by a driver crash. Make sure your OS and GPU drivers are up to date and that your GPU is properly installed in the first place to hopefully resolve this error code.
Marathon error code centipede
The centipede error code is a general networking error, but it can appear specifically when connection to the Marathon servers is lost. That might be due to your wifi connection dropping or a Strict/Type 3 NAT.
To fix a persistent centipede error code, you should switch to a wired connection, if possible, or check your NAT type and see if you can change it to Open/Type 1. The latter might not be possible depending on your ISP or if you're connected to a widely used network, such as at a university campus.
It's also worth noting that Bungie has observed centipede errors spiking in certain regions from temporary issues that can pass quickly. Therefore, it might also just be worth waiting a bit before trying to log back into Marathon.
Marathon error code ginger
Error code ginger occurs in Marathon when a player in your crew disconnects during matchmaking, preventing you from entering a match without a full team. There's a good chance that the disconnected player received their own error code which might need resolving, but it shouldn't be anything to worry about on your end unless it persists.
Marathon error code oregano
Bungie hasn't listed a clear cause for the oregano error code in Marathon, but it sounds like it's most likely to strike when attempting to load into a match. The solution is essentially to just try whatever you were doing again or restart Marathon if it happens again. But if error code oregano persists, you should try checking your network and connection and submit a Help forum thread.
Marathon error code paprika
Error code paprika is resolved in a similar way to basil – try logging back in but check for maintenance or post a forum thread if it persists, especially if there is a numeric error code too.
Marathon error code marmot
Error code marmot strikes when Marathon's game files are corrupt. Ensure the game has been shut down entirely, then try the following depending on your platform to resolve marmot:
- Steam: Right-click on Marathon in your Steam library, select 'Properties' from the list, then 'Local Files'. Select 'Verify Integrity of Game Files', wait for this process to finish, then restart Marathon.
- PS5: Turn off your PS5 and wait until it has fully powered down, then press and hold the power button until it beeps twice – this starts your console up in Safe Mode, which can only be navigated with a PS5 controller using a wired connection. Select option 6, 'Clear Cache and Rebuild Database', then option 1 'Clear System Software Cache', then 'Ok'. Once this process has completed, you should be able to log back into your PS5 and start Marathon.
- Xbox Series X: Press and hold the power button on your Xbox Series X until it fully shuts down, unplug the power cable from the back of the console, then leave it for a minute or two. Plug it back in, then turn on your console and start Marathon.
Bungie has additional information here, but if the above suggestions fail, you should try fully reinstalling Marathon on your chosen platform.
Marathon error code stingray
If you're seeing error code stingray while trying to play Marathon, that means you're either not signed into your platform account or that there's ongoing maintenance for the platform's services – in short, the problem is likely down to issues on the PlayStation Network, Xbox network, or Steam, so you should check their respective service statuses. Bungie also notes that the stingray code can occur if you try to play Marathon with and expired PlayStation Plus or Xbox Game Pass subscription.
Marathon error code tapir
Error code tapir can appear because of Bungie taking Marathon down for maintenance, so your first port of call should be to check the server status and scheduled maintenance. If Marathon definitely isn't down for maintenance and you're still getting this issue, then you should post on the Marathon help forum as this may be a widespread issue out of your control that affects others too.
Marathon error code weasel
Error code weasel is one of the broadest codes that Bungie uses and typically indicates that you are having a general networking issue, so the way to solve it be to do what you can to improve your online connection – refer to the list of possible fixes at the top of this guide! However, if the issues are on your ISP's end, you might just have to be patient until things are resolved.
Weasel errors can also sometimes occur when logging into Marathon on multiple platforms at the same time, so maybe don't do that.
What happens if I disconnect in Marathon?
If Marathon crashes or you get disconnected, your Marathon character will stay in the match but will obviously be completely unable to do anything. You will have to rely on your crew to protect you and hope that another player or the UESC don't come along and kill you, wiping your inventory and any Marathon weapons you had. If you're able to log back into Marathon without issue, you should be able to reconnect to the match and your Runner Shell, letting you finish off your run.
If you get disconnected due to a server error or something else on Bungie's end, the studio says that reconnecting to a match might not be possible, but it will try to return your starting gear to you, though this isn't guaranteed.
© GamesRadar+. Not to be reproduced without permission.
You must confirm your public display name before commenting
Please logout and then login again, you will then be prompted to enter your display name.
