Destiny 2 BABOON

Bungie names this code but does not publish the wording it prints on screen, so we quote only the code itself: BABOON. Any site showing you an exact message for it has written one.

What it actually means

Bungie describes it as a tracked networking error and names the causes: “This error can be due to packet loss or disconnections between your home network and Bungie (such as ISP saturation or general internet congestion)… or mobile hotspots that may have experienced a blip.”

It commonly appears paired with WEASEL in a loop where sign-in keeps failing, which is why people search for both together.

How to tell which one you have

If it arrives in bursts and clears on its own, that is congestion. If it arrives and then nothing works until you force quit, the client is in a stuck state. If it is everywhere at once, check the status above — BABOON is one of the codes that floods during a Bungie outage.

Fixes, in the order worth trying

1. Use a wired connection — Bungie puts this first. Hotspots and Wi-Fi are both named in their own description of the cause.
2. Force quit the game rather than restarting it — Bungie publishes per-platform instructions for this, covering PlayStation and Xbox generations separately. Quitting from the dashboard is not the same as closing the game, and for the stuck cases only the force quit works.
3. Free up the connection — Another device saturating the line produces exactly this error, and it is the easiest cause to rule out.

Operator documentation: help.bungie.net. Bungie documents its error codes in a public directory of over 300 articles. Those articles describe causes and fixes and never quote the in-game dialog, so neither do we.

Common questions