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
-
1 ReplySubject: Constant CURRANT and CENTIPEDE errors in Italy / EU - Solo activities affected too "@BNGHelp8 Hi, I'm playing from Italy on a flawless FTTH fiber connection (wired ethernet, DMZ active, perfect open NAT, and all ports forwarded). Yet, the game is completely unplayable. I constantly get hit by 4-5 CENTIPEDE errors just to reach the character selection screen. Once I finally manage to get into orbit, I get slammed with CURRANT errors whenever I try to load any destination—even when launching solo activities like Lost Sectors completely on my own. This is clearly a routing/server-side issue affecting the EU/Italian player base right now. Our local networks are perfectly fine. Can we please get an official update or a real investigation into these server bottlenecks? Thanks."
-
@BNGHelp8 any updates??
-
Edited by NinjaTomBot: 7/14/2026 10:34:34 PMSame here, already made a post but no fix yet. I also tried some different VPNs and sometimes it works and other times not. I'm losing faith if it's ever going to be fixed.
-
Edited by Kadgulu: 7/15/2026 6:37:42 PMSame problem. I get centipede error then just 1 time I had oppurtunity to enter the game and the currant error occured to me Edit: I tried 2 more times first didn't land on the planet then the currant error but now I am able to play the game. So I hope you folks can also play the game as soon as possible
-
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.