If you are getting the error code ‘Currant’ while trying to play Bungie’s Marathon and are unable to connect to Marathon servers, and don’t know what is going on and how to fix it, I’ve got you covered.
Currant is one of the many error codes in Marathon, with another example being Anteater, etc, that players encounter while playing the game.
While each error code is unique, one thing that remains the same is the fact that players are unable to play the game due to these errors.
In this guide, I have explained the possible reasons for the Currant error code in Marathon while talking about possible workarounds and fixes, sort of.
What is error code Currant in Marathon?
The error code Currant arises whenever there is a network-related issue with Marathon.
To put it in simple words, when your game client is unable to establish a connection with the game servers.
There are two main reasons behind this:
- Bungie’s Marathon game servers are down or overloaded, or not working as intended. [Server Side.]
- Your internet connection is not working or is blocking the game. [Issue from your end.]
Related: Marathon redeem codes
How to fix the error code Currant
To fix the error code Currant, first you must check whether Marathon’s game servers are up and running.
If they indeed are working fine and there are no reported issues, the second thing that you must check is if your internet connection is working.
I am sure you may have already checked it. If your internet was not working, how did you check the Marathon server status?
If you are still getting the error code Currant, head to your ‘Firewall & network protection settings’ and select the ‘Allow an app through Firewall’ option.
Make sure the ‘Public’ and ‘Private’ boxes are checked besides Marathon. If you are on a wireless network, it’s best to switch to a LAN, of course, if possible.
Lastly, if everything is good and you are still getting the same error, I recommend contacting your ISP (Internet Service Provider), as some of them block certain applications.
Also, make sure your NAT Type is Open. If it is Strict, it may be causing the issue. If you are worried about Secure Connection, switching the NAT Type to Moderate is fine.
If you have a better working fix for the issue, let me know in the comments, and I will update the article.
