"Hitreg is broken" is one of the most common complaints in competitive shooters, CS2 included. Sometimes that's a genuine server-side or engine issue during a specific patch. Very often, though, the actual cause is sitting on the network path between your PC and the game server — specifically jitter, which is a different problem from simple high ping and gets far less attention.
Why Ping Alone Doesn't Explain It
Ping tells you the average round-trip time to the server. It's a useful number, but it hides a critical detail: whether that time is consistent. A connection with 30ms ping that stays steady at 28-32ms every single packet behaves completely differently from a connection that averages 30ms but actually swings between 10ms and 90ms from one packet to the next — even though both might report a similar average ping in a basic test. That swing is jitter, and it's what actually determines how reliably the game server receives your input at a predictable, steady cadence.
How Jitter Breaks Hit Registration Specifically
Competitive shooters use server-side lag compensation: when you fire, the server rewinds its model of where the enemy was at the moment your client believes the shot happened, based on the timing of packets it's been receiving from you. This system works well when your packet timing is consistent and predictable. When jitter is high, the server's model of "when did this shot actually happen from the shooter's perspective" becomes less reliable, because the timing data it's working from is inconsistent. The practical result: shots that looked clearly on-target on your screen can fail to register, because the server's reconstruction of the moment doesn't line up cleanly with what you saw locally.
What Actually Causes High Jitter
- WiFi instead of Ethernet — WiFi's inherent retransmission and contention behavior introduces far more packet-timing variance than a wired connection, even when average ping looks fine.
- Bufferbloat — background load elsewhere on your network (someone streaming, a download running) can create the exact queuing-delay variance that shows up as jitter, as covered in this related breakdown.
- Overloaded home router CPU — an older or budget router juggling many connected devices and background processes can introduce its own small, inconsistent delays before packets even leave your home network.
- ISP route instability — a route that isn't consistent hop-to-hop can introduce jitter that's entirely outside your home network's control, which shows up identically to a home-network cause unless you specifically test for it.
How to Check If Jitter Is Actually Your Problem
A normal one-off ping test won't show this — you need a test that specifically reports jitter as its own number, not just an average latency figure. DCSpeedTest reports jitter alongside ping on every test for exactly this reason. As a rough guide, jitter under 5ms is generally not something you'll notice in competitive play; jitter climbing into the 20-30ms range and higher is where hit-registration and movement feel start becoming genuinely inconsistent.
What Actually Fixes It
- Switch to a wired Ethernet connection if you're currently on WiFi — this alone resolves the largest single source of jitter for most players.
- Enable SQM/CAKE on your router to control bufferbloat-driven jitter spikes during shared household usage.
- Test at different times of day — if jitter is consistently worse during peak evening hours regardless of what's running on your own network, that points toward ISP-side congestion rather than anything fixable at home.
Frequently Asked Questions
Is high jitter always the cause when hitreg feels off?
No — server-side issues during specific game updates do happen and are a separate, real cause. Checking your own jitter first is worth doing because it's both common and something you can actually verify and often fix yourself.
Does a gaming-branded router reduce jitter more than a regular one?
Only if it actually implements real queue management (SQM/CAKE) rather than just marketing terminology — the underlying mechanism matters more than the "gaming" label on the box.
Can a VPN reduce jitter?
Rarely, and often the opposite — adding a VPN hop typically adds its own latency and potential jitter on top of your existing route, unless the specific VPN route happens to be more stable than your ISP's default path, which isn't something to assume without testing.
Why This Is Easy to Misdiagnose
Because jitter's symptoms look similar to server-side lag compensation issues, it's easy for players to blame "the game" when the actual bottleneck is sitting on their own network path. Running an actual jitter measurement, rather than relying on how the game feels, is the only way to tell the two apart with any confidence — a subjective sense of "lag" doesn't distinguish between a client-side network problem and a genuine server-side issue.
It's also worth checking whether the issue is consistent across different servers and regions, or specific to one. Jitter tied to a specific server region often points toward an ISP routing issue on that particular path, while jitter that shows up everywhere regardless of server points more strongly toward something local — your own WiFi, router, or home network congestion.