{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by BNGHelp5:
8/26/2024 6:21:19 PM
15
STILL huge Cabbage and Currant-issues in Europe!!
Bungie, can we PLEASE get SOME communication from you on this matter?
Destiny is the only game online-game not working properly for me atm. It has been like this for me and many others for almost a week at this point. Even if the problem does not lie with you then surely you know more about the situation than we do?
Many of us that are affected seem to have Telia as our ISP. I'm sure there are more countries and ISPs that are involved in this.
Please, any information as to what the problem is and when it might be fixed would be greatly appreciated!
Best regards!
-
4 RepliesHi there, Thanks for reaching out! We recommend you refer to our Network Troubleshooting Guide to explore potential solutions to your problem: https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide If you continue experiencing this error after trying our network troubleshooting, please contact your internet service provider for further assistance.
-
1 ReplyThe disconnection has stopped for me, i have played 2 days without the error popping up
-
1 ReplySame here, tried fiddling around with all types of network settings like Bungie said on the troubleshooting guide, however nothing changed and the problem persists. Located in Sweden if that makes any difference!
-
2 RepliesEdited by Dooodley: 8/26/2024 5:37:23 PMBungie just keeps posting the same standard "check your settings" reply. We are not network engineers and a bunch of us probably know little to nothing about this stuff so before fiddling with even more stuff they could at least try to clarify what the issue could be or assure us that the problem is not on their end. At this point everything seems to be pointing at their end though because: * No reports of issues in other games and applications * Nothing on the ISP sites * My ISP (I'm not using Telia) had no issues * No reports of problems from non-D2 players on the big Swedish forums * Issues started after the patch last week Additionally I've reset all my hardware, flushed DNS, tried two different routers and ran straight from the fiber socket. Everything els has worked under all those conditions, except for D2. The game is literally unplayable. Tried to do a lost sector just now. Took three tries just to not land in blackscreen in the cosmodrome. Finally managed to load in but have to switch area for where the lost sector is located. That's when I obviously come in conflict with other players in that area so I'm getting thrown out again. I try another time, get all the way to the lost sector, launch it....and is sent to orbit with one of the two errors. The whole thing is also inconsistent as hell because just minutes before that I had been to what looked like a tower full of players. Also, for the longest time now -prior to all the errors - I've constantly and consistenly been matched with/against players with east asian names and letters. I don't know if that's just some new thing among westerners to type in mandarin and whatnot now or if the game is completely bonkers in terms of matching and regions. And no, I'm not running a VPN.
-
2 RepliesI've also had this issue. really annoying and ive done what the troubleshooting guide they have has told me. nothing changed. it is only destiny that doesnt work. and Im not even sure if they are aware of the issue
-
The same problem, constant errors
-
Edited by Miwenskee: 8/27/2024 10:33:34 PMCan confirm. Located in Scandinavia, Telia is my ISP, and I've been getting cabbage and currant exclusively and consistently for the past 3 days! Changed router settings, enabled UPnP, didn't seem to fix the issue.
-
I've been sitting here ripping my hair out for the past couple of days, trying to figure out what's going on.. Finally finding this thread knowing I'm not alone is honestly good to hear. I'm also using Telia as my ISP and the issue started happening 4 - 6 days ago randomly. Staying away from Destiny 2 atm since every other instance or so I just get booted out of because of the damn cabbage/currant error code.
-
I've had similar issues for almost 2 weeks. I'm using Telia (wired connection) and I haven't had any issues until now. I didn't change my router settings and after the Solstice update, and I had to change my Bungie name for no reason, and I've never changed it. After that, I've been getting ''centipede'' error code when I log into the game, and ''rabbit'' and ''centipede'' error codes every day. It even says that I have NAT type 3, even though PS5 says it's type 2. There are times when I can't even load into the Tower or join my friends. I have tried Bungie's troubleshooting guides and even reset my router, which helped for a moment but rhe next day I kept getting the same error codes. I don't have these issues in other games. In The Division 2 I had a similar issue where I suddenly had moderately high ping and experienced some packet loss, which led to en error code, but that hasn't happened once and it's been fine since that. I don't know what the problem is and nothing seems to help. I don't think it's the ISP's fault, because everything else seems to be working fine.
-
Am Swedish and I have the exact same problem.
-
-
I have same problem, tried wired, wifi, connecting directly to the fiberbox. Same error I have even tried with a new ps5. Also tried connecting with mobile internet, and get same error.
-
Same here so annoying
-
1 ReplyI’ve been reading these posts today and Bungie has been answering by linking to their trouble shooting guide or asking for people to contact their service provider. It seems they have no idea what’s going on…
-
Same for me! I can play every game without any issues. But in destiny2 i get cabbage or currant error code all the time. This is really anoying i have been banned from certain playlists and activity due to "match incomplete" but it is not my fault! Fix this fast!
