If you’re staring at BN-564 while Overwatch 2 refuses to log in, you’re not dealing with a random hiccup or a bad install. This error is Blizzard’s way of telling you the handshake between your client and Battle.net never completed. The game didn’t even get far enough to check your hero gallery or ranked MMR.
BN-564 usually appears during login, queue initialization, or right after hitting “Play,” which is why it feels so brutal. One second you’re ready to lock DPS, the next you’re kicked back to desktop like the servers just hard-countered your entire session.
BN-564 Is a Battle.net Communication Failure, Not a Gameplay Bug
At its core, BN-564 means Overwatch 2 couldn’t establish a stable HTTPS connection to Battle.net services. This isn’t about corrupted game files, broken hitboxes, or balance patches gone wrong. The client is waiting on Battle.net to respond, and that response never arrives.
Think of it like trying to queue for ranked when the matchmaker never finishes searching. The request goes out, but the server side fails before anything meaningful can happen. That’s why reinstalling the game rarely fixes BN-564 on its own.
Why It Resembles a 502 Bad Gateway Error
The reason BN-564 feels like a 502-style failure is because, functionally, it is one. A 502 error happens when one server acts as a gateway and receives an invalid or no response from another upstream server. In Overwatch 2’s case, Battle.net is the gateway, and one of Blizzard’s backend services isn’t responding correctly.
When this happens, Battle.net retries the request several times. Once those retries fail, you get BN-564. From the player’s perspective, it looks like an instant lockout, but behind the scenes the system already tried to recover.
The Most Common Causes Players Run Into
The biggest trigger is a Blizzard-side service disruption. This can be a full outage, a regional server issue, or a partial failure affecting authentication, friends lists, or matchmaking. These issues often hit during patches, events, or high-traffic hours.
Regional routing problems are another major factor. If your ISP’s route to Blizzard’s servers is unstable, packets can drop just long enough to break the login handshake. This is why some players can log in instantly while others in the same region are completely blocked.
Account conflicts also play a role. Being logged into Battle.net on multiple devices, suspended sessions, or stale authentication tokens can all cause the server to reject your request without giving a clean error message.
When It’s Actually on Blizzard’s Side
If BN-564 hits multiple players at once, especially right after a patch or during peak hours, it’s almost certainly a server-side problem. You’ll often see Battle.net friends failing to come online, delayed notifications, or the Blizzard launcher itself acting sluggish.
In these cases, no amount of router resets or file scans will brute-force a fix. The fastest way to confirm this is checking Blizzard’s service status page or seeing if players across different regions are reporting the same issue.
What You Can Safely Try Without Wasting Time
Restarting Battle.net fully, not just minimizing it, can clear stuck authentication sessions. Logging out, closing all Blizzard-related background processes, and signing back in forces a fresh connection request.
If the issue persists, switching networks briefly, such as using a mobile hotspot, can rule out ISP routing problems. If BN-564 disappears on another connection, the problem isn’t your account or PC, it’s the path your traffic is taking to Blizzard’s servers.
When none of that works and reports keep rolling in, the correct play is patience. Just like waiting out a bad meta or a broken hero patch, sometimes the smartest move is letting Blizzard fix the backend before you jump back into the fight.
Primary Causes of BN-564: Blizzard Server Outages, Battle.net Authentication, and Regional Routing Issues
At its core, BN-564 isn’t a random crash or a corrupted install. It’s a failed handshake between your client, Battle.net’s authentication layer, and Blizzard’s Overwatch 2 backend. When any part of that chain stutters, the game refuses the connection and throws BN-564 instead of letting you into the menu.
Understanding which link is breaking is the difference between wasting an hour on pointless fixes and knowing when to just wait it out.
Blizzard Server Outages and Backend Instability
The most common trigger for BN-564 is a partial Blizzard outage, not a full shutdown. Overwatch 2 might be “online,” but authentication servers, region selectors, or social services can be degraded. When that happens, the login request times out and BN-564 pops immediately.
These issues spike during patches, seasonal events, hero reworks, or Twitch drop campaigns when login traffic explodes. Ranked grinders usually notice it first, since competitive queues rely on multiple backend checks before you even reach the main menu.
If friends lists aren’t loading, endorsements are delayed, or the Battle.net launcher feels slow, that’s a dead giveaway this is on Blizzard’s side. No local fix will brute-force a server that’s already on fire.
Battle.net Authentication Failures and Account Session Conflicts
BN-564 also shows up when Battle.net authentication gets confused about your account state. Being logged in on multiple PCs, swapping regions rapidly, or leaving the launcher suspended for days can cause stale tokens that the server rejects without explanation.
This is why fully closing Battle.net, killing background Blizzard processes, and logging back in sometimes works instantly. You’re forcing a clean authentication request instead of reusing a broken session.
Account security checks can also trigger BN-564. If Blizzard flags unusual login behavior, the connection may be blocked temporarily without a clear warning, especially for returning players who haven’t logged in since earlier seasons.
Regional Routing Issues and ISP-Level Packet Loss
Even when Blizzard’s servers are stable, your connection path to them might not be. Regional routing problems happen when your ISP sends traffic through unstable nodes, causing packet loss during the login handshake. The game doesn’t see a clean response, so it fails with BN-564.
This is why switching to a mobile hotspot or VPN sometimes fixes the error instantly. You’re not fixing Overwatch 2, you’re changing the route your data takes to Blizzard’s servers.
These routing issues are often region-specific and time-based, hitting hardest during peak hours. That’s also why players in the same country can have wildly different experiences, with one logging in instantly while another is completely locked out.
How to Quickly Check If BN-564 Is a Blizzard-Side Problem (Server Status, Maintenance, and Hotfix Windows)
After ruling out local routing weirdness, the next step is figuring out whether you’re fighting your setup or Blizzard’s backend. BN-564 loves to show up during moments when everything looks fine on your end, but the servers are quietly choking. The trick is knowing where to look and what signals actually matter.
Check Blizzard’s Official Server Status First (Not Guesswork)
Start with Blizzard’s official Overwatch 2 and Battle.net service status pages. You’re looking specifically for authentication, login, or account services, not just “game servers.” If those are degraded, BN-564 is essentially guaranteed, and no amount of restarting will fix it.
Pay attention to regional status, too. NA, EU, and Asia can be in completely different states, which explains why your friend logs in instantly while you’re stuck staring at an error code. If your region shows “Investigating” or “Degraded Performance,” you’re done troubleshooting for now.
Maintenance Windows and Silent Hotfixes Are Prime BN-564 Triggers
Blizzard often deploys backend hotfixes without a full client patch, especially during balance tweaks, bug fixes, or event prep. These updates don’t always kick you offline cleanly, which leads to authentication mismatches and BN-564 during login. If the error appears right after a reset time, you’ve likely hit this window.
Scheduled maintenance usually happens early morning server time, but emergency fixes can roll out anytime. When this happens, the launcher might still say “Playable,” even though login services are half-up. That mismatch is a classic BN-564 setup.
Launcher Alerts, In-Game Symptoms, and What They Really Mean
The Battle.net launcher will sometimes show a small yellow or gray warning banner instead of a full outage notice. Players ignore these all the time, but they’re huge red flags for BN-564. If the launcher is slow to load friends lists or news panels, authentication is already under strain.
In-game, watch for missing endorsements, empty friends lists, or delayed challenge progress. These are backend calls failing quietly, not client bugs. If you see these alongside BN-564, the issue is almost certainly Blizzard-side.
Using Community Reports Without Falling for False Alarms
Sites like Downdetector and social media can help, but only if you read them correctly. A sudden spike in reports within the last 15 to 30 minutes is meaningful; scattered complaints over hours usually aren’t. Look for patterns like “can’t log in,” “BN-564,” or “stuck at connecting,” not generic lag posts.
Blizzard’s official Overwatch and BlizzardCS accounts are the final confirmation. If they acknowledge login issues, stop troubleshooting immediately. At that point, waiting is the optimal play, even if it feels worse than grinding through a bad ranked match.
When BN-564 lines up with server status warnings, maintenance timing, and widespread reports, you’ve hit a hard wall. That’s not a skill issue, a PC issue, or an ISP issue. It’s Blizzard’s court, and all you can do is wait for the servers to stabilize.
Immediate Player-Side Troubleshooting Steps That Are Safe and Worth Trying
If you’ve checked server status and there’s no confirmed outage, this is the point where light, low-risk troubleshooting makes sense. The goal here isn’t to brute-force your way past BN-564. It’s to clean up potential client-side mismatches without making things worse or wasting hours on placebo fixes.
Fully Restart Battle.net, Don’t Just Close It
Closing the launcher window isn’t enough. Battle.net loves to hang onto background processes, especially after failed authentication attempts. Fully exit Battle.net, open Task Manager, and make sure every Blizzard and Agent process is dead before reopening it.
This forces a fresh handshake with Blizzard’s login servers. If BN-564 was caused by a stale session token, this alone can fix it in under a minute.
Log Out of Battle.net, Then Log Back In Manually
Yes, this feels obvious, but it works more often than players expect. BN-564 commonly triggers when your account session expires silently, especially if you’ve been idle or switched regions recently. Logging out manually resets your authentication state instead of trying to reuse a corrupted one.
When you log back in, double-check you’re on the correct region for your account. Playing on the wrong regional endpoint can trigger login errors even if the servers look “up.”
Power Cycle Your Network to Clear Routing Issues
This isn’t about “fixing the internet.” It’s about clearing bad routing paths between you and Blizzard’s authentication servers. Fully unplug your modem and router for at least 60 seconds, then power them back on.
BN-564 has been linked to temporary ISP routing conflicts, especially after maintenance or backend updates. A clean network restart forces your connection to renegotiate a better path.
Switch Network Types if You Can
If you’re on Wi-Fi, try a wired connection. If you’re already wired, briefly test a mobile hotspot or alternate network if available. This isn’t a permanent fix, but it’s a powerful diagnostic tool.
If Overwatch 2 logs in immediately on another network, the issue is almost certainly routing or ISP-related, not Blizzard-wide. At that point, waiting or contacting your ISP makes more sense than reinstalling the game.
Disable VPNs, Proxies, and Aggressive Firewalls
VPNs are a frequent BN-564 trigger, even ones that usually work fine for gaming. Blizzard’s login services are far less tolerant than match servers, and authentication can fail if your IP location changes mid-session.
Temporarily disable VPNs, packet-filtering firewalls, or network-level ad blockers. If the game logs in cleanly afterward, you’ve found the culprit.
Restart the Overwatch 2 Client Only Once
Repeatedly hammering “Play” doesn’t help and can actually make BN-564 worse. Each failed attempt stacks authentication requests on Blizzard’s backend, which increases the chance of temporary throttling.
Restart the game once after trying the steps above, then stop. If the error persists, you’re no longer dealing with something you can brute-force through.
What Not to Do When BN-564 Hits
Do not reinstall Overwatch 2. This error is almost never tied to corrupted game files, and reinstalling won’t touch authentication services. You’re just burning bandwidth and time.
Also avoid changing DNS settings, flushing caches repeatedly, or editing network configs unless you already know what you’re doing. BN-564 is a login-layer failure, not a gameplay-layer issue.
Knowing When to Stop Troubleshooting
If none of these steps work and there’s even mild chatter about login instability, the problem is almost certainly Blizzard-side. At that point, continuing to troubleshoot is like trying to out-DPS an invulnerable boss during I-frames.
BN-564 is designed to protect account integrity when systems are unstable. When it refuses to budge, waiting isn’t giving up. It’s making the correct play.
Battle.net Client Fixes: Cache Resets, Re-Authentication, and Network Refresh Procedures
When BN-564 refuses to clear but you’re confident the issue isn’t a full Blizzard outage, the Battle.net client itself becomes the next checkpoint. These steps target authentication tokens, cached login data, and stale network handshakes that can desync your account from Blizzard’s servers.
This is the layer where BN-564 usually lives, not in Overwatch 2’s game files.
Fully Reset the Battle.net Client Cache
Battle.net aggressively caches login and session data to speed things up, but when that data goes bad, BN-564 can hard-lock your account from re-authenticating. Closing the client isn’t enough. You need to wipe the cache manually.
Exit Battle.net completely, then open the Windows Run dialog and type %ProgramData%. Delete the Blizzard and Battle.net folders inside, then relaunch the client. This forces a clean authentication request instead of reusing corrupted session data.
Force a Clean Re-Authentication (Log Out Properly)
If you’ve been suspended in a half-logged-in state, Battle.net may think you’re authenticated while Blizzard’s servers disagree. That mismatch is a classic BN-564 trigger.
Open Battle.net, log out of your account manually, and fully close the client. Wait at least 30 seconds before reopening it and logging back in. This clears stuck auth tokens instead of stacking new ones on top of a broken session.
Switch Battle.net Regions Temporarily
Regional authentication nodes don’t always fail evenly. Your local region can be struggling while another is stable, even if Overwatch 2 itself appears online.
In the Battle.net launcher, switch your region to a different one, log in, then switch back to your home region and try again. You’re not changing matchmaking servers long-term, just forcing a fresh routing path for authentication.
Perform a True Network Refresh
BN-564 can also surface when your router or modem is holding onto bad routing data, especially after ISP hiccups or firmware updates. A quick power cycle can clear that without touching advanced network settings.
Unplug your modem and router for at least 60 seconds, then power them back on fully before launching Battle.net again. This refreshes your public IP and resets routing tables that Blizzard’s login servers rely on.
When These Fixes Work — and When They Won’t
If one of these steps clears BN-564 immediately, the issue was client-side desynchronization, not your account or Blizzard’s core services. That’s the best-case scenario, and it means you’re safe to queue ranked without worrying about repeat lockouts.
If none of these steps work and login attempts still fail instantly, the error is almost certainly Blizzard-side. At that point, BN-564 isn’t blocking you because of something you did. It’s doing its job by stopping unstable logins until the backend settles.
Advanced Network Checks: DNS, ISP Routing, VPN Conflicts, and Firewall Considerations
If BN-564 is still blocking you after a clean re-auth and router reset, you’re officially in advanced territory. At this point, the error usually means Battle.net’s login handshake is failing somewhere between your PC and Blizzard’s authentication edge servers. That doesn’t automatically mean Blizzard is down, but it does mean something in your network path is interfering.
These checks won’t magically fix a full Blizzard outage. What they do is eliminate silent conflicts that only affect specific players, ISPs, or network setups.
Flush or Change Your DNS to Eliminate Bad Resolution
DNS issues are a sleeper cause of BN-564, especially after ISP maintenance or Windows updates. If your system is resolving Battle.net or Blizzard auth servers to outdated or broken IPs, login requests can fail instantly with no visible delay.
Open Command Prompt as administrator and run ipconfig /flushdns, then restart Battle.net. If the error persists, switch to a public DNS like Google (8.8.8.8) or Cloudflare (1.1.1.1). This forces fresh server lookups instead of relying on cached or ISP-controlled DNS entries.
ISP Routing and Regional Peering Problems
Sometimes the issue isn’t your connection quality, but how your ISP routes traffic to Blizzard’s infrastructure. Certain ISPs experience bad peering routes where traffic technically connects but drops or loops during secure authentication checks.
This is why BN-564 can affect only some players in a region while others log in fine. If using a mobile hotspot or alternate connection lets you log in instantly, your ISP’s routing is the problem. In those cases, waiting or contacting your ISP is the only real fix.
VPNs and Network Accelerators Can Break Authentication
VPNs, gaming accelerators, and “ping reducers” often interfere with Battle.net’s security checks. Even if Overwatch 2 launches normally, the authentication layer may reject the connection if the IP changes mid-handshake or routes through flagged regions.
Disable all VPNs completely before launching Battle.net, not just before launching the game. If BN-564 disappears immediately, you’ve found the culprit. Blizzard’s login servers are far less forgiving than matchmaking servers when it comes to altered routing paths.
Firewall and Antivirus Blocking Secure Handshakes
Overzealous firewalls and antivirus software can silently block Battle.net’s HTTPS authentication traffic. This is especially common after security software updates that reset rules without warning.
Temporarily disable your firewall or antivirus and try logging in again. If the error clears, add Battle.net and Overwatch 2 as explicit exceptions rather than leaving protection off. If disabling security software changes nothing, the problem isn’t local and isn’t something you can brute-force through.
Knowing When to Stop Troubleshooting
If DNS changes, VPN removal, firewall checks, and alternate connections all fail, BN-564 is no longer actionable on your end. That means Blizzard’s authentication backend is either overloaded, rate-limiting logins, or resolving a regional service disruption.
At that point, repeated login attempts won’t help and can sometimes extend the lockout window. The smartest play is to wait for Blizzard to stabilize the service, monitor official status pages, and avoid spamming retries that only stack more failed requests.
Account and Region Conflicts That Can Trigger BN-564 (Cross-Region Logins, Merges, and Suspensions)
If your network checks out and Battle.net isn’t actively melting down, BN-564 often points to something tied directly to your account. This is where things get especially frustrating, because the error doesn’t say “account issue” outright. Instead, Blizzard’s authentication servers quietly refuse the login when account data doesn’t line up cleanly across regions or services.
Unlike pure server outages, these problems can hit individual players while friends queue into matches without a hitch. That’s why it’s critical to rule out account-level conflicts before assuming Blizzard just broke everything again.
Cross-Region Logins and Mismatched Battle.net Regions
One of the most common hidden triggers for BN-564 is logging into the wrong Battle.net region. Overwatch 2 technically lets you switch between Americas, Europe, and Asia, but authentication tokens don’t always translate cleanly between regions.
If your Battle.net launcher is set to a region different from where your account was last active, the login handshake can fail instantly. This is especially common for players who traveled, used VPNs previously, or installed the client on a new PC.
Open the Battle.net launcher, manually select your usual region, fully log out, then restart the launcher before trying again. Don’t rely on “last used” settings. If switching back to your home region fixes BN-564, the issue was never your connection—it was a region mismatch Blizzard didn’t explain.
Account Merges and Cross-Progression Desync
Account merges are another major BN-564 landmine. Overwatch 2’s cross-progression system ties console and PC data together, but the merge process can leave your account in a half-synced state if it was interrupted or recently completed.
When this happens, Battle.net authentication sees conflicting entitlements or profile flags and refuses the login. The game never loads far enough to tell you what’s wrong, so you just get BN-564 instead.
If you recently merged console and PC accounts, give it time. Logging in repeatedly won’t force the merge to finish and can actually slow resolution. Waiting several hours, sometimes up to 24, is often the only fix unless Blizzard manually resolves the sync on their end.
Temporary Suspensions, Restrictions, and Silent Locks
BN-564 can also appear if your account is temporarily restricted, even if you haven’t received a clear suspension notice. Payment disputes, chargebacks, or automated behavior flags can all trigger silent login blocks.
These aren’t always full bans. Sometimes Blizzard limits access while verifying account activity, and the authentication server simply denies the request without surfacing details to the client.
Check your Battle.net account page and email associated with your Blizzard ID. If there’s a restriction, no amount of reinstalling or network tweaking will fix BN-564. This is one of those cases where the issue is entirely on Blizzard’s side, and only time or support intervention will resolve it.
Logging In on Multiple Devices or Sessions
Rapidly logging into Battle.net on multiple PCs, consoles, or even mobile apps can trip Blizzard’s rate-limiting systems. If the authentication service detects overlapping sessions or repeated token requests, it may temporarily block new logins as a security precaution.
This often happens to ranked grinders who hop between PC and console or players testing settings on multiple machines. The system interprets the behavior as suspicious, even if it’s completely legitimate.
Log out of Battle.net everywhere, wait at least 10–15 minutes, then try again on a single device. If BN-564 clears after a cooldown period, you were rate-limited, not disconnected.
When Account Conflicts Mean Waiting Is the Only Play
If you’ve confirmed the correct region, avoided VPNs, waited after merges, and checked for restrictions, there’s nothing left to troubleshoot locally. At that point, BN-564 means Blizzard’s account services haven’t reconciled your data yet.
This is the hardest version of the error to swallow because there’s no skill-based workaround and no tech trick to outplay it. Spamming logins only increases failed requests and can extend the lockout window.
When BN-564 is account-driven, patience isn’t just recommended—it’s mandatory. Monitor Blizzard’s service updates, keep retries minimal, and let the backend catch up before diving back into matches.
When There Is No Fix: How Long BN-564 Typically Lasts and What to Do While Waiting
Once you’ve ruled out local issues and account missteps, BN-564 shifts from a puzzle you can solve into a server-side problem you have to endure. This is the point where understanding Blizzard’s timelines matters more than tweaking settings or rebooting hardware.
BN-564 isn’t random. It’s a symptom of Battle.net authentication desync, and those systems usually correct themselves on a predictable cadence depending on the root cause.
Typical Duration: Minutes, Hours, or a Full Maintenance Window
In most cases, BN-564 lasts between 10 minutes and 2 hours. These are usually tied to short-lived Battle.net hiccups, backend restarts, or regional authentication throttles that resolve without a formal announcement.
When the error coincides with Overwatch 2 patches, seasonal rollovers, or hotfix deployments, expect longer downtime. Authentication servers are often the last systems to stabilize, even after the game itself comes back online.
If BN-564 persists beyond 6–8 hours, especially across multiple login attempts spaced out over time, you’re likely dealing with an account sync issue or a wider Battle.net service disruption. At that point, waiting isn’t just smarter—it’s required.
How to Tell If Blizzard Is Still Fixing It
The fastest signal is Blizzard’s official CS and Battle.net status pages, not community chatter. If authentication services show “degraded” or “investigating,” BN-564 is actively being worked on, even if Overwatch 2 appears online.
Social channels help, but they lag behind real-time fixes. By the time Twitter lights up, Blizzard engineers are usually already mid-patch or rolling restarts behind the scenes.
If streamers and high-profile players suddenly log back in without client updates, that’s your cue. The backend flipped, and your next login attempt has a real chance of sticking.
What You Should and Shouldn’t Do While Waiting
Do space out login attempts. Hitting Battle.net every 30–60 minutes is safe and keeps you from triggering additional rate limits.
Don’t reinstall Overwatch 2, reset your router repeatedly, or swap regions hoping for a miracle. Those actions won’t touch an authentication-layer failure and can actually create new conflicts once services normalize.
If you’re itching to play, use the downtime productively. Review patch notes, tweak hero loadouts, or warm up aim in another FPS. When BN-564 clears, you want to jump straight into matches, not troubleshooting mode.
When to Contact Support and When Not To
If BN-564 lasts more than 24 hours with no service alerts and no change across multiple devices or networks, that’s when a support ticket makes sense. Provide timestamps, region, platform, and confirmation that other Battle.net games fail to authenticate.
Before that window, support will almost always tell you to wait. They don’t have a manual override for live authentication queues, and submitting tickets too early won’t speed things up.
This error feels personal, but most of the time it’s systemic. Blizzard fixes it once, and thousands of players slide back online at the same moment.
In Overwatch 2, patience can be as important as positioning or ult economy. When BN-564 hits and there’s no fix, step back, let the servers breathe, and be ready. The moment Battle.net stabilizes, the doors open fast, and the matchmaker doesn’t wait.