Error BLZBNTBGS80000011 is a “Connection Timeout” error that occurs when the Battle.net launcher is unable to reach the Blizzard authentication servers.
As of Wednesday, March 25, 2026, this is currently a widespread server-side issue. While Blizzard’s official status pages sometimes show “Green,” thousands of players in the Americas and EU regions are reporting that they cannot log in following today’s maintenance and a reported DDoS attack.
## Current Status (March 25, 2026)
-
Outage Type: Global Authentication Failure.
-
Symptoms: Getting stuck at “Connecting…” followed by this error code, or being placed in a login queue that never ends.
-
Official Word: Blizzard CS has confirmed they are investigating “Login issues affecting all games.” There is currently no estimated time for a fix, though these outages typically resolve within 2–4 hours.
## How to Fix It (If it’s local to you)
If your friends are online but you are still seeing this error, the “handshake” between your PC and Blizzard is likely stuck. Try these steps:
1. The “Region Swap” (Most Successful)
-
Click the Globe icon above the “Play” button in the launcher.
-
Change your region (e.g., from Americas to Asia or Europe).
-
Try to log in. If it works, log out and switch back to your original region. This forces a fresh login token.
2. The TLS Registry Fix (For Advanced Users)
Recent Windows updates or “privacy/debloat” scripts can sometimes disable the specific security ciphers Battle.net requires.
-
Open PowerShell as Admin and paste the following (this resets your security protocols to default):
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL" /f -
Restart your PC and try again.
3. Clear the “Battle.net” Cache
Corrupt temporary files are a frequent cause of this specific code:
-
Close Battle.net completely (check Task Manager).
-
Press Win + R, type
%programdata%, and hit Enter. -
Delete the
Battle.netandBlizzard Entertainmentfolders. -
Relaunch the app.
## Summary of Today’s Chaos
Today’s maintenance has been particularly rocky due to the “Stadium” event launch and high traffic. Many players are also seeing Error BN-564 or BLZ51900073 alongside this one. If the steps above don’t work, the best course of action is to wait for Blizzard to stabilize the login nodes.
Pingback: BN 115 Overwatch Battlenet Down | Overwatch Error BN-564 - Tech Tips, Guides and Support