How to Fix Destiny 2 Error Code Centipede (Network Disconnected)
What Error Code Centipede means
Error code Centipede is one of Destiny 2's classic connection errors, and it always strikes at the worst moment: mid-strike, mid-raid, or right as you queue for Crucible, the game stutters and dumps you back to the title screen with a small CENTIPEDE error message. Nothing crashed — your console or PC is fine, the game is fine — the network connection between you and Bungie's servers simply dropped.
Bungie's official help page keeps it deliberately simple: Centipede is a general networking error code, caused by a loss of connection to their servers. Their guidance focuses on two things — switch from Wi-Fi to a wired connection if you can, and if your NAT is Strict or Type 3, get it into an Open or Type 1 state. Bungie has also noted that these errors sometimes hit in geographic clusters when Internet routing conditions deteriorate; during one investigation they observed 25 percent packet loss from the UK at exactly the time players there were getting these errors. That kind of problem usually passes within a few hours and is completely outside your control.
Your account and progress are safe whenever Centipede appears. Everything in Destiny 2 — your characters, gear, and seasonal progress — lives on Bungie's servers, so a dropped connection never deletes anything. The error is purely about getting a clean connection back: confirming the servers are actually up, ruling out your home network, and fixing the router settings that most commonly cause it. The steps below follow exactly that order, starting with the checks that save you from troubleshooting a problem on Bungie's end.
Common causes
- Bungie server maintenance or patch deployment: scheduled maintenance and major content drops disconnect players and trigger Centipede until the servers come back up.
- Steam's Tuesday afternoon downtime: Steam performs regular maintenance on Tuesday afternoons, Eastern Time, disconnecting all users everywhere — Centipede spikes during these windows.
- Strict or Type 3 NAT: a restrictive NAT on your router can block or degrade the traffic Destiny 2 exchanges with Bungie's servers.
- Unstable Wi-Fi or packet loss: wireless interference, ISP congestion, or a bad route between your ISP and Bungie drop the connection mid-session.
- VPN, firewall, or antivirus interference: VPNs and overly strict firewall rules can block Destiny 2's traffic, cutting the session short.
How to fix Error Code Centipede — step by step
Work through these fixes in order. Centipede is frequently a Bungie-side problem, which is why the list starts with the check that saves you from troubleshooting something you can't fix.
- Check Bungie's server status and Steam maintenance first. Before touching your setup, confirm the problem is not on the server side. Open Bungie's official help status page or the @BungieHelp account on X and look for maintenance notices or a known outage. Centipede frequently spikes during scheduled maintenance and patch deployments, and one of the most common triggers is Steam's regular Tuesday afternoon downtime, when Steam disconnects all users everywhere. If any maintenance is announced, the only fix is to wait until the servers are stable again — no amount of router troubleshooting will change it.
- Restart Destiny 2 and power-cycle your network hardware. Quit Destiny 2 completely, then power-cycle your network gear. Unplug your modem and router from power for at least 60 seconds, then plug them back in and wait until every status light is stable before launching the game again. On PlayStation or Xbox, power the console down fully and unplug the power cable for 30 seconds; on PC, shut the machine down completely rather than restarting. A fresh connection handshake clears stale session data and resolves many Centipede errors on its own.
- Switch to a wired connection and turn off your VPN. Bungie recommends playing on a wired Ethernet connection whenever possible, and Wi-Fi instability is one of the most common silent triggers for Centipede. If you play over Wi-Fi, run an Ethernet cable from your router to your PC or console, at least for a test session. Also disconnect any VPN before launching the game — VPNs can block or reroute the traffic Destiny 2 needs, and Bungie's own troubleshooting guide lists disabling VPNs as a key step. Try launching Destiny 2 with the VPN off and the firewall temporarily relaxed to see if the error clears.
- Open your NAT type on the router. A strict NAT type is a classic Centipede trigger: Bungie advises getting your NAT into an Open or Type 1 state, because a Type 3 or Strict NAT can interfere with your connection to Destiny 2's servers. Log in to your router's admin page and enable UPnP first, which lets the console or game open the ports it needs automatically. If UPnP does not help, enable manual port forwarding with Destiny 2's ports — on Xbox One, TCP 3074 and UDP 88, 500, 1200, 3074, 3544, 4500; on PC, UDP 3074 and 3097. Then check your console's network status to confirm the NAT type changed before relaunching the game.
- Change your DNS to a public provider. Switching to a public DNS service can improve connection stability when your ISP's default DNS is slow or flaky. On PlayStation, go to Settings, then Network, then Settings, then Set Up Internet Connection, select your network, and set DNS Settings to Manual. On Xbox, go to Settings, then General, then Network settings, then Advanced settings, then DNS settings, and choose Manual. Enter Google DNS as Primary 8.8.8.8 and Secondary 8.8.4.4, or Cloudflare DNS as Primary 1.1.1.1 and Secondary 1.0.0.1. Save the settings, test the connection, and launch Destiny 2 again.
- Test for packet loss and contact your ISP if it persists. If Centipede keeps returning after everything above, the problem may be packet loss on the route between your ISP and Bungie's servers — Bungie's own investigations have found geographic clusters of these errors during periods of heavy packet loss, and those Internet conditions usually pass on their own within a few hours. On PC, open Command Prompt as an administrator and run tracert to a known stable address like 8.8.8.8; if you see hops with latency above 200 ms or dropped requests, that points to your ISP or its upstream routes. Take a screenshot of the results and contact your ISP's support, or wait a few hours and try again if no route problem shows up.
Did this fix it? Quick checklist
- You can log in and stay connected through an activity without a Centipede error
- Bungie's status page and Steam show no active maintenance or outages
- Your console or PC is on a wired connection with an open or Type 2 NAT
- No VPN is running, and the firewall allows Destiny 2 through
If Centipede still keeps appearing, try logging in on a different platform to rule out a device-specific problem, and double-check that your router's UPnP setting actually stayed on — some routers disable it after a firmware update. As a last resort, note the time of day the errors happen: if they cluster on Tuesday afternoons, it is Steam maintenance and will pass; if they are random, your ISP's routing is the most likely culprit, and the tracert results above are the evidence to hand them.
Frequently asked questions
What does error code Centipede mean in Destiny 2?
According to Bungie's official help page, Centipede is a general networking error code caused by a loss of connection to Bungie's servers. It kicks you back to the title screen mid-activity and can be triggered by server maintenance, an unstable home network, a strict NAT type, or broader Internet routing problems between your ISP and Bungie's servers. It is a connection issue, not a sign your account or characters are damaged.
Is Centipede caused by Bungie's servers or my connection?
It can be either, which is why the first step is always to check the server status. Centipede appears during Bungie maintenance, patch deployments, and Steam's regular Tuesday afternoon downtime. But it also appears when your own connection is the problem — Wi-Fi packet loss, a strict NAT type, an interfering VPN or firewall, or packet loss on your ISP's routes to Bungie. If the status pages show no outages, the cause is on your side and the steps above should resolve it.
Why do I get Centipede every Tuesday afternoon?
Steam performs regular scheduled maintenance on Tuesday afternoons, Eastern Time, and during those windows Steam disconnects users everywhere — which causes Destiny 2 to lose its connection to Bungie's services. Centipede and other Destiny 2 networking errors spike during these periods. If the error reliably appears on Tuesday afternoons and clears a few hours later, it is almost certainly the Steam maintenance window, not your network. Check the Steam status page before troubleshooting your own hardware.
Can a strict NAT type cause Centipede?
Yes. Bungie's own guidance for Centipede specifically calls out NAT type: if your NAT is Strict or Type 3, you should work to get it into an Open or Type 1 state. A restrictive NAT can block or degrade the traffic Destiny 2 exchanges with Bungie's servers, producing exactly this error. Enable UPnP on your router first, and if that does not change the NAT type, use manual port forwarding with the ports Destiny 2 needs.
How do I know if packet loss from my ISP is the cause?
Bungie's investigations have shown Centipede errors hitting in geographic clusters during periods of packet loss — for example, 25 percent packet loss from the UK coinciding with widespread errors there — and those conditions usually clear on their own within hours. On PC, run tracert 8.8.8.8 in an elevated Command Prompt and watch for hops with latency above 200 ms or dropped requests. If the trace looks clean and the error persists, the issue is more likely your home network or router settings; if hops time out, call your ISP with the results.