Getting the “Error BN-115: Unable to Log In” in Overwatch 2? Don’t panic. Here’s a complete step-by-step guide to fix it quickly and get back into your matches.
If you’re currently trying to jump into an Overwatch 2 match and suddenly hit a wall, you definitely aren’t the only one. A lot of players have been running into that highly frustrating message: “Overwatch Error BN-115: Unable to log in.”
This specific connection bug has a habit of striking completely out of the blue. You might see it pop up even when your internet looks totally fine and your other online games are loading without a hitch.
The good news: While it completely disrupts your gaming session, this hiccup is almost always temporary. Plus, it rarely has anything to do with something you did wrong, so you haven’t broken your game or your console.
In this guide, we’ll walk you through exactly what this error actually means, why your game is struggling to authenticate, and the precise steps you can take to get back into your matches fast.
What Does Error BN-115 Mean in Overwatch?
To figure out how to fix the problem, it helps to know what the error is actually trying to tell you.
Essentially, this message means your device was unable to process your login request with the Battle.net servers at that exact moment. To get a bit technical, Overwatch relies on TCP ports 1119 and 3724 to verify your login. If data can’t travel freely through those specific ports, the request just gets dropped.
Think of it like a handshake: When you log in, your system tries to “shake hands” with Blizzard’s authentication servers. If that handshake fails—whether due to network lag, a server overload, or a sudden connection drop—you get hit with the BN-115 code.
It’s important to know that this does not mean your account has been banned, nor does it mean your system has permanently failed or that Blizzard’s entire network has crashed. It’s usually just a disrupted session between your game client and the server.
Players usually experience this specific login issue in a few different ways:
- An outright “Unable to log in” message.
- An infinite connecting screen that goes nowhere.
- A sudden logout right before you enter the actual game.
- The BN-115 code showing up over and over again.
Why This Error Happens
Based on reports from the community and technical data, this connection problem usually boils down to one of three main culprits:
1. Server Overload or Maintenance
Sometimes, the team at Blizzard Entertainment experiences congestion on their end, or parts of their service temporarily degrade. This is incredibly common right after major updates, seasonal events, or new content drops, where the servers simply get overwhelmed by the sheer number of players. This leads to authentication timeouts and temporary instability.
2. Network Instability or Router Buffer Issues
Your home router actually stores temporary network data in what are called “buffers.” Over time, these buffers can get totally congested. When that happens, your data packets get delayed, your login requests fail, and that crucial connection handshake breaks. This is actually one of the most common reasons you’ll see this error.
3. Account Authentication Failure
Sometimes your login session just becomes invalid or goes out of date. This happens if your login tokens expire, if there’s a sync issue between your console and your Battle.net account, or if there’s a credential mismatch.
Quick Checks Before You Try Fixes
Before you spend time digging into your advanced network settings, run through this quick diagnostic checklist to save yourself a headache:
- Are a lot of other players reporting this same error online right now?
- Has the BlizzardCS team confirmed an active outage on social media?
- Did this happen immediately after a major Overwatch update?
- Are you the only one affected in your friend group, while your other games work perfectly?
The takeaway: If you answered “yes” to those first three questions, you’re likely looking at a global server disruption. If you’re the only one dealing with it, it’s probably a local connection or session issue on your end.
How to Fix Overwatch Error BN-115: 7-Step Guide
To sort this out efficiently, follow these steps in order. Try not to skip ahead, as the simplest fixes are usually the ones that work best!
Step 1: Check Overwatch Server Status
Before you try any complex troubleshooting, make sure the issue isn’t global. If the servers are down, no local fix is going to help, and you’ll just have to wait it out.
How to do it:
- Open your browser and check the official Blizzard CS Twitter account for your region (like @BlizzardCS for the Americas or @BlizzardCSEU_EN for Europe).
- Look at third-party tracking sites like DownDetector to see if there’s a sudden spike in player reports for Overwatch or Battle.net.
- Check the top banner of your Battle.net desktop app for breaking news, maintenance schedules, or alerts about known issues.
Step 2: Restart Your Router (Most Effective)
Surprisingly, over 42% of players fix this login issue instantly just by doing this. Restarting your router clears out network congestion, resets those connection buffers, and forces a fresh session with Battle.net.
How to do it:
- Turn off your router and modem, and completely unplug them from the wall outlet.
- Wait a full 60 seconds. This is crucial, as it allows the internal capacitors to drain and completely clears the network cache.
- Plug the modem back in first and wait for the lights to become stable.
- Plug the router back in, reconnect your PC or console, and fire up Overwatch.
Step 3: Unlink and Relink Your Account
Around 35% of players manage to resolve the problem by forcing a brand-new authentication cycle.
How to do it (PC/General):
- Go to your Battle.net account settings in a web browser and log in.
- Open the “Connections” tab on the left-side menu.
- Find your linked platform (Xbox, PlayStation Network, Nintendo, etc.) and click “Disconnect.”
- Refresh the page, click “Connect” next to your platform, and verify your details to add it back.
For Console Users: Log out of the game entirely, remove the linked account using the web steps above, restart Overwatch, and relink when you log in by following the on-screen QR code or web prompt.
Step 4: Restart Battle.net and Game Client
Sometimes your session just gets stuck in the background. Closing everything completely forces a clean data transmission.
How to do it (Windows PC):
- Close Overwatch and exit the Battle.net app normally.
- Press Ctrl + Shift + Esc to open your Task Manager.
- Under the “Processes” tab, look for any lingering background tasks: Battle.net.exe, Agent.exe, and Overwatch.exe.
- Right-click each one and hit “End Task.”
- Right-click your Battle.net desktop shortcut, select “Run as administrator,” and launch the game again.
Step 5: Disable VPN or Firewall Temporarily
Strict firewalls and VPNs can sometimes scramble your authentication by misrouting TCP and UDP packets.
How to do it (Windows Defender Firewall):
- Fully disconnect and close any active VPN software (like NordVPN or ExpressVPN).
- Press the Windows key, type “Windows Defender Firewall,” and hit Enter.
- Click “Allow an app or feature through Windows Defender Firewall” on the left menu.
- Click “Change settings” (you’ll need admin privileges for this).
- Scroll down to find “Overwatch” and “Battle.net,” and make sure both the “Private” and “Public” boxes are checked. Click OK and restart.
Step 6: Switch DNS for Gaming
Changing your Domain Name System (DNS) can seriously improve your connection stability and help cut down on authentication delays. The best options are usually Google DNS (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1).
How to do it (PC & Console):
- For PC (Windows): Go to Settings > Network & Internet > Advanced network settings > More network adapter options. Right-click your connection, choose “Properties,” double-click “Internet Protocol Version 4 (TCP/IPv4),” and select “Use the following DNS server addresses.” Enter 8.8.8.8 (Primary) and 8.8.4.4 (Secondary).
- For PlayStation 5: Go to Settings > Network > Settings > Set Up Internet Connection. Select your network, hit Options, choose “Advanced Settings,” change DNS Settings to “Manual,” and enter 1.1.1.1 (Primary) and 1.0.0.1 (Secondary).
- For Xbox Series X/S: Go to Settings > General > Network Settings > Advanced Settings > DNS Settings > Manual. Enter 8.8.8.8 (Primary) and 8.8.4.4 (Secondary).
- Save your settings and restart your device.
Step 7: Run an MTR Test (Advanced Network Check)
If the error just won’t go away, an MTR test will help you figure out if there is deep network instability, packet loss, or latency spikes between your house and Blizzard’s servers.
How to do it (PC):
- Download a free diagnostic tool like WinMTR.
- Extract the file and run it as an Administrator.
- In the “Host” field, type the IP address for your regional server (use 24.105.62.129 for US West, or 185.60.112.157 for Europe).
- Click “Start” and let it run for 10 to 15 minutes while you try to play.
- Click “Stop” and check the “Loss %” column. If you see high packet loss on certain routing hops, you can export these results to show your ISP or Blizzard Support.
Is Overwatch Down Right Now? How to Tell
Because online games are complex, it’s totally possible for Overwatch to experience partial service issues where the game is technically online, but certain features (like logging in) fail.
Always check the official Blizzard status pages first, but keep an eye out for these strong signs of a wider issue:
- The error is appearing for every player trying to log in.
- None of the network fixes make a difference on your PC or console.
- The issue popped up suddenly right after a new content drop.
When this happens, waiting is usually your only real option while the engineering team works to get everything restored.
Why the Status Page May Still Look Normal
It can be confusing to see an error when the official dashboard says everything is “operational.” This happens because status indicators usually only track core systems. They might not reflect:
- Regional access issues that only affect your specific location.
- Authentication failures that are only affecting consoles (Xbox/PS5).
- Highly localized handshake or interface-level problems.
Can This Error Affect Other Overwatch Codes?
Absolutely. This specific code is just one of many login and connection errors you might encounter. It’s closely related to login timeouts, server disconnects, and game launch errors. Once you understand how these underlying authentication issues work, troubleshooting future connection problems becomes a lot easier.
FAQ
What does error BN-115 mean in Overwatch?
It simply means your login request failed to authenticate with the Blizzard servers. This is usually due to a disrupted session or temporary server instability.
How do I fix BN-115 in Overwatch 2?
Your best starting points are restarting your router, double-checking the global server status, and relinking your Battle.net account.
Is BN-115 a server issue or my connection?
It can genuinely be both. Always verify the server status first—if everything is green on Blizzard’s end, it’s time to troubleshoot your local network.
How long does BN-115 last?
If it’s a server issue, it can last anywhere from a few minutes to a few hours. If it’s a local problem, it’s usually resolved instantly once you apply the fixes mentioned above.
When should I contact Blizzard support for BN-115?
If you’ve tried all the troubleshooting steps and the issue continues for an extended period of time.
What to Do If Nothing Works
If you have walked through every single fix on this list and you’re still seeing the error, your best move is to stop retrying and reach out to Blizzard Entertainment support.
Make sure to give them all the details: your exact error code (BN-115), your platform (PC, Xbox, or PS5), whether you’re using WiFi or Ethernet, and a list of the steps you have already tried.
If you suspect it’s a server-side problem, spamming the login button won’t speed things up. Take a break, come back a little later, and try again once the network conditions have stabilized so you can get back to your matches seamlessly.
Visit Our Post Page: Blog Page