Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Packet loss (the one that actually costs ships)
There is no prediction layer to smooth over a lost packet. Your module activation, your target lock, your warp command - if the packet carrying it does not arrive, the server resolves the tick without it and you find out a second later that nothing happened. In a fight where a hardener cycle decides whether you survive an alpha strike, that is the whole engagement.
Ping (matters far less than you would expect)
With a one second tick, the difference between 40 ms and 200 ms is the difference between using 4% and 20% of the window you have. Both fit. This is why EVE genuinely does support one worldwide server: a player in Australia and a player in Germany are resolving against the same tick, and neither of them is losing a tick to distance alone.
Jitter (the tick-boundary problem)
Jitter only hurts here when it pushes a command across a tick boundary. A command that would have made this tick lands in the next one instead, and the effect is identical to having clicked a full second later. If your ping line is spiky rather than high, that is what is happening to your commands.
What you see in game, and which number on this page explains it.
EVE's server resolves the state of the universe once per second. Every module activation, every target lock, every warp command is collected during that second and applied at the boundary. There is no client-side prediction to hide the wait, which is why the game feels deliberate even on a perfect connection - you are genuinely waiting for a server decision rather than watching a guess that gets corrected.
That design is what makes a single worldwide shard possible. In a 128 Hz shooter, a tick is under eight milliseconds and a transatlantic route eats several ticks of it, so the game has to be split into regional servers. Here a tick is a thousand milliseconds and the whole planet fits inside one. The trade is that when something does go wrong, it goes wrong at the granularity of a whole second.
This inverts the usual advice about what to measure. In most games, latency and loss both degrade the experience gradually. In EVE, latency is absorbed almost entirely by the tick, and loss is not absorbed at all: a command that does not arrive is not applied late, it is simply not applied, and the next thing you can do about it is a second later. A connection with 200 ms of ping and no loss is genuinely better here than one with 30 ms and occasional drops.
Time dilation is worth understanding because it is frequently mistaken for a personal connection problem. When a system's node cannot process everything queued for a tick, CCP slows the clock rather than discarding commands - the simulation can run down to a small fraction of real time, and the UI shows the percentage. This is the server protecting fairness under load. If you can see a TiDi figure, your own line is not the story; if you cannot, and things are still going missing, this chart is where to look.
If the chart above shows packet loss or high jitter, work through
these in order.
Does ping matter in EVE Online?
Much less than in almost any other online game. The server resolves once per second, so even 250 ms of round trip fits comfortably inside a tick. Packet loss is the metric that decides fights, because a lost command is not late - it never happened.
What is time dilation and can I fix it?
Time dilation is CCP deliberately slowing the simulation when a system's node is overloaded, so that thousands of queued commands are processed slowly instead of being dropped. It is server-side and affects everyone in the system equally. Nothing on your connection changes it.
Why do I keep getting disconnected in big fights?
Two different causes look identical from the client. A node under extreme load can end sessions, and so can sustained packet loss on your own line. Run this test during a quiet period: if it is clean, the fights are the server; if it is not, it is your connection and you can act on it.
Is a single worldwide server the reason EVE feels slow?
No - that is the tick, not the geography. One shard is possible precisely because a one second tick absorbs intercontinental latency. The pace of the game is a design choice, and it is the same choice that lets everyone play in the same universe.