Why do I get LC-202 only on Overwatch 2 while other games work fine?

Overwatch 2's netcode is unusually sensitive to packet loss and jitter because it syncs hero positions and abilities in real time. A connection that streams video fine can still drop Overwatch 2 sessions. Other games with looser timing may tolerate the same network without disconnecting you.

🔧 Overwatch 2 Error Fix · 8 Proven Fixes

How to Fix Overwatch 2 Error LC-202: Disconnected From Game Server

By GameAddaUpdated October 19, 20267 min read

You queue up, pick your hero, the match starts — and seconds later you're staring at the login screen: Disconnected from the game server. (LC-202). You can log back in, but the error comes right back, and ranked is starting to feel like a gamble. If that sounds familiar, this guide is for you.

In plain English, LC-202 means your game client lost its connection to Blizzard's Overwatch 2 servers. It is not an account problem, not a ban, and not a graphics issue — it's a networking problem. The tricky part is that the problem can live in two places: Blizzard's servers or your own network. This guide walks you through both, starting with the checks that take seconds and ending with the deep fixes. Work from the top down.

What does Error LC-202 actually mean?

Overwatch 2 keeps a constant, real-time conversation between your PC or console and Blizzard's game servers — hero positions, ability cooldowns, hit registration, all synced many times per second. LC-202 fires when that conversation breaks down: either your client can't reach the server at all, or the server stops hearing back from your client and drops your session. Blizzard uses LC-prefixed codes for all of these client-connection failures, and LC-202 is one of the most common.

The error tells you that the connection dropped, but not where. A broken connection can start at Blizzard's data center (server outage, overloaded region after a patch), your ISP (routing problems, congestion), your home network (failing router, Wi-Fi interference), or your device (firewall blocking the game, corrupted files). The fixes below eliminate these one by one, cheapest first.

What causes LC-202?

Every cause below is a break somewhere along the path between you and Blizzard:

Blizzard server outages or maintenance — the single most common cause during patch days and big events. If the servers are down, everyone in your region disconnects.
ISP routing problems — your internet provider routes your traffic through a broken or congested path to Blizzard's servers, even though your general browsing works fine.
Unstable home network — Wi-Fi interference, an overheating router, or a modem that needs a reset can cause the packet loss that triggers LC-202.
Firewall or antivirus blocking the game — security software sometimes flags Overwatch.exe or Battle.net traffic and silently kills the connection mid-match.
Corrupted game files — damaged network or patch files can break the client-server handshake, making every login attempt fail at the same point.
Bad DNS responses — your ISP's DNS may point your client at a dead or faraway server endpoint, so the connection never completes.
Bandwidth congestion at home — 4K streams, cloud backups, and big downloads competing for upload bandwidth starve the game's real-time traffic.
Wrong region selected — connecting to a faraway region (accidentally or from travel) raises latency so high that the server drops your session.

Check this before anything else: LC-202 spikes across the whole community whenever Blizzard's servers go down. Visit Blizzard's service status page and check a community outage tracker for Overwatch 2. If there's an active outage or scheduled maintenance, stop here — no router reset or reinstall will help, and the error clears on its own when the servers recover. Only continue if their servers are healthy.

1Confirm Blizzard's servers are actually healthy

Open the Battle.net launcher and look for service alerts at the top, then check Blizzard's official status page for Overwatch 2. Patch days, new seasons, and big esports events routinely overload the servers and produce mass LC-202 waves — forums and social media will light up within minutes when this happens. Also glance at an outage tracker to see whether the reports are concentrated in your region. If the servers are struggling, the correct fix is patience: play quick play later, and definitely stay out of ranked until the status page is green again. This check saves you from an hour of pointless network troubleshooting.

2Power-cycle your router and modem

Oldest trick in the book, and it still fixes more LC-202 cases than any other step. Unplug both your modem and router from power for at least 60 seconds — not 10, a full minute, so the capacitors drain and the hardware truly resets. Plug the modem back in first, wait until all its lights are stable (this can take 2–3 minutes), then plug in the router and wait for its Wi-Fi light. When everything is back, launch Overwatch 2. This clears stale NAT entries, renews your DHCP lease, and forces a fresh route to your ISP — exactly the kind of reset a flaky connection needs.

3Switch to a wired connection

If you play on Wi-Fi, LC-202's packet-loss sensitivity makes wireless the prime suspect. Temporarily run an Ethernet cable from your PC or console directly to the router or modem and try logging in. If the error disappears on wired, your Wi-Fi was the problem — interference from neighbors' networks, distance from the router, or a dying Wi-Fi radio. For a permanent fix, consider moving the router closer, switching to the less crowded 5 GHz band, or investing in a powerline adapter. If you absolutely can't run a cable, at least move your console or PC as close to the router as possible and minimize walls between them.

4Flush your DNS and switch to a public DNS server

Your ISP's default DNS servers can go stale or return bad endpoints. On PC, open Command Prompt as administrator and run these three commands in order: ipconfig /flushdns, then ipconfig /release, then ipconfig /renew. Next, change your DNS servers to a fast public resolver: Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). On Windows this is under Settings → Network → your adapter → DNS settings; on consoles it's in the network setup screen. Restart the game and try again. This step alone resolves a surprising number of persistent LC-202 cases where everything else looks fine.

