New updates are being added at the bottom of this story…….

Original story (published on June 25, 2021) follows:

Bungie Inc’s free-to-play online multiplayer first-person shooter — Destiny 2 — has been one of the best multiplayer games going around for the past couple of years.

Destiny 2 has seen a constant rise in the number of active players ever since the game went free to play, opening up the game for everyone.

destiny2

With the rise in players every day Bungie Inc is having a hard time maintaining Destiny 2 servers.

Players are reporting that they are facing trouble playing the game and getting error codes Bat, Weasel & Porpoise.

It looks like error codes Bat and Weasel are related to servers being down or being at their limit.

destiny2
(Source)

Error code Bat and Weasel trying to do the seasonal comp challenge now. Also contacting Destiny 2 Servers.

Clearly issues with the game, as no other internet problems (and obviously I can post on twitter Face with rolling eyes) (Source)

Impossible to play the game since I get Contacting Destiny 2 Servers on every login then a Baboon with Bat error code during Trials.
@BungieHelp (Source)

Bungie Help has acknowledged and their team is investigating all the issues that players are facing and will soon provide an update on the situation.

Destiny-2-server-down
(Source)

This isn’t a one-off incident. Destiny 2 players have been facing these server issues from time to time in the recent past.

Bungie needs to get its house in order and solve these server issues once and for all, if it cares about Destiny 2 players.

We are hopeful that Bungie Inc will address these issues soon and fix all of them.

In the meantime, we will continue to track all the developments related to Destiny 2 and update you once any relevant information becomes available.

Click/tap to view older updates

Update 1 (June 26, 2021)

Bungie has confirmed that the issues causing error codes Weasel, Rabbit, and Porpoise have subsided. Hence, players shouldn’t notice these errors often. However, the team is still investigating issues that lead to the error code Bat.

Issues causing Destiny 2 players to experience elevated error codes WEASEL, RABBIT and PORPOISE have subsided. We are continuing to investigate issues causing Destiny 2 players to receive error code BAT. (Source)

Update 2 (January 31, 2022)

Players have again begun reporting about the CHICKEN, WEASEL, and CENTIPEDE connection errors (1, 2, 3, 4, 5, 6, 7, 8) which are preventing them from entering the matches.

While Bungie has acknowledged these errors and worked on mitigating them, players can still encounter the errors until a permanent fix arrives, which should come soon.

@BungieHelp I am still unable to login to Destiny 2. I keep getting Chicken errors, and there are multiple people reporting the same issue on the forums, as well as our characters not showing up on our accounts. Do you have any updates on this issue? (Source)

@DestinyTheGame this is ridiculous. Constant Weasel and Centipede. How can you charge people for new stuff and they can’t even play it!!!!! Before you say it’s my network, I have a static ip and all relevant ports are forwarded!!! (Source)

@BungieHelp cant get inside Destiny 2.. something is wrong at your side! check it out?.. getting chicken and centipede error codes! and nothing is wrong with my connection (Source)

Update 3 (December 02, 2022)

10:54 am (IST): Many Destiny 2 players are now reporting (1, 2) that they are getting ‘weasel’ and ‘bee’ error codes.

Its worth mentioning that devs have recently extended the server maintenance and the abovementioned errors could be related to that. However, support is yet to acknowledge these error codes.

12:46 pm (IST): Several Destiny 2 players are reporting (1, 2, 3) that they are facing issues with matchmaking even after the maintenance is completed.

Luckily, Bungie support has acknowledged this issue and said that they are investigating it. However, there’s no ETA for the fix.

This maintenance is complete. Destiny 1 and 2 are online, though matchmaking issues remain. Players can still join on other players’ activities, but cannot matchmake otherwise. We’ll continue to post updates as we investigate. (Source)

Update 4 (January 03, 2023)

12:34 pm (IST): Bungie support has confirmed that they have fixed the issue where players are getting WEASEL and CALABRESE error codes.

Issues causing Destiny 2 players to experience elevated error codes WEASEL and CALABRESE have subsided.
(source)

Update 5 (April 25, 2023)

08:18 am (IST): Destiny 2 players are again dealing with multiple error codes when trying to log in or looking for matches (1, 2, 3). Bungie team has acknowledged the issue, but no ETA for a fix yet.

Update 6 (April 26, 2023)

10:00 am (IST): Bungie team confirmed that the issue has already been fixed.

Update 7 (May 1, 2023)

02:26 pm (IST): Some Destiny 2 players are again receiving the error code ‘Calabrese’.

