[Update: Jan. 3] Destiny 2 server error code Bat, Weasel & Porpoise under investigation

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.


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.


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.


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.

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.

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.

Want to work for PiunikaWeb and enjoy best-in-industry compensation & benefits? You'll be glad to know we're hiring experienced candidates.

Akhilesh Singh