Bungie names this code but does not publish the wording it prints on screen, so we quote only the code itself: CENTIPEDE. Any site showing you an exact message for it has written one.
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
Bungie has every core Destiny 2 service switched on
Bungie's baseline description: “CENTIPEDE is a general networking error code. This can be caused by a loss of connection to our servers.”
The more useful part is the admission that follows: “Bungie has seen users hitting these errors in geographic clusters in different places at different times. For example, we recently detected 25% packet loss from the UK… These Internet conditions usually pass quickly.”
That is a company saying out loud that some instances of this code are nothing to do with the player and nothing to do with Bungie either — they are the internet in between.
If people in your country are reporting it at the same time and it clears within the hour, that is a transit or ISP cluster and waiting is correct. If it is only you and it persists across reboots, it is your network or your NAT.
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. WEASEL is documented as having split off from CENTIPEDE, so the two are often searched together.
Bungie's baseline description: “CENTIPEDE is a general networking error code. This can be caused by a loss of connection to our servers.”
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
Start with: Use a wired connection. First, as with every networking code in this set.