To Fix error BN‑564 in Overwatch 2, Restart your console / PC / router. If the error is caused by server downtime, nothing you do locally will work.
Here’s a detailed guide to understanding error BN‑564 in Overwatch 2 and how to fix it (depending on your platform).
ℹ️ What Is Error BN‑564?
-
The official Blizzard support article describes BN‑564 as:
“Sorry, we were unable to log you in. Please try again later.”
-
On consoles, Blizzard states the error often happens when Overwatch 2 servers are down for maintenance.
-
If the servers are not under maintenance, the support article suggests unlinking and re‑linking your console / platform account via your Battle.net account.
-
In community threads, many users on PC / Steam have also reported the error, often when Steam‑Blizzard linkage is involved.
🛠 How to Fix BN‑564 (Step by Step)
Here are the most common and practical fixes. Try them in order, and test logging in after each.
| # |
Fix |
Why It Helps |
|---|---|---|
| 1 | Check server / maintenance status | If the error is caused by server downtime, nothing you do locally will work. Check BlizzardCS on Twitter or Overwatch’s status pages. |
| 2 | Restart your console / PC / router | Clears temporary network or cache glitches. Many users report this helps. |
| 3 | Unlink and re‑link your platform account | On Battle.net account settings → “Connected Accounts” / “Connections”, disconnect the console/platform, then relink it. |
| 4 | Use correct account / linkage with Steam | If you play Overwatch 2 via Steam, ensure your Steam account is properly linked to your Blizzard (Battle.net) account. Some reports say linking via web helps bypass the error. |
| 5 | Log out and back in | In Blizzard / Battle.net client or webpage, log out, then log back in. Might fix token or session issues. |
| 6 | Clear caches / temporary data | On console, clear cache or reinstall Overwatch 2. On PC, you can try verifying game files or reinstalling. |
| 7 | Contact Blizzard Support | If none of the above work, the issue may be account-specific or need backend fixes from Blizzard. |
🔍 Platform-Specific Notes & Cautions
-
On consoles, unlinking your Battle.net‑console link is explicitly recommended by Blizzard.
-
Be careful when unlinking and relinking — there may be cooldowns in how often you can link/unlink certain accounts. In user discussions, some mention cooldown wait times.
-
On PC/Steam, the issue often revolves around the Steam → Blizzard account linkage. Users say logging in via the Blizzard web, then linking Steam, resolved the error for them.
-
This error sometimes appears only on one account, while other accounts on the same console/PC work fine. That suggests the issue might be with your account linkage.
Be the first to comment