Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Red lines (packet loss)
Loss is the direct cause of the animal error codes. In a peer-based fireteam it hurts twice over, because a dropped packet can break the connection to a specific player rather than merely delaying a server update.
Jitter (stability)
Jitter is why enemies in a Crucible match blink between positions. With peer traffic, the quality of the worst link in the lobby shapes what everyone sees - your own stability is what you can control.
Ping (latency)
Under 60 ms is comfortable. Because part of the traffic is peer to peer, your effective latency depends on where the other players are, and a good result here is a necessary but not sufficient condition.
What you see in game, and which number on this page explains it.
Destiny 2's error codes are named after animals rather than components, and that naming hides something useful: most of them describe a failure to reach another player, not a failure to reach Bungie. The game uses a hybrid model in which Bungie's servers hold authority over your character and inventory while a large share of moment-to-moment gameplay traffic is exchanged directly between fireteam members.
That is why BEAVER and BABOON both boil down to the same thing: your machine could not establish or hold a connection to another player's machine. Packet loss on either side causes it, ISP congestion causes it, and so does a router that cannot map the ports several consoles behind it need at once - which is why enabling UPnP resolves a surprising share of these reports. WEASEL is the general catch-all, and it usually means the same underlying connectivity trouble without a more specific classification.
The practical method is to stop treating the codes as mysteries and start treating them as timestamps. Leave this chart running in a second window during a raid or a Trials card. If red lines appear at the moment you are thrown out, the code was telling you the truth and the fault is on your line. If the chart is clean, the failing link was on someone else's side, and no change you make locally will prevent it.
Peer connections are also less forgiving than server connections in general, because there is no infrastructure in the middle absorbing jitter. A wireless link that is merely mediocre against a dedicated server can be visibly unstable against another household's connection, which is the strongest argument for a cable in this particular game.
If the chart above shows packet loss or high jitter, work through
these in order.
What causes the BEAVER error in Destiny 2?
A failure to connect your machine to another player's over the internet. Packet loss, ISP congestion and routers without UPnP are the usual causes - it is a peer link failing, not Bungie's servers.
What does WEASEL mean?
It is Bungie's catch-all network error. It usually points at general connectivity trouble such as packet loss between you and the rest of the fireteam.
Does Destiny 2 use dedicated servers?
Only partly. It is a hybrid: Bungie's servers hold authority and inventory, while a large share of moment-to-moment gameplay traffic runs peer to peer between fireteam members.
Why do errors hit me and not my fireteam?
Because each peer link is separate. The worst connection in the lobby decides who gets dropped, and this test tells you whether that is yours.