Every online shooter has launch problems. Few have launch problems that become a defining, years-long punchline the way Overwatch’s did. When Blizzard’s hero shooter released in 2016, its servers ran at 20.8Hz — a number so low it became one of the most publicly criticized technical decisions of that entire console generation, discussed and dissected by players who had never heard the term “tick rate” before Overwatch taught it to them.
How Low Is 20.8Hz, Really?
To put that number in context against games we’ve already covered: Valorant runs at 128Hz. CS2 runs at 64Hz. Even Apex Legends, itself criticized for a low 20Hz tick rate years later, edges out Overwatch’s original number. A server updating barely 20 times a second in a shooter built around split-second peeker duels and precise hitscan aim was never going to feel clean, and it didn’t. Community frustration built for years, loud and specific enough that Blizzard’s own director eventually addressed the criticism directly rather than letting it fade on its own.
The Fix Nobody Expected From a Live Service
What makes this story genuinely worth telling isn’t just how bad the launch number was — it’s that Blizzard actually fixed it, and fixed it substantially. Rather than quietly patching in a marginal improvement, Blizzard rolled out a real bandwidth and netcode overhaul that pushed servers to roughly 63-64Hz, verifiable by any player directly in-game through the netgraph (Ctrl+Shift+N), which displays live packets-per-second alongside ping. That’s not a minor bump — it’s more than tripling the original tick rate, landing Overwatch roughly in line with CS:GO’s tick rate at the time, and Overwatch 2 has carried that upgrade forward rather than regressing.
Why This Story Still Matters Years Later
A meaningful number of players still carry the “Overwatch has bad servers” assumption forward from 2016, even though the actual infrastructure has been fundamentally different for years. That’s a useful lesson beyond this one game: a studio’s technical reputation, once earned, tends to outlive the specific problem that created it. If you’re evaluating a game’s netcode today, it’s worth checking what’s actually true right now rather than relying on a reputation that might be describing a version of the game that no longer exists. Overwatch’s netcode also uses predictive, shooter-favored hit registration similar to most modern competitive shooters, meaning a lower and more stable ping still gives you a real, measurable edge in close-range duels — the upgrade improved the floor, but your own connection still determines how close to that ceiling you actually play.
Check your own live ping to Overwatch 2’s regional servers with our Overwatch 2 ping test, and see how it compares to other tactical shooters like Valorant or CS2.
Related Guides
- Gamer Hub — All Game Ping Tests
- Overwatch 2 Ping Test
- Valorant Ping Test
- CS2 Ping Test
- What Is a Good Ping for Gaming?
Frequently Asked Questions
Is Overwatch 2’s tick rate still as bad as the original Overwatch?
No — that’s an outdated assumption a lot of players still carry. The original Overwatch launched at a criticized 20.8Hz, but Blizzard rolled out a major netcode overhaul years ago that brought servers to roughly 63-64Hz, and Overwatch 2 has continued running on that upgraded infrastructure.
How can I check my own tick rate and ping in Overwatch 2?
Press Ctrl+Shift+N in-game to open the netgraph, which shows live packets-per-second alongside your ping and connection stats in real time during any match.