Destiny 2 Not Working: What’s Going On and What to Do
When Destiny 2 isn’t working, the cause is rarely one single thing. The game might refuse to launch, get stuck updating, drop you with a weasel or centipede error, crash to desktop, or lock you out of an activity. Some faults sit on Bungie’s side, others come from your device, network, or NAT type, and a tool like Planet VPN only helps with a few of them. This guide walks through each symptom, how to tell a real outage from a local issue, and the fix that actually applies.
Why Is Destiny 2 Not Working?
Destiny 2 leans heavily on the network: a stable route to Bungie’s servers, an open NAT type, your platform’s online service, and your GPU drivers. When any one of them slips, you get one of Destiny’s colourfully named error codes.
The usual causes are a wobbly or throttled connection, a strict NAT type, server maintenance, a crossplay setting, or an outdated GPU driver. Network blocks matter too, since some school, work, and public Wi-Fi networks block game traffic.
How to Fix
- Check the Destiny 2 server status and @BungieHelp before you change anything.
- Power cycle your console or router, then relaunch.
- Switch to a wired Ethernet connection.
- Open your NAT type or enable UPnP in your router settings.
- Update your GPU and network drivers.
- Clear the game cache or verify files on PC.
Is Destiny 2 Down, or Is It Just You?
A real outage hits everyone at once: mass disconnects, an endive error, or failed logins across a whole platform, often during Bungie’s scheduled maintenance around the weekly reset. If only you are affected while friends play fine, the problem is local. Bungie posts maintenance and known issues on its help channels.
How to Fix
- Check help.bungie.net and @BungieHelp for maintenance or outage notices.
- Look at Downdetector for a spike in reports from other players.
- Check your platform status too, at the PlayStation or Xbox status pages.
- If it’s maintenance (error code endive), wait for the window to finish.
- If servers are up but you still can’t connect, the problem is on your side, so move to the fixes below.
Tip: Bungie’s maintenance usually lands around the Tuesday weekly reset. If you hit an endive error or mass disconnects near reset time, it’s scheduled downtime, not your setup, so check @BungieHelp before you start troubleshooting.
When a VPN Can Help with Destiny 2
A VPN reroutes your traffic and hides your real IP, which helps with some Destiny 2 problems and not others. It can steady things when your ISP throttles gaming traffic, when your school, office, or hotel Wi-Fi blocks the game, or when a poor route to Bungie is adding packet loss. A good VPN for Destiny 2 also hides your IP from targeted DDoS attacks, which competitive Crucible and Trials players are exposed to.
A VPN cannot fix a Bungie outage, an endive maintenance error, an account ban, a strict NAT that your router controls, or a GPU-driver crash. If Destiny’s servers are down for everyone, no server change will bring them back. Use a VPN for a steadier, more private connection, not as a cure for every error.
Destiny 2 Not Working With a VPN
Destiny 2 is picky about connection changes. A VPN can restore access on a blocked network, but an unstable or distant server can also trigger weasel and centipede errors. Importantly, if Cross Save is enabled and you appear to log in from two places at once, Bungie hands you a weasel error on the first platform, so a VPN can occasionally look like the cause.
How to Fix
- If errors appear only with the VPN on, toggle it off to test.
- Switch to a different, gaming-optimised server close to your usual region.
- Restart the VPN and start a fresh connection before launching.
- Don’t log in on a second platform while Cross Save is active.
- Pair the VPN with a wired connection and an open NAT for stability.
- Switch protocol or enable obfuscation if your network fights VPNs.
Keep it honest: connect to a server in the region your account plays on. A distant server usually adds ping and packet loss, which Destiny handles badly, so use a VPN for stability, access, and privacy, not to force into another region.
Why Can’t I Access Destiny 2?
If Destiny 2 works elsewhere but not on one network, something between you and Bungie is blocking it, or your NAT is too strict. Schools, offices, hotels, and public Wi-Fi often block game traffic, and a strict NAT type can stop matchmaking. Occasionally the block runs the other way, and a shared VPN or proxy IP is rejected.
How to Fix
- Try a different network or a phone hotspot to confirm it’s a network block.
- On restricted Wi-Fi, connect through a VPN to route around the local filter.
- Open your NAT type or enable UPnP so matchmaking can connect.
- If a VPN or proxy IP is being rejected, switch servers or disable the VPN to test.
Destiny 2 Won’t Launch
You press Play and nothing opens, or you get a broccoli error that means your device couldn’t detect the GPU. This usually points to an outdated or broken graphics driver, a launcher problem, or damaged files.
How to Fix
- Update or cleanly reinstall your GPU drivers, then restart the PC.
- Verify or repair the game files through Steam or the Epic launcher.
- Power cycle your console if it won’t launch there.
- Close overlays and background apps that hook the game.
- Run the launcher as administrator on PC.
- Reinstall Destiny 2 as a last resort.
Destiny 2 Stuck on Loading or Won’t Update
A frozen loading screen or an infinite spinner usually means a network hiccup, a patch that hasn’t finished, or corrupted files. Right after an update, a version mismatch can also hang the load.
How to Fix
- Let the launcher finish downloading the update to 100 percent.
- Verify or repair the game files.
- Restart the game and your router.
- Clear the console cache or the launcher’s download cache.
- Pause downloads on other devices to free bandwidth.
Destiny 2 Connection Errors and Disconnects
The classic Destiny disconnect codes are weasel, centipede, baboon, anteater, and chicken. Weasel is Bungie’s all-encompassing network error, centipede means you lost connection to your network or your NAT is too strict, baboon means you were removed from the game world, and chicken means no internet was detected. Most are connection-side, though weasel can rarely signal an account ban.
How to Fix
- Power cycle your router and console, and switch to a wired connection.
- Open your NAT type or enable UPnP in your router.
- Close other apps and downloads that are eating bandwidth.
- Clear the game cache, then relaunch.
- If everyone is affected, check @BungieHelp and wait for a server-side fix.
Destiny 2 NAT and Crossplay Issues
Some Destiny codes are about how players connect to each other, not to Bungie. Beaver means a failed peer connection, bee points to a bandwidth imbalance on your network, and chickpea appears when a fireteam member turns off crossplay during an activity. A strict NAT type is the usual root cause behind poor matchmaking.
How to Fix
- Set your NAT type to Open or Type 1 where your network allows it.
- Enable UPnP, or manually forward Destiny 2’s ports.
- Close bandwidth-heavy apps for bee errors.
- For chickpea, have your fireteam re-enable crossplay in settings.
- Use a wired connection to steady peer connections.
Destiny 2 Keeps Crashing
Crashes to desktop or a broccoli error usually trace to a GPU driver problem, an overlay conflict, overheating, or corrupted files. If it only happens on your machine, it’s local rather than a Bungie outage.
How to Fix
- Update or reinstall your GPU drivers and update Windows.
- Verify or repair the game files.
- Turn off overlays like Discord and GeForce Experience.
- Try running the game in windowed or borderless mode.
- Check for overheating and improve airflow.
- Reinstall if crashes continue after a patch.
Destiny 2 Lag and Packet Loss
Rubber-banding, delayed abilities, and stutters are usually caused by packet loss or an overloaded route, not a full outage. Destiny is known to spike bandwidth use, so other downloads on your network can tip it over into lag.
How to Fix
- Test your ping and packet loss, not just download speed.
- Switch to a wired Ethernet connection.
- Close background downloads and streaming on your network.
- Open your NAT type to improve matchmaking quality.
- If your ISP routes poorly, a nearer VPN server can steady the path, though it can add ping, so test both.
Common Destiny 2 Error Codes
Destiny 2’s error codes use animal and food names. Here are the ones players hit most and what to do about each.
| Error | What it means | What to do |
|---|---|---|
| weasel | An all-encompassing general network error. | Power cycle your console or router, use a wired connection, and check server status. |
| centipede | You lost connection to your network, or your NAT is too strict. | Restart your network and open your NAT or enable UPnP. |
| baboon | You were removed from the game world by a connection drop. | Switch to wired and restart; avoid multi-platform login with Cross Save. |
| anteater | The connection to the servers dropped mid-activity. | Check your internet, use Ethernet, and restart your router. |
| chicken | No active internet connection was detected. | Check your router and ISP, then restart your network gear. |
| chickpea | A fireteam member disabled crossplay during an activity. | Have them re-enable crossplay in the settings menu. |
| broccoli | Your device failed to detect the GPU. | Update or reinstall your graphics drivers and restart the PC. |
| bee / beaver | A peer-connection or bandwidth problem between players. | Close bandwidth-heavy apps, open your NAT, and use a wired connection. |
| endive | The Destiny 2 servers are down for maintenance. | Wait for maintenance to finish and check @BungieHelp. |
| honeydew | Bungie manually locked the activity you tried to start. | Wait, the activity was disabled for an issue or an update. |
How to Prevent Destiny 2 Problems in the Future
Keep Destiny 2, your GPU drivers, and your OS updated, and verify files after big patches. Play on a wired connection with an open NAT type, and avoid heavy downloads on your network during raids and Trials. Check @BungieHelp before a session, especially around the Tuesday reset. On public or restricted Wi-Fi, connecting through Planet VPN keeps your route stable and your data private.
Conclusion
Work from the outside in. Check whether Destiny 2 is down, then your network and NAT, then the game files and drivers, then your account. Most issues clear within a few steps. If everything on your side is fine but Destiny still won’t connect, the block is likely regional or ISP-level, and that’s exactly where a VPN helps.
Frequently Asked Questions (FAQs)
-
1. Why is Destiny 2 not working today?
It’s usually a Bungie outage or maintenance, or a local network or NAT issue. Check help.bungie.net and @BungieHelp first. If servers are fine, power cycle your router and console, switch to a wired connection, and open your NAT type.
-
2. Is Destiny 2 down right now?
Check help.bungie.net and @BungieHelp for maintenance notices, glance at Downdetector, and check your PlayStation or Xbox status too. An endive error means the servers are down for maintenance. If everyone is affected, wait it out.
-
3. What does the weasel error mean in Destiny 2?
Weasel is Bungie’s all-encompassing general network error. Power cycle your console or router, switch to a wired connection, and open your NAT. Note that logging into two platforms at once with Cross Save enabled also triggers weasel, and in rare cases it can signal an account ban.
-
4. Can a VPN fix Destiny 2?
A VPN helps when your ISP throttles gaming traffic, when your Wi-Fi blocks the game, or when a poor route adds packet loss, and it hides your IP from DDoS. It can’t fix a Bungie outage, an endive maintenance error, a ban, a strict NAT your router controls, or a driver crash.
-
5. How do I fix a strict NAT type in Destiny 2?
A strict NAT causes centipede and matchmaking problems. Enable UPnP in your router or manually forward Destiny 2’s ports to set your NAT to Open or Type 1. A wired connection also helps, though some ISPs limit how open your NAT can be.
-
6. Why does Destiny 2 keep disconnecting me?
Repeated weasel, centipede, or baboon disconnects usually come from packet loss, a strict NAT, or bandwidth being eaten by other apps. Power cycle your gear, switch to Ethernet, open your NAT, and close background downloads. If it’s everyone, check @BungieHelp.
-
7. Why won’t Destiny 2 launch on PC?
If Destiny won’t launch or shows a broccoli error, your GPU usually wasn’t detected. Update or cleanly reinstall your graphics drivers, verify the game files, close overlays, and run the launcher as administrator. Reinstall only as a last resort.