Is Overwatch down?
Check the current FrameReady community service signal.
Open pageFrameReady news
Overwatch July 14 Update FPS Drops, Freezing and Memory Leak: What Players Are Reporting
Reports of sharp FPS drops, combat freezes, settings resets and apparent memory growth began appearing within hours of Overwatch's July 14, 2026 update. These are player reports, not confirmation that one widespread Blizzard defect is causing every symptom.
Bottom line
The reports are real, but the scope and cause are not established. One PC player described roughly 400 FPS falling to about 120 and sometimes 9 FPS, while another reported RAM growth and heavy disk activity. A PS4 player reported LC-202, and a second player described the same login situation on PC and PS5. Blizzard had not acknowledged a common July 14 performance defect when FrameReady checked, and there is no confirmed workaround.
Evidence status
player reported: FrameReady keeps news claims tied to sources so updates do not drift into guesses.
Issue state: Investigating. Last checked Jul 15, 2026, 7:20 AM.
Current status
This is the clearest status available at review time. A working server connection does not prove the game client is performing correctly.
| Check | Status |
|---|---|
| Player reports | Yes. New PC performance and memory reports appeared within hours of the July 14 update. |
| Blizzard acknowledgement | None found for one shared July 14 FPS or memory defect. |
| Server status | FrameReady showed no community outage spike at review time. |
| Confirmed workaround | None. FrameReady is not recommending unverified fixes. |
| Last checked | July 15, 2026 at 7:20 AM EAT (4:20 AM UTC). |
Sources: Blizzard patch notes, FrameReady Overwatch status.
What PC players reported
The most detailed report says performance changed immediately after the patch, including in Practice Range with low graphics settings. It is one configuration example, not a list of hardware known to be affected.
- One player reported a fall from about 400 FPS to about 120 FPS, with occasional drops to 9 FPS.
- The same report describes constant stutter, brief combat freezes and a freeze when a hit lands on an enemy.
- That player also said the update reset graphics settings.
- Example system only: Ryzen 5 5600, RTX 5060 8 GB, 32 GB DDR4, SSD and 1080p low settings.
- Another reply said similar stutter existed before July 14 on different hardware. That weakens any claim that every report started with this patch.
Sources: July 14 FPS, stutter and freeze report.
Why the memory leak wording needs care
A second player called the behavior a memory leak after seeing RAM allocation rise toward the system limit, heavy disk activity while idle, crashes, freezes and FPS loss. That is enough to document apparent memory growth, but not enough to establish a technical memory leak.
- Blizzard had not confirmed a memory leak in the checked patch archive or support indexes.
- Older Overwatch RAM complaints exist, so a high memory figure alone does not tie the cause to July 14.
- FrameReady will change the label only if Blizzard acknowledges the defect or reproducible technical evidence establishes it.
Sources: Player report describing memory growth.
LC-202 and post-update login reports
One PS4 player reported connection error LC-202 a few hours after installing the latest update. The post says license restoration, network checks, database rebuilding, reinstalling and changing connection type did not resolve it. A second player later described the same situation on PC and PS5, but did not explicitly repeat the LC-202 code.
- These two reports are not evidence of a platform-wide outage.
- FrameReady's Overwatch status page showed the service up with no report spike at review time.
- Server availability and client-side performance can diverge, so the two findings do not contradict each other.
Sources: PS4 LC-202 report, Overwatch server status.
What to do now
There is no confirmed fix to prescribe. Preserve useful evidence and avoid turning a forum suggestion into a cure.
- Record platform, game version, map, mode, FPS before and after the patch, RAM trend and whether settings were reset.
- Check the Blizzard patch notes and support forums for an acknowledgement before changing files or reinstalling again.
- Use the FrameReady status page to separate a service outage from a local or client performance problem.
- Do not assume an online workaround is safe or effective unless Blizzard documents it.
Related next steps
Sources
- official: Blizzard Overwatch patch notes. Official patch archive checked for a July 14 acknowledgement.
- inferred: July 14 FPS and freeze report. Player account of FPS loss, stutter, hit freezes and reset settings.
- inferred: Apparent memory growth report. Player account of rising RAM use and disk activity; not a confirmed memory leak.
- inferred: LC-202 and login reports. One PS4 LC-202 report and a second similar login report on PC and PS5.
- inferred: FrameReady Overwatch status. Community availability signal checked at publication time.