Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Packet loss (the disconnect metric)
Sustained loss is what turns into a Delta or Mike error. The client and server fall out of agreement about your state, the server cannot reconcile it, and the session ends. If you are seeing red lines here for more than a moment, the error codes are a symptom rather than a bug.
Jitter (bullet sponge syndrome)
The complaint that enemies absorb a whole magazine is usually jitter rather than balance. Your client shows hits immediately; the server confirms them when your packets arrive. When they arrive in clumps, the damage lands in clumps too, and an enemy appears to take nothing and then die all at once.
Ping (and the Dark Zone)
Under 60 ms is comfortable for PvE. The Dark Zone is where ping starts deciding fights, because you are now trading against other players under the same server validation - and there, being the one whose packets arrive later is exactly as costly as it sounds.
What you see in game, and which number on this page explains it.
The Division 2 validates everything server-side, including when you play alone. Damage, loot rolls, enemy health and your own position are all decided by Ubisoft's servers rather than by your client, and the client's job is to display a prediction of that decision. This is a deliberate choice driven by the loot economy: a game where gear is the whole progression cannot afford to let the client decide what dropped.
The cost of that choice is that there is no graceful degradation. In a game where the client has authority over your own character, a rough connection produces a rough experience and play continues. Here, when your client's prediction and the server's authoritative state drift too far apart, there is nothing sensible left to display - and the game does the only correct thing, which is to end the session rather than show you a world that is not real.
That is what the error codes are. They are not arbitrary failures; they are the game telling you which link in a specific chain gave way. DELTA codes point outward at the connection between you and the servers, MIKE codes point at the backend, BRAVO at matchmaking and session handling. Read together with a measurement of your own line, they become genuinely diagnostic: the same code means very different things depending on whether your connection was clean at that moment.
The bullet-sponge complaint comes from the same root. Your client draws the hit markers as soon as you fire because it is predicting, but the health bar only moves when the server confirms. A connection delivering packets unevenly produces exactly the pattern players describe - nothing, nothing, nothing, then an enemy dying instantly - and it is indistinguishable from enemy scaling unless you measure.
If the chart above shows packet loss or high jitter, work through
these in order.
What causes Delta errors in The Division 2?
DELTA codes generally indicate a connection problem between your machine and the game servers. Run this test for a few minutes: sustained packet loss here is the most common cause, and it is one you can act on.
Why do enemies take a full magazine before dying?
Because the server, not your client, decides when damage lands. If your hit packets arrive in clumps after a gap, the damage applies in clumps too. Look at jitter here rather than assuming it is enemy scaling.
Can I play The Division 2 offline?
No. The game is always online and server-authoritative even in solo play, because the loot economy depends on server-side validation. A connection problem is therefore a gameplay problem, not just a multiplayer one.
Does a VPN fix Division 2 disconnects?
Usually not. A VPN adds a hop and cannot repair packets your own line dropped. It only helps in the uncommon case where your ISP routes badly to Ubisoft's servers, which this test will not tell you on its own.