Competitive FPS · Blizzard

Overwatch 2 Ping Test

A good ping for Overwatch 2 (Competitive FPS) is under 30 ms — ideally below 15 ms. Around 50 ms is the playable ceiling, and past roughly 80 ms it's effectively unplayable. FRAGRATE measures your real ping, jitter, packet loss and bufferbloat to the regions Overwatch 2 runs in and returns a per-game Playable / Risky / No-go verdict.

Good ping, jitter & packet loss for Overwatch 2

MetricOptimalGoodPlayable maxNo-go
Ping15 ms30 ms50 ms> 80 ms
Jitter2 ms5 ms10 ms> 20 ms
Packet loss0%0.1%0.5%> 2%

High-tick hit-reg is unforgiving; jitter matters as much as raw ping.

Overwatch 2 regions FRAGRATE checks

  • NA East · Virginia
  • NA Central · Ohio / Chicago
  • NA West · Oregon
  • EU West · London
  • EU Central · Frankfurt
  • Asia SE · Singapore
  • Korea · Seoul
  • Asia East · Tokyo
  • Oceania · Sydney
  • SA East · São Paulo

How FRAGRATE measures this

FRAGRATE measures ping and jitter as a TCP-handshake to a public endpoint in each game region, packet loss via UDP/WebRTC, and bufferbloat as the latency added while your line is saturated. Run it locally for true per-region game-server ping, or use the hosted browser test for ping, loss and bufferbloat.

FAQ

What is a good ping for Overwatch 2?
Aim for under 30 ms; under 15 ms is optimal for Overwatch 2. Up to 50 ms is the playable ceiling, and above about 80 ms Overwatch 2 feels laggy.
How much packet loss can Overwatch 2 tolerate?
Keep packet loss under 0.1%. Between 0.1% and 0.5% is borderline; above 2% Overwatch 2 is effectively unplayable.
Does jitter matter for Overwatch 2?
Yes — keep jitter under 5 ms for Overwatch 2 (Competitive FPS). Above 20 ms you get inconsistent hit registration and rubber-banding even when average ping looks fine.
How much internet speed does Overwatch 2 need?
Surprisingly little — about 10–25 Mbps down and 3–10 Mbps up is plenty. Latency, jitter and packet loss decide playability far more than raw speed.

More for Overwatch 2

Run the live Overwatch 2 test →