Skip the VPN trap: Forum advice often suggests using a VPN to fix LC-202, and it can work if your ISP's route is the problem — but a VPN adds latency, can trigger account security flags at Blizzard, and often just moves the bottleneck. Test a VPN for a few minutes to diagnose, but treat the DNS change above and your ISP call as the real long-term fix.

5Allow Overwatch 2 through your firewall and antivirus

Security software is a quiet cause of LC-202: it may let the game launch but kill its network traffic mid-session. Open Windows Security → Firewall & network protection → Allow an app through firewall and make sure both Overwatch.exe and the Battle.net client are allowed on private and public networks. If you use third-party antivirus (Norton, McAfee, Avast, and friends), add the same two programs to its exceptions list. For a quick test, temporarily disable real-time protection, launch Overwatch 2, and see if LC-202 clears — if it does, you've found your culprit. Remember to turn protection back on and keep the game on the exception list rather than leaving your PC unprotected.

6Scan and repair the game installation

Corrupted files can break the client-server handshake so that every connection attempt fails at the same point. In the Battle.net client, select Overwatch 2, click the gear icon next to the Play button, and choose Scan and Repair. Let it finish — it verifies every game file and re-downloads anything damaged. This takes a few minutes and fixes the file-corruption cause of LC-202 without a full reinstall. On consoles, the equivalent is checking the game data in system settings or reinstalling from the store (console players should also install any pending system software updates, since outdated firmware can break network handshakes too).

7Update network drivers and free up bandwidth

Outdated network adapter drivers cause subtle packet-loss patterns that Overwatch 2 punishes. On PC, open Device Manager → Network adapters, right-click your adapter, and check for driver updates — better yet, grab the latest driver from your motherboard or laptop manufacturer's site. Then, before launching the game, close everything that eats bandwidth: pause cloud backups (OneDrive, Google Drive), stop streaming services, kill big downloads, and close browser tabs. Overwatch 2 needs only a little bandwidth, but it needs it consistently — upstream congestion is the silent killer here. If someone in your house starts a 4K stream mid-match, that's often exactly when LC-202 strikes.

8Change your login region or contact Blizzard support

In the Battle.net client, above the Play button, you'll see your current region (Americas, Europe, Asia). Try switching to the nearest alternative and logging in — if your usual region's servers are having issues that the status page hasn't announced yet, the other region will work fine. If LC-202 follows you across regions and every fix above failed, it's time to contact Blizzard support: open a ticket with your platform (PC, PlayStation, Xbox, or Switch), your region, your ISP, and the exact time your disconnects happen. They can check server-side logs and routing data that you can't see, and they'll tell you if it's a known issue with a fix incoming.

Quick checklist to keep LC-202 away

Check the Blizzard status page before troubleshooting anything — most mass LC-202 waves are server-side.
Play on a wired Ethernet connection whenever possible; Wi-Fi is the most common home-side cause.
Keep Overwatch.exe and Battle.net on your firewall and antivirus exception lists permanently.
Restart your router monthly and keep its firmware up to date — stale routers cause slow rot, not sudden failures.
Don't queue ranked right after a patch or during known server issues — LC-202 disconnects in ranked cost you SR and can trigger leaver penalties.
Use a public DNS (Google 8.8.8.8 or Cloudflare 1.1.1.1) as your default rather than your ISP's.

Frequently asked questions

What does Overwatch 2 Error LC-202 mean in plain English?

It means your game client couldn't keep a stable connection to Blizzard's Overwatch 2 servers, so it disconnected you. In plain English: the phone line between your PC or console and Blizzard dropped, and the game booted you back to the login screen.

Is LC-202 caused by my internet or by Blizzard's servers?

It can be either, which is why Fix 1 is always to check Blizzard's server status first. If their servers are down, overloaded after a patch, or under maintenance, everyone in your region gets LC-202 and no setting on your end can fix it. If their servers are healthy, the cause is on your side — your network, firewall, or game files.

Can a VPN fix Overwatch 2 Error LC-202?

A VPN sometimes helps when your ISP's routing to Blizzard's servers is broken, because it changes the network path your traffic takes. But VPNs add latency and can trigger account security flags, so use one only as a temporary diagnostic test. The DNS switch in Fix 4 usually solves routing issues more cleanly.

Does LC-202 affect ranked matches and SR?

Yes — if you disconnect from a ranked match with LC-202, the game may count it as leaving and apply the usual leaver penalties, including SR loss and temporary suspensions. Fix the error in quick play or practice first before queueing ranked again.

Why do I get LC-202 only in Overwatch 2 while other games work fine?

Overwatch 2's netcode is unusually sensitive to packet loss and jitter because it syncs hero positions and abilities in real time, many times per second. A connection that streams video perfectly can still drop Overwatch 2 sessions, while games with looser timing tolerate the same network without disconnecting you.

Will reinstalling Overwatch 2 fix LC-202?

Reinstalling can help if the cause is corrupted game files, but it's a last resort. Try Scan and Repair in the Battle.net client first — it finds and replaces the same broken files in a few minutes without a full re-download. Reinstall only if the scan doesn't help.

For most players, LC-202 ends at Fix 1 or 2 — either Blizzard's servers were having a moment, or the router just needed its monthly nap. The error feels catastrophic because it boots you mid-match, but it's almost never a serious problem with your PC or console. Start with the server check, work down the list, and you'll be back on the payload in no time. And if you'd rather skip login screens, server queues, and patch-day drama entirely for a while, the free browser games here on GameAdda start with a single click. 🎮