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 reason an ultimate goes on cooldown without happening. The input packet never arrived, the server never cast it, and your client had already played the animation. This is the metric to watch for wasted ultimates.
Jitter (ability timing)
Dive heroes live and die on a few hundred milliseconds of timing. Jitter above the 16.7 ms tick interval makes enemy positions arrive out of step, so your dive lands where the target was, not where it is.
Ping (latency)
Under 40 ms is comfortable. Above 80 ms, reacting to a telegraphed ultimate stops working: the window you are reacting to closed on the server before your screen showed it.
What you see in game, and which number on this page explains it.
Marvel Rivals launched on 60-tick servers, and the creative director confirmed the figure before release - one of the few numbers NetEase has stated publicly. It is worth correcting a widespread error here, including one this site made: the game does not run at 64 ticks. That figure gets copied over from Counter-Strike and then repeated. We measured Marvel Rivals at 64Hz until this page was written, and the traffic pattern this test sends has been corrected to 60.
Sixty ticks means the server reconciles a fight every 16.7 milliseconds, which is quick enough that your own connection, rather than the server rate, is usually the limiting factor. That shifts where the useful diagnosis is: not "are the servers good enough", but "does my line keep up with them".
Hero shooters have a specific vulnerability that tracking shooters do not. Abilities are discrete, expensive events. A lost packet in an aim-based game costs a few frames of tracking accuracy; a lost packet carrying an ultimate cast costs the entire ultimate. Your client plays the animation locally because it predicts optimistically, the server never receives the cast, and the cooldown you are looking at is that prediction being corrected. There is nothing to learn from and nothing to play around - which is why loss is the number to watch on this page.
Jitter is the second-order version of the same problem. If your packets vary by more than the tick interval, dive timing becomes unreliable in a way that feels like inconsistent aim, because the target's position is arriving out of step with the ticks it belongs to.
If the chart above shows packet loss or high jitter, work through
these in order.
What tick rate does Marvel Rivals use?
60 ticks per second on the live servers, confirmed by the creative director at launch. Note that this is not 64 - a figure often copied over from Counter-Strike.
Why does my ultimate go on cooldown without firing?
The input packet was lost. Your client played the animation locally, the server never received the cast, and the cooldown you see is your client's optimistic prediction being corrected.
Is 60 ticks enough for a competitive hero shooter?
It is one reconciliation every 16.7 ms, which is enough that your own jitter usually dominates. If your jitter is above that interval, the server's extra precision cannot reach you.
Does high ping cause missed hits in Marvel Rivals?
It shifts what you see relative to the server's truth, so close-range hits get less reliable. Packet loss causes outright misses, which is the more visible failure.