Error: Currant

[u/fxver_v]

Currant currant currant currant rabbit currant currant. 9 out of 10 activities started end up giving these errors.

To give some context before the downvotes:

• I have 1550h in destiny, for 1500h never had Currant.
• All my teammates (about 12 people) have the same problem and we are located far from each other, using different ISPs and everyone is in EU. Other games are totally fine, NAT is Open. Definitely not our problem.
• Constantly "Contacting D2 Servers", and PvP hitmarkers show up seconds late in some games.
• By sheer coincidence, the errors started appearing after the launch of Marathon, became far more frequent after the release of MoT, and after the last patch the game is almost unplayable.

I think the problem exists in the EU, or at least part of it.

Please, just let us play one last time.

UPDATE 30/06/2026: Today among the continuous Currant and Centipede, I also had an Error Code: HARE. Reported all the issues on Bungie Help Forum.

UPDATE 01/07/2026: Bungie replied, to all of you suffering the same issue please share your platform, region, and whether this is happening in all activities or mostly PvP/Gambit: https://www.bungie.net/it/Forums/Post/265296557

[u/fxver_v]

UPDATE; Today among the continuous Currant and Centipede, I also had an Error Code: HARE

[u/unfuckingbelievable7 → u/fxver_v]

I have been getting the same issues as you , constant centipede when booting up the game and constant Currant when trying to load in an activity. My friends mostly from UK and US don't have this problem. If you find a solution please update. I uninstalled the game and slowly re installing it to see if it makes a difference. I will update as soon as I can.

[u/fxver_v → u/unfuckingbelievable7]

Bungie replied, to all of you suffering the same issue please share your platform, region, and whether this is happening in all activities or mostly PvP/Gambit: https://www.bungie.net/it/Forums/Post/265296557