Update 8 (May 10, 2023)

04:34 pm (IST): Destiny 2 players continue to report (1, 2, 3, 4, 5) the issue where they are getting different error codes after the latest v7.0.5.3 update including ‘CHICKEN’, ‘Plum’, ‘Weasel’ & other error codes.

In the recent acknowledgment, the support team has confirmed that they are aware of these error codes and currently investigating. However, they didn’t provide any ETA for the fix.

Update 9 (May 12, 2023)

06:00 pm (IST): Destiny 2 players continue to report error messages (like ‘CHICKEN’) appearing in the last few hours (1, 2).

Update 10 (June 6, 2023)

12:25 pm (IST): Bungie team is investigating an issue where players are constantly receiving a MONKEY error code.

Update 11 (June 7, 2023)

03:41 pm (IST): Reports regarding the Destiny 2 ‘MONKEY’ error code stopped surfacing several hours ago.

Update 12 (June 8, 2023)

12:15 pm (IST): Destiny 2 devs are already aware of the issue where multiple players are unable to log into the game (1, 2).

01:15 pm (IST): Players report (1,2,3,4) getting the Weasel error code that prevents them from entering the game.

Update 13 (June 9, 2023)

12:26 pm (IST): Bungie team performed a server maintenance to resolve error codes and login issues. The company will be monitoring the situation after that.

Update 14 (August 10, 2023)

09:11 am (IST): Destiny 2 is currently down or not working (1, 2, 3) for some players on PlayStation and they are getting error when trying to sign in.

Update 15 (August 11, 2023)

12:22 pm (IST): Destiny 1 servers are in the middle of a maintenance during which the game will be unaccessible. It will conclude at 5 AM PDT (1300 UTC).

06:45 pm (IST): The server maintenance with Destiny 1 has ended.

Update 16 (August 18, 2023)

09:49 am (IST): Some players are reporting (1, 2, 3, 4) that they are getting different errors while playing the game such as LOGANBERRY, error code WEASEL, and other server related issues.

Luckily, Bungie support has acknowledged the problem and asked those affected to report the issue on their official forum. Moreover, they are investigating issues with WEASEL and BEE error codes.

12:46 pm (IST): Bungie support has confirmed that they issue where players are getting WEASEL and BEE error codes has subsided.

The issue causing some players to encounter WEASEL and BEE has subsided. Players still experiencing issues should report to the Help Forums. (Source)

Update 17 (September 19, 2023)

08:09 am (IST): Several Destiny 2 players are reporting new server issues like crashing and being kicked out of matches due to error codes (1, 2).

Update 18 (September 20, 2023)

12:27 pm (IST): Bungie support has confirmed that players are getting error codes due to DDOS attack.

destiny-2-ddos-attack
(Source)

And according to reports (1, 2) from some players, servers have already started working.

Update 19 (September 21, 2023)

08:30 am (IST): Destiny 2 players are reporting new server issues that are preventing them from completing matches since they are being kicked out (1, 2, 3, 4).

Update 20 (September 22, 2023)

09:23 am (IST): Several Destiny 2 players are reporting (1, 2, 3, 4) that the game servers are currently down or unstable.

Update 21 (September 23, 2023)

06:36 pm (IST): Today reports continue to emerge about Destiny 2 server issues where players are unable to access the game (1, 2, 3).

Update 22 (September 25, 2023)

09:07 am (IST): Destiny 2 players continue to report the constant appearance of error codes when trying to access the game (1, 2, 3, 4).

Update 23 (September 26, 2023)

08:32 am (IST): Destiny 2 dev team is currently investigating the issue of constant error codes that are affecting several players.

Update 24 (September 27, 2023)

08:20 am (IST): Destiny 2 server issues are still present (1, 2, 3) while the Bungie dev team continues to investigate to resolve it.

Update 25 (September 29, 2023)

09:12 am (IST): Again, multiple players report the appearance of errors that prevent them from accessing matches or the game itself (1, 2, 3).

Update 26 (October 06, 2023)

08:04 am (IST): Some Destiny users (1,2,3,4) are reporting that the game is not loading for them currently due the the server issues.

Update 27 (October 09, 2023)

07:54 am (IST): Lack of fresh reports suggest that the recent issue has been fixed.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.

Next article View Article

Google Drive not letting users play videos, throws 'allowed playbacks has been exceeded' error

Google Drive users have been dealing with an issue for years where they get an 'allowed playbacks has been exceeded' error when trying to play videos. And Google has still...
Feb 20, 2024 2 Min Read