Detailed analysis
LC-202 in Overwatch 2 means the game can't reach Blizzard's login servers. You're stuck at the title screen and nothing is loading. The fastest fix: check if Blizzard's servers are actually down first (downdetector.com), then restart Battle.net from the system tray and flush your DNS. That clears it most of the time.
What's actually happening
When you launch Overwatch 2, the game client needs to authenticate with Blizzard's login servers before you can do anything. LC-202 fires when that initial handshake fails. Your game is sending a connection request and getting nothing back — either because Blizzard's servers aren't responding, your network can't reach them, or something on your PC is blocking the traffic.
The tricky part about LC-202 is that your internet can be working perfectly fine for everything else. You can browse Reddit, watch YouTube, and run speed tests showing great numbers, but OW2 still shows LC-202. That's because Blizzard uses specific ports and endpoints that can be blocked or misrouted independently of your general internet connection.
The most common causes (in order of likelihood)
Blizzard server outage or maintenance — This is the cause more often than people expect. Blizzard's servers have regular maintenance windows (usually Tuesdays) and occasional unplanned outages. When millions of players try to connect during a new season launch or a major patch, the login servers can buckle. If it's affecting everyone, there's nothing to fix on your end.
Stale DNS cache — Your computer caches the IP addresses of servers it connects to. If Blizzard changes their server IPs (which they do during maintenance) and your DNS cache still has the old addresses, OW2 tries to connect to servers that no longer exist. Flushing DNS forces your computer to look up fresh addresses.
ISP routing problems — Some internet providers have bad routing tables to Blizzard's server infrastructure. Your data takes a weird path through the internet, hits a congested node, and the connection times out. This is more common with smaller regional ISPs and during peak evening hours.
Firewall or security software blocking OW2 — Windows Firewall, third-party antivirus suites, and especially corporate or school network firewalls can block the specific ports OW2 needs. Blizzard uses TCP ports 80, 443, and 1119 for Battle.net, plus additional ports for the game itself.
Battle.net client issues — The Battle.net launcher itself can get into a bad state where its authentication tokens expire or its network stack gets stuck. A full restart (not just closing the window) resets everything.
How to fix it
Before touching anything on your PC, check Blizzard's server status. Go to downdetector.com/status/overwatch-2 and look for a spike in recent reports. Also check @BlizzardCS on Twitter/X for maintenance announcements. If thousands of people are reporting issues at the same time, the problem is on Blizzard's end and you just need to wait it out. No amount of troubleshooting on your side will fix a server outage.
If servers look fine, restart Battle.net properly. Don't just close the window — that minimizes it to the system tray. Right-click the Battle.net icon in your system tray (bottom-right of your taskbar) and click Exit. Wait 10 seconds, then relaunch Battle.net. This forces a fresh authentication cycle.
Flush your DNS cache. Open Command Prompt as Administrator (search 'cmd' in Start, right-click, Run as administrator). Run these commands one at a time: ipconfig /flushdns, then ipconfig /release, then ipconfig /renew. This clears out any stale server addresses and gets fresh ones from your DNS provider.
Switch to a faster DNS provider. Your ISP's default DNS servers are often slow and unreliable. Open Windows Settings > Network & Internet > Change adapter options. Right-click your active network connection and select Properties. Click on Internet Protocol Version 4 (TCP/IPv4), then Properties. Select "Use the following DNS server addresses" and enter 1.1.1.1 as Preferred and 1.0.0.1 as Alternate (Cloudflare DNS). Click OK on everything. Alternatively, use Google DNS:
8.8.8.8 and 8.8.4.4. Cloudflare tends to be slightly faster for gaming.
Check your firewall settings. Open Windows Security > Firewall & network protection > Allow an app through firewall. Make sure Overwatch.exe and Battle.net.exe are both allowed on Private and Public networks. If they're not in the list, click "Allow another app" and browse to their locations. Overwatch is typically in C:\Program Files (x86)\Overwatch\ and Battle.net in C:\Program Files (x86)\Battle.net\.
Restart your router and modem. Unplug both from power, wait 30 seconds, plug the modem back in first, wait for it to fully connect (all lights stable), then plug in the router. This clears your router's DNS cache and refreshes your connection to your ISP. It also fixes any NAT table issues that might be blocking Blizzard's traffic.
If you're on a school, dorm, or corporate network, the network administrator is likely blocking game traffic. The only workaround is using a phone hotspot to connect instead, which bypasses their network entirely. If LC-202 disappears on a hotspot, confirm the network is the issue and talk to IT (or just plan to use cellular data for gaming).
As a last resort, try a VPN. Some ISPs have genuinely bad routing to Blizzard's servers, especially during peak hours. A VPN reroutes your traffic through a different path. Use a gaming-optimized VPN like ExitLag or Mudfish for minimum added latency. Connect to a server geographically close to your nearest Blizzard data center.
Is this a hardware or software problem?
LC-202 is a network problem, not a hardware or software issue with your PC. Your GPU, CPU, and RAM are completely irrelevant here. The question is whether the problem is on Blizzard's servers, your network configuration, or somewhere between you and Blizzard (your ISP's routing). If restarting Battle.net and flushing DNS fixes it, it was a stale connection. If you need a VPN to connect, it's an ISP routing issue. If nothing works and everyone on downdetector is complaining, it's Blizzard. If you're not sure, Crashless can check your drivers, temps, VRAM, and 400+ known patterns automatically — just use the chat above.
Games commonly affected
LC-202 is specific to Overwatch 2, but similar login server connection failures happen across all Blizzard titles. World of Warcraft shows BLZ51903006 or BLZBNTBGS000003F8, Diablo IV shows various connection errors, and Hearthstone just spins on the title screen. The DNS and network fixes in this guide work across all Battle.net games.
Frequently asked questions
Q: LC-202 only happens at certain times of day. Is that normal?
A: Yes, this is classic peak-hour ISP congestion. Your ISP's routing to Blizzard degrades during busy periods (typically 6-11 PM). Switching DNS to Cloudflare (1.1.1.1) often helps. If it doesn't, a gaming VPN during peak hours is the most reliable fix.
Q: I can play other online games fine. Why does only Overwatch 2 fail?
A: Different games connect to different server infrastructure through different network paths. OW2's login servers are separate from, say, Riot's or Steam's. Your ISP might have perfect routing to Valve but terrible routing to Blizzard. The VPN trick confirms this — if OW2 works through a VPN, your ISP's direct route to Blizzard is the problem.
Q: Do I need to port forward for Overwatch 2?
A: Usually not. Blizzard's recommended ports are TCP 80, 443, 1119 and UDP 3478-3479, 5060, 5062, 6250, 12000-64000. Most routers handle these through UPnP automatically. Port forwarding helps more with in-game disconnects (other error codes) than with LC-202 login failures. But if your router has UPnP disabled, enabling it is worth trying.