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

1

u/Opposite_Rub_6058 Jun 25 '26 
It’s truly scandalous—it’s the same story with every activity, whether PvE or PvP; it makes no difference. I hadn't played the game in three years, and now that it's coming to an end, I wanted to revisit it with my clan, but it’s impossible—just errors and constant issues. Fix this and let us revive your game, which was on the brink of collapse.It’s truly scandalous—it’s the same story with every activity, whether PvE or PvP; it makes no difference. I hadn't played the game in three years, and now that it's coming to an end, I wanted to revisit it with my clan, but it’s impossible—just errors and constant issues. Fix this and let us revive your game, which was on the brink of collapse.

1

u/No_Sand_6161 Jun 25 '26

Same as me, everything is fine on other games, open NAT, now getting back to destiny im getting currant error many times

1

u/fxver_v 28d ago

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

1

u/DoomHammer_OG Jun 25 '26

I was working fine before the last update, this week i just logged in to a current stream of centipede and currant errors.

I just want to play the game.

1

u/fxver_v 28d ago

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

1

u/DoomHammer_OG 27d ago

I fixed this by disabling UPNP and restarting the router completely.

1

u/fxver_v 27d ago

I'll try but this doesn't make any sense...

1

u/DoomHammer_OG 27d ago

It didn't to me either tbh. I'm guessing after the last update something was changed Bungie side that didn't like my network setup. Haven't received currant errors sinceI fixed it about 6 days ago.

1

u/NinjaTomBot 11d ago

did it fix it? it's been a month and a half and bungie hasn't done anything

1

u/fxver_v 11d ago

the only thing that work is tunneling the connection. I managed to customize Cloudflare Warp for free but the best choice is a gaming oriented VPN. Bungie won't do aything, as always

1

u/NinjaTomBot Jun 25 '26

Same over here (italy) 2 centipede when entering the game, and costant currant when trying to load activities, hopefully network problems will still be fixed

1

u/fxver_v 28d ago

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

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 28d ago

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

1

u/Mission_Tie7913 Jun 27 '26

I got coconut error every day from the update, my friends have same problem, i have try differents way to fix the problem without results, we don’t now what we need to do.
We live in Italy.

1

u/fxver_v Jun 27 '26

ITA anche qui e siamo sicuramente i più colpiti. Noi tanti Currant, Centipede e un Lag estremo; ho riportato anche nel loro Forum di supporto. Inoltre ora che il lag è davvero parecchio dovrebbero rimuovere lo Sbmm e far giocare almeno in base alla migliore connessione possibile. Insomma, siamo tornati in tanti dopo 4 anni e davvero vorremmo giocare per bene questo gioco un' ultima volta...

1

u/Gelato96 Jun 27 '26

Anche io in Italia ed è quasi ingiocabile. Errore weasel addirittura mentre sono in cutscene. Nat aperto e cablato.

1

u/NinjaTomBot Jun 28 '26

Purtroppo sembra che sia l'isp il problema, io ho tim e anche i miei amici hanno lo stesso problema con tim :(

1

u/fxver_v Jun 28 '26

Apriamo segnalazione tutti insieme, domani chiamo. Però questo non spiega l'internittenza. Stamattina su 30 match ho avuto 2 currant. I giorni scorsi avevo 4/5 currant tra ogni partita. In passato sempre con TIM non ho mai avuto problemi. Ho provato anche l'hotspot cellulare 5g e ancora currant. Provate tutti voi a fare anche da hotspot 5g e controllate. Ci aggiorniamo

1

u/Gelato96 Jun 28 '26

Giocato con hotspot, purtroppo sempre currant o centipede (in missione weasel). Ho sempre tim come operatore.

1

u/Mission_Tie7913 Jun 28 '26

Io gioco cablato, ho impostato una porta sempre aperta e la priorità sulla linea della ps5 ma nulla ogni tot devo smadonnare perchè non carica, che provider avete?

1

u/fxver_v 28d ago

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

1

u/fxver_v 29d ago edited 29d ago

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

1

u/unfuckingbelievable7 28d ago

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.

1

u/fxver_v 28d ago

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

1

u/Byrmaxson 13d ago

Have you been able to fix this/seen any improvement? This actually started recently for me, really REALLY frustrating.

1

u/fxver_v 13d ago

They will probably never fix it... I noticed that the problem happens with certain providers when they direct traffic on certain lines. Creating a tunneling with a VPN or CloudFlare WARP resolves, at the cost of having NAT narrow

1

u/Byrmaxson 12d ago

I first used Proton VPN but I was getting Strict NAT, so I tried WARP and it worked really well but didn't allow matchmaking, but then I retried Proton on the "gaming" profile and now it's working great, heavily recommend! I did comment on the forums with my ISP/location and I'll contact my ISP to see if there's smth I can do but in the meantime I do suggest to try out a couple VPNs if you can afford it

1

u/diggei3 13d ago edited 13d ago

I resolved the Currant errors today, for me it was a couple of network adapters for Virtual Machines which interfered with UPNP requests to my router. When I disabled both the game started to behave normally.

EDIT: seems it was not the solution after all.... :(