Where most complaints about this service are coming from, over the last 24 hours.
Shows where the service URL was unreachable during the detected outage periods. Percentages indicate the share of failed checks from monitoring locations in each country.
Tap what’s going wrong — one click helps thousands of others see the outage.
If the desktop client refuses to open or dies immediately, start with the basics: delete the Battle.net cache folder (found in %ProgramData%\Battle.net\), then relaunch. If that doesn't help, run the client as administrator and check whether your antivirus is quietly blocking the process — Avast and Windows Defender are known offenders here.
Error codes like BLZBNTBNA00000005 or 'login failed' usually point to one of these:
If a game install freezes at some percentage or the download speed is a fraction of what your connection can do, open the app settings and switch the download region to the nearest server manually. Also limit background bandwidth usage — the client sometimes throttles itself when another Blizzard process is running.
High latency inside a match while your internet feels fine elsewhere usually means a routing problem between you and the game server. Run a traceroute to the Blizzard server IP for your region and look for where packet loss starts. Switching from Wi-Fi to a wired connection alone can drop ping by 20–40ms in many home setups.
If a purchase fails at checkout, first confirm the billing address in your Blizzard account matches exactly what your bank has on file. Try a different browser or clear cookies — stored session data sometimes breaks the checkout flow. If the card keeps getting declined, your bank may be flagging the transaction; a quick call to them usually resolves it within minutes.
When a game crashes with asset errors or refuses to start, use the 'Scan and Repair' option in the client next to the Play button. It checks file integrity and re-downloads only what's broken, so you don't have to reinstall the whole game.