Overwatch 2 Error BN-564 Disconnected from Game Server Fix
Tested & peer-reviewed by the GameFixDB Systems & Anti-Cheat Lab for Overwatch 2 (Error BN-564 (Disconnected from Game Server)).
Error BN-564 in Overwatch 2 occurs when the client's Battle.net session token is invalidated by Blizzard authentication servers or when packet loss causes an unrecoverable handshake drop during competitive matchmaking.
- ▸Sign out and sign back in to the Battle.net Desktop App
- ▸Flush Windows DNS and reset Winsock catalog
- ▸Disable IPv6 on your active network adapter
Step-by-Step Resolution Steps
Click steps to track progressPurge Battle.net & Blizzard Entertainment Cache (CMD)
Delete cached session tokens that prevent clean authentication with Blizzard servers.
taskkill /f /im Battle.net.exe 2>nul & taskkill /f /im Agent.exe 2>nul & rmdir /s /q "%programdata%\Battle.net" 2>nul & rmdir /s /q "%programdata%\Blizzard Entertainment" 2>nulFlush DNS and Reset WinSockets (PowerShell)
Clear stale network routing entries to Blizzard edge server datacenters.
Clear-DnsClientCache; netsh winsock reset; netsh int ip resetDisable IPv6 on Active Network Adapter
Press Win + R → type 'ncpa.cpl' → Enter → Right-click your Ethernet/Wi-Fi connection → Properties → Uncheck 'Internet Protocol Version 6 (TCP/IPv6)' → Click OK.
Did these steps resolve your error?
Your feedback updates our verified fix telemetry for players worldwide.
Community Verification & Success TelemetryLIVE
Verified by 0 competitive PC gamers across Windows 10 & 11
Rating
Blizzard Live Server Status & Maintenance Hub
Check if Blizzard Battle.net authentication servers are currently offline.
Pro Esports Advisory: Preventing Recurrence in Overwatch 2
Professional tournament players tune their Windows environment to prevent sudden runtime crashes, memory leaks, and 1% low frame stuttering:
Never immediately jump into a ranked queue after a driver or game update. Wait 2-3 minutes at the main menu until the shader compilation pipeline reaches 100% to avoid mid-round micro-freezes.
Turn off "Hardware Acceleration" in Discord, Chrome, and Spotify. Background apps using your GPU video decoder compete with the game engine for DirectX video memory (VRAM) handles.
Avoid powerline adapters and mesh Wi-Fi nodes during competitive matches. Direct Cat 6/Cat 8 Ethernet eliminates packet jitter drops that trigger anti-cheat server timeouts.
Why Does This Error Happen?
Understanding the root cause prevents recurrence during competitive matches:
- 1Battle.net OAuth authentication session token expired or corrupted in local app cache
- 2Blizzard datacenter undergoing routine maintenance or DDoS mitigation
- 3IPv6 protocol conflict causing packet loss to Blizzard regional edge relays
- 4Windows Firewall blocking Overwatch.exe outbound UDP port range 1119, 3724, 6112
Recommended Diagnostics for Overwatch 2 Players
Gaming DNS Benchmark & Ping Optimizer
Benchmark latency to Cloudflare 1.1.1.1 and Google 8.8.8.8. Apply 1-click PowerShell network optimization.
Packet Loss & Network Jitter Test
Simulate 64-tick & 128-tick game packet bursts, measure bufferbloat, and optimize TCP stack.
Frequently Asked Questions (Error BN-564 (Disconnected from Game Server))
Does BN-564 give me a competitive penalty in Overwatch 2?
Yes. If the disconnection occurs during a ranked match and you cannot reconnect within 2 minutes, the game counts it as an abandon. Following the cache clear steps above typically prevents recurring disconnections.
Can switching Battle.net server region bypass BN-564?
Yes. On the Battle.net launcher, click the globe icon above the 'Play' button for Overwatch 2 and switch from Americas to Europe or vice versa to route through an alternate login cluster.