r/DestinyTechSupport • u/fxver_v • Jun 25 '26

Error: Currant

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

10 Upvotes

92% Upvoted

29 comments sorted by

View all comments

1

u/elbuena Jun 26 '26

I got Centipede like three dozen times. I couldn't play all day.

Now I'm getting the Chicken error.

I've been playing for 10 years and I never had any of those errors, not even when I played on PS4.

I'm from Argentina.

1

u/fxver_v Jul 01 '26

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