Forgot password
Enter the email address you used when you joined and we'll send you instructions to reset your password.
If you used Apple or Google to create your account, this process will create a password for your existing account.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Reset password instructions sent. If you have an account with us, you will receive an email within a few minutes.
Something went wrong. Try again or contact support if the problem persists.
Destiny 2 The Final Shape Trailer Reveals the End of Light & Darkness, Release Date
Image via Bungie
Category:
Video Games
News

Why Destiny 2 Is Getting Hit With Error Codes Coconut, Currant, Centipede and Cabbage

Image of Alex Berry
Alex Berry
|

Published: Sep 20, 2023 09:17 am

If you’re having trouble loading into Destiny 2 or getting kicked off the game and receiving an error code, you’re not alone! Tons and tons of players are experiencing connection issues with Destiny 2 and and are seeing all kinds of error codes likes Coconut, Currant, Centipede, and Cabbage. Bungie has now revealed there may be a larger reason why that’s happening.

Recommended Videos

The error codes Coconut, Currant, Centipede and Cabbage are all issues related to networking. These are usually entirely limited to players own internet connectivity to the servers as the reason to be served one of these error codes. The reason players all over the world are suddenly experiencing these codes en masse however is due to Destiny 2 being under a DDoS attack. Bungie confirmed on their X account that the root cause of the error codes is due to the denial of service attack the game is currently suffering. They usually don’t announce when they’re being attacked and deal with the issue quickly for security reasons. This means that this DDoS attack in particular is quite severe. Sounds like someone sure wasn’t happy with their Exotic drops!

Related: Destiny 2 The Final Shape Trailer Reveals the End of Light & Darkness, Release Date

For now there won’t be much players can actually do to resolve these error codes in Destiny 2 until Bungie can navigate the DDoS attack. For what it’s worth, prior to sending out that message, Bungie said that the issues should be resolved for players. The company also noted that their update on why servers were down was not something they generally confirm for security reasons, though in this instance, they felt it necessary to inform players about what was going on.

If you still find you’re getting those error codes, keep an eye on the Bungie Help X account for updates on the situation.

Post Tag:
Destiny 2
The Escapist is supported by our audience. When you purchase through links on our site, we may earn a small affiliate commission. Learn more about our Affiliate Policy
related content
Author
Image of Alex Berry
Alex Berry
Alex Berry has been a freelance contributor at The Escapist since January 2023. His coverage ranges from funny takes on the latest games to a whole bunch of guide content on such titles as Honkai: Star Rail, Genshin Impact, and various new games. Alex is a jack of all trades when it comes to games, playing almost every new title that shows promise. From RPGs to shooters, all the way through to sports games, he plays it all, although he does have a soft spot for turn-based RPGs having started out his gaming journey with a copy of Pokémon Red on the original Game Boy. Alex has a master's degree in Business and is fascinated by online game economies, often spending a lot of time finding ways to maximize wealth in these games (but he should really be doing that in real life instead).
twitter