Those trying to get their Destiny 2 fix in advance of Shadowkeep may have run into some difficulty actually accessing the game. That’s right, much like the Gears 5 error that was kicking around yesterday, Guardians today are having some issues with interrupted connections and a very specific problem. We’ll tell you what the Destiny 2 Error Code Currant is and what you can do, if anything, to fix it.
Destiny 2 Error Code Currant: What Is It?
If you’ve been able to load into Destiny 2, gotten yourself into orbit, and then been unceremoniously shown that you’re suffering from the Currant error when you try to crack onto a mission, then you’re definitely not alone. There have been a spate of occurrences of this particular error code ever since the launch of the Season of Opulence, so it’s not entirely new at this stage, but it definitely cuts down on the time that you’re going to have to hit your in-game goals before Shadowkeep launches on October 1.
Now, what does the Destiny 2 Error Code “Currant” actually mean? According to Bungie’s official Help articles, Currant errors are ones that the team actively monitors because of their nature: they’re connection issues. The reason why players might get a Currant error are, as per Bungie:
- ISP issues
- Packet loss
- Complications with network hardware
- Wi-fi glitches
- Anything that affects connection stability
If any of those issues sound familiar to you, then maybe going through the game’s Network Troubleshooting Guide might be a way to start dealing with this pesky Currant error code. Some players have reported that they’re only encountering this error when they’re trying to load into a Gambit match, so if you’re otherwise having a seamless Destiny 2 experience then our recommendation would be to stay away from that mode for now until all issues are fully resolved. We know that the game will be down as well on 30 September for maintenance and only come back up when Shadowkeep drops on 1 October, so pencil that into your diaries!
