Destiny 2 BEAVER

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

What it actually means

Bungie groups three codes together and names the mechanism: “BEAVER/FLATWORM/LEOPARD errors are caused by a failure to connect your console to another player's console via the internet… However, they are most commonly caused by router or network configuration issues.”

The key phrase is console to console. This is peer connectivity, not your link to Bungie, which is why it shows up in activities with other players rather than at sign-in.

Bungie is explicit about the biggest single factor: “Strict NATs tend to see these errors far more often than Open or Moderate NATs.”

How to tell which one you have

If sign-in works and the error only hits once you are matched with other players, this is peer connectivity. If several consoles share your router, that makes it more likely rather than less.

Fixes, in the order worth trying

1. Open your NAT type — This is the fix, and the rest are variations on it. Strict NAT is Bungie's own named culprit.
2. Enable UPnP on the router — The low-effort route to an open NAT, and usually enough on its own.
3. Use a wired connection — Packet loss breaks peer handshakes, and Wi-Fi is where packet loss lives.
4. Follow Bungie's network guide for port configuration — If UPnP is unavailable or disabled by your ISP's router, manual forwarding is the remaining option.

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