It looks like Destiny 2 suffering through connection issues again this January 28, as players are reporting that they are stuck in queue or in orbit. Bungie has acknowledged the error issues that have surfaced where players will see “Coconut,” “Currant” and “Cabbage” errors pop up.
Destiny 2 Connection Errors This January 28:
Update: Issues have been sorted according to Bungie:
Issues causing Destiny 2 players to experience elevated error codes COCONUT, CURRANT, and CABBAGE have subsided. https://t.co/4hzITVx3sq
— Bungie Help (@BungieHelp) January 28, 2023
While Destiny 2 players can connect to the server (meaning it’s not actually down like what happened earlier in the week), multiple reports have surfaced stating of long wait times and the like.
NAT types? from DestinyTheGame
The studio acknowledged the errors as well:
We are investigating issues causing Destiny 2 players to encounter the following errors: COCONUT, CURRANT, CABBAGE
— Bungie Help (@BungieHelp) January 28, 2023
Once the studio posts an update regarding the issue, we’ll update the article accordingly. If you can connect (or can’t connect), leave a comment below and let us know what platform you’re on and connecting from where.
More Destiny 2 Reading: