{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
6/27/2026 12:23:00 PM
2
Error: Currant
Currant currant currant currant rabbit currant currant. 9 out of 10 activities started end up giving these errors. It is also a continuous ban on Trials, Crucible and Gambit.
To give some context:
- 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.
-
5 RisposteHello there, Thanks for the report. Currant means the game failed to connect you to the activity server, so if this is happening in most activities and you are also seeing repeated “Contacting Destiny 2 Servers” messages and delayed hit registration, that does not sound like normal gameplay behavior. If multiple players across different ISPs and locations are all running into the same thing around the same time, that also points away from this being just one person’s home setup. The suspension part is also unfortunately expected if the game treats the disconnect like leaving a match early in Trials, Crucible, or Gambit. Please keep reporting your platform, region, and whether this is happening in all activities or mostly PvP/Gambit. Thanks for calling it out.
-
Modificato da Fxver: 6/30/2026 10:24:51 AMUPDATE; Today among the continuous Currant and Centipede, I also had an Error Code: HARE
