The BN-564 Error in Overwatch 2, Traced From When It Started to What Actually Clears It

BN-564 isn't a new error. Overwatch 2 players first saw it in numbers during Season 6: Invasion, then it hung around into Season 7 and picked up again when the Steam version launched and started mixing accounts across platforms. The error message itself is generic Battle.net language, which is why it's so hard to search for a useful answer: the same code shows up in different contexts on Blizzard's backend, and most of the "how to fix BN-564" pages online mash all of those into one list. Understanding when BN-564 tends to appear tells you which of the fixes actually matches your case.

What Blizzard Is Actually Telling You

BN-564 is a Battle.net authentication failure. Your Overwatch 2 client is trying to confirm with Blizzard's servers that your account is valid for this session and something in that exchange is failing. That "something" falls into a few buckets:

• The Battle.net authentication service is under strain (usually right after a patch or during a big event launch)
• Your Battle.net account has a stale session that needs to be cleared on Blizzard's side by logging out fully
• Your network is dropping the authentication handshake somewhere between your machine and Blizzard's servers
• The Steam account link to Battle.net is in a bad state, especially if you play across both

The error message doesn't tell you which one. You have to figure that out from context, which is why timing matters.

Timing Tells You a Lot

Before touching anything, look at when the error is hitting you.

Right after a patch or new season? Almost always backend load. Blizzard's authentication service takes a beating whenever the population spikes, and BN-564 becomes common for a few hours. No local fix will help. Wait it out. If everyone in your group is getting it at the same moment, this is definitely the case.

Consistently at the same time every evening? Your route to Blizzard's servers is congesting at that hour. Local fixes might help, network-layer fixes definitely will.

Randomly and only for you? Something on your machine or Battle.net account state is the problem. This is where the actual troubleshooting starts.

Only when launching from Steam? The Steam-to-Battle.net handoff is the failure point. Different fix path, covered further down.

Skipping this ten-second question is why players end up reinstalling Battle.net twice and still get the error the next evening.

The Fixes That Match Each Case

If it's a backend event

Confirm by checking the official Overwatch status page and community reports. If dozens of players are reporting BN-564 within the last hour, log out and try again in 30 to 90 minutes. Reinstalling anything during a backend outage is a waste of an evening.

If it's a stale session

Fully log out of Battle.net (not just close it, actually sign out), close the Battle.net client, then relaunch it and sign in fresh. This clears the session token that might have gone bad. On PlayStation and Xbox, restart the console to force the platform session to refresh too.

If it's the Steam launch path

Blizzard added Steam support for Overwatch 2, and the link between your Steam and Battle.net accounts can end up in a weird state where authentication rejects the session. The fix is deliberate:

1. Launch the game from Battle.net first, get to the main menu.
2. Close it and log out of Battle.net.
3. Now relaunch through Steam.

This sounds silly and it is, but it re-syncs the account link and clears BN-564 for a lot of Steam-side players.

If it's a network authentication drop

Router reboot is the actual first move here, and it works more often than it should. Consumer routers accumulate stale NAT sessions, and the Battle.net authentication handshake is exactly the kind of long-lived TCP session that stale NAT breaks. Unplug the router for 60 seconds and plug it back in.

If reboot doesn't help and BN-564 keeps coming back during a specific time window, the handshake is failing somewhere between your ISP and Blizzard's authentication servers. This is the case where a routing tool becomes relevant. GearUP works on the path between your machine and the game's servers, keeping the authentication handshake on a stable route rather than the congested peer your ISP defaults to during prime time. This matters specifically for Battle.net because its authentication has short timeouts, so a route that intermittently drops packets fails the handshake even when your speed test looks fine. Console players who can't install anything on the machine itself can use GearUP HYPEREV as a network-level device, which does the same job for the whole console at the router layer.

Warning: Some guides suggest fully disabling your antivirus or Windows Firewall to test BN-564. Don't do that as a first move. Add Battle.net.exe and Overwatch.exe to your firewall's exceptions and to your antivirus's exclusions instead. Turning off protection wholesale invites problems bigger than a login error.

What Rarely Actually Fixes BN-564

The most common bad advice for this specific error:

• Reinstalling Overwatch 2. Doesn't touch authentication state or network path. Only fixes it when it happens to coincide with an update the reinstall pulls down.
• Changing DNS servers. DNS resolves names once. It doesn't affect the ongoing authentication session. Might slightly speed up initial connection, won't stop BN-564 from returning.
• Running the game as administrator. Doesn't affect network traffic. Might affect a small set of file permission errors, not this one.

A Note on Platform Behavior

BN-564 shows up differently across platforms even when the root cause is the same. On PC you see it as a login screen bounce. On PlayStation you often see the game get to the menu and then kick you out with the code. On Xbox it sometimes appears as a "cannot connect to server" message that only reveals BN-564 in the details view. If you're on console, the fix hierarchy is the same, but the router reboot step matters more because you can't easily install anything on the console to isolate the network path. HYPEREV or a similar router-level tool is the only way to actually address the route without a PC in the picture.

The pattern to remember with BN-564 is this: identify the timing, match the fix to that timing, and don't jump to the destructive options first. Most of the time this error clears within the first two low-effort attempts. The rare cases where it doesn't are almost always a persistent route issue between you and Blizzard's authentication servers, and that has its own class of fix.