{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/14/2026 4:24:11 PM
5
Currant error code
Currant error code is still a big issue.
>Trying to farm a lost sector getting 4-5 errors until the game finally lets me load in the planet.
>Trying to start the lost sector getting 4-5 errors that [b]take me back to orbit[/b] until I finally can complete a lost sector.
>After completing the lost sector I get sent back to orbit instead of the flag at the entrance of the sector because of error code [b]CURRANT[/b].
It is so exhausting trying to play the game at this state.
PvP is even worse when playing with a fireteam because my teammates get suspended for [b]QUITTING A MATCH THAT NEVER STARTED [/b] , even in control because of this error.
Many players have been facing this issue in East EU.
The network troubleshooting guide offers no help.
Connection is stable, ISP has been contacted and don't see issues on their end, other multiplayer games run perfectly.
Please give us an update on this
-
Yep. I'm italian and I'm in your same exact boat, and so are many others from the EU area. Another week, another 4 Centipede errors before I somehow managed to log in only to get immediately hit by Currant as soon as I tried to load into the tower. It's so damn tiresome at this point. I'm a returning player, I came back shortly after the MoT update and I've had these issues constantly. I don't think I would have bothered, had I known the game was going to be unplayable.
