What does Destiny 2 Error Code 'Chicken' mean?

The short answer

Error code Chicken in Destiny 2 means your game lost connection to Bungie’s servers, usually because of a network issue on your end or a server-side problem.

Why does it happen?

Destiny 2 uses animal-themed names for its error codes. Chicken specifically relates to network connectivity problems. The most common causes are:

  • Bungie’s servers are having issues — during maintenance, major updates, or high-traffic events like expansion launches, their servers can struggle or go offline
  • Your internet connection is unstable — packet loss, high latency, or brief disconnects can all trigger this error
  • NAT type restrictions — a strict NAT type can prevent your device from properly communicating with Bungie’s servers
  • ISP or routing issues — sometimes the problem is between your network and Bungie’s servers, not on either end directly

How to fix it

Try these steps in order:

  1. Check Bungie’s server status — visit Bungie’s help page or their social media for any known outages
  2. Restart the game — close Destiny 2 completely and relaunch it
  3. Restart your router — unplug it for 30 seconds, then plug it back in and wait for a full reconnect
  4. Use a wired connection — Wi-Fi is less stable than ethernet, and Destiny 2 is sensitive to connection quality
  5. Check your NAT type — you want an Open or Type 1/2 NAT. If it’s Strict, enable UPnP on your router or set up port forwarding for Destiny 2
  6. Disable VPN or proxy — these add extra hops that can cause connection drops
  7. Clear your console or Steam cache — on console, power cycle the device. On PC, verify game files through Steam

When should you worry?

In most cases, error code Chicken is temporary.

  • If Bungie reports an outage, just wait it out. Server issues typically resolve within a few hours
  • If the error only affects you, focus on your own network. The steps above should resolve it
  • If it happens repeatedly, your connection may not meet the stability Destiny 2 requires. Try connecting during off-peak hours or contact your ISP about packet loss