Problem: Call of Duty “Packet Burst” (rubber-banding + stutter) making matches feel unplayable — with no single reliable fix
Published: 2026-01-12 12:00 (local time)
Quick Summary
- Many Call of Duty players report frequent “Packet Burst” indicators paired with hitching, rubber-banding, and sudden gunfight lag.
- It appears across multiple recent CoD titles/branches and can feel worse after certain updates or on certain networks.
- Research suggests a mix of server-side factors (you can’t fully fix) and client/network factors (you sometimes can mitigate).
- Workarounds that repeatedly help some players include changing texture streaming behavior, forcing shader rebuilds, and removing network instability (Wi‑Fi/mesh/bufferbloat).
- None of the fixes are universal; success varies by platform, ISP routing, and in-game settings.
What’s happening
Players describe “Packet Burst” as an on-screen warning/icon accompanied by micro-stutters, sudden latency spikes that don’t match the in-game ping readout, rubber-banding/teleporting, delayed hit registration, and periodic “waves” of lag. Reports show it can happen even on high-end PCs and even with wired Ethernet, which is why so many players consider it especially frustrating and hard to solve.
Who’s affected: Most complaints cluster around PC players (Steam/Battle.net/Xbox app/Game Pass PC), but console players also report similar symptoms. It’s commonly discussed in Black Ops 6/BO6 communities and also appears in Warzone/CoD HQ contexts. Some users claim it became dramatically worse after particular game updates or events, while others say it comes and goes regardless of patches.
When it started: “Packet Burst” has been discussed for years in CoD communities, but the problem remains actively reported in recent months, including threads describing it as “unplayable,” returning after updates, or changing suddenly day-to-day.
Likely causes (what research suggests)
- Server-side load / netcode / data center variance: Many users believe the primary cause is server-side (or routing to specific data centers). When that’s true, local tweaks may only reduce symptoms, not eliminate them.
- On-demand texture streaming interactions: Multiple guides and user reports connect stutter/burst symptoms to texture streaming settings and cache behavior (reducing streaming demand sometimes reduces in-match hitching).
- Shader compilation/cache problems (client-side hitching that feels like “network”): Some players report improvements after forcing shader re-preload or manually clearing shader caches, implying that what looks like network instability can be compounded by frame-time spikes.
- Home network instability (Wi‑Fi/mesh/extenders/bufferbloat): Users frequently report that switching from Wi‑Fi/mesh to wired, removing extenders, or upgrading network gear helps, suggesting jitter/queueing is a real contributor for many setups.
Solutions & Workarounds
1) Reduce On-Demand Texture Streaming pressure (often helps “burst + stutter” combos)
Who it helps: PC and console players in CoD titles with texture streaming options.
Steps:
- Open the game’s graphics/settings menu.
- Find On-Demand Texture Streaming and set it to Minimal (or the lowest available option).
- Set the texture streaming cache size to the lowest reasonable value for your platform.
- Restart the game after applying changes.
Risks / tradeoffs: Visual quality may drop (less detailed textures at distance), and you may see more texture pop-in.
Stop & contact support when: You still rubber-band every few seconds on wired internet and other online games are fine—collect evidence (dates/times, region, ISP, and a short clip) and submit to Activision support.
2) Force a full shader rebuild (in-game “Restart Shaders” + wait it out)
Who it helps: Primarily PC players; sometimes reduces hitching that masquerades as network “bursts.”
Steps:
- In graphics settings, use the option to Restart Shaders Pre-Loading (wording varies).
- Exit to desktop and relaunch the game.
- Do not queue into matches until shader compilation/preloading finishes.
Risks / tradeoffs: The first launch after rebuild can take several minutes; playing mid-compile can be worse than before.
Stop & contact support when: Shaders repeatedly “finish instantly” but performance remains erratic after multiple clean rebuild attempts—note your GPU driver version and submit a report.
3) Manually clear shader cache folders (advanced; works for some, not all)
Who it helps: PC players with persistent issues after patches or driver changes.
Steps:
- Close the game completely.
- Locate the game’s shader cache folder (commonly within the CoD install directory; some users reference a “shadercache” folder under a “cod” subfolder) and delete the contents (not necessarily the folder itself).
- Relaunch and allow shaders to recompile fully before matchmaking.
Risks / tradeoffs: Deleting the wrong files can cause re-downloads or longer rebuilds. Always ensure the game is closed before deleting caches.
Stop & contact support when: The issue worsens dramatically after cache deletion and persists across reboots—revert changes and contact support with your steps.
4) Try switching Crossplay OFF (a matchmaking tradeoff that can smooth some matches)
Who it helps: Players who don’t need cross-platform parties and suspect uneven lobbies/servers.
Steps:
- Open Settings > Account & Network (or similar).
- Set Crossplay to Off (and Crossplay Communication off if available).
- Restart matchmaking and compare multiple matches.
Risks / tradeoffs: Smaller player pool, longer queue times, and you can’t party with friends on other platforms.
Stop & contact support when: Disabling crossplay makes no difference and you can reproduce the issue reliably on specific maps/times.
5) Eliminate Wi‑Fi/mesh/extender variables (most “real-world” fix when it works)
Who it helps: Anyone playing over Wi‑Fi, mesh networks, powerline, or extenders.
Steps:
- Test a direct wired Ethernet connection to your main router (not a mesh node) for at least 5–10 matches.
- If you must use Wi‑Fi, temporarily remove extenders and connect to the primary router’s 5 GHz network.
- Reboot modem/router, then retest.
Risks / tradeoffs: Running Ethernet may be inconvenient; removing mesh/extenders can reduce coverage in the home.
Stop & contact support when: Wired-from-main-router still bursts while other competitive shooters remain stable—this suggests game/server/routing issues beyond your LAN.
6) Check for “bufferbloat” and reduce it (QoS/SQM can help jitter-sensitive games)
Who it helps: Households where uploads/downloads happen during play (streams, cloud backups), or where latency spikes occur under load.
Steps:
- Pause heavy downloads/streams on all devices and retest.
- If your router supports QoS/SQM (Smart Queue Management), enable it and set bandwidth limits slightly below your real max speeds.
- Retest in CoD and compare consistency (not just average ping).
Risks / tradeoffs: You may reduce peak throughput to gain stability (that’s the point).
Stop & contact support when: You cannot stabilize latency under load even with QoS/SQM—your ISP may have upstream congestion or routing problems.
Prevention (so it doesn’t come back)
- After major GPU driver updates or big CoD patches, proactively rebuild shaders before serious play sessions.
- Keep texture streaming conservative if your connection is inconsistent or capped.
- Avoid extenders/mesh hops for competitive play; prefer Ethernet to the main router when possible.
- Schedule large downloads/updates outside playtime; enable QoS/SQM to prevent jitter under load.
FAQ
Q: Is “Packet Burst” always my internet?
A: No. Many players report it on strong connections and high-end rigs; research suggests both server-side and client/network contributors.
Q: Why does it feel like lag when my ping looks fine?
A: Ping is an average; brief jitter spikes, routing hiccups, packet loss, or frame-time stutters can feel like “lag” without obvious ping changes.
Q: Why would shaders affect a network warning?
A: If your frame time spikes hard, the game can “feel” like networking instability; some players report the icon coinciding with stutters that improve after shader rebuilds.
Q: Should I lower graphics/VRAM targets?
A: Some users claim lowering VRAM targets reduces issues, but it can be a quality/performance compromise and isn’t universal. Try it only after safer steps (streaming/shaders/network).
Q: When should I stop troubleshooting and escalate?
A: If wired play from the main router still bursts, other games are stable, and the problem persists across multiple days—document it and contact Activision support.
Q: Does disabling Crossplay “fix” it?
A: It sometimes helps matchmaking consistency for some players, but it’s not guaranteed and can increase queue times.