BN 115 Overwatch Battlenet Down | Overwatch Error BN-564

Players across North America and Europe are reporting widespread issues with entering the game, specifically citing errors BN-115 and BN-564.

As of today, Wednesday, March 25, 2026, there is a major ongoing outage affecting Overwatch 2 and the Battle.net launcher.

---

## Current Status (March 25, 2026)

• Authentication Servers: DOWN/DEGRADED. Most users are being placed in a long login queue (e.g., “300 players ahead of you”). When the queue reaches zero, the client fails to hand off to the game server, triggering the BN errors.

• Official Acknowledgement: Blizzard CS has acknowledged the issue on their official forums and social media (Bluesky/X), stating they are investigating “login issues and high latency.”

• Cause: Reports suggest a combination of post-maintenance instability and a potential DDoS attack targeting the Americas region, coinciding with the “Stadium” event launch.

---

## What the Error Codes Mean

• BN-115: A general “failed to connect” error. This usually means the game client cannot find the Blizzard authentication server.

• BN-564: This is a “handshake” error. It occurs when you pass the login queue but the server fails to validate your account credentials to let you into the main menu.

Also Read : BLZBNTBGS80000011 Connection Timeout” Error 

---

## Potential Fixes (Community Tested)

While the primary issue is on Blizzard’s end, some players have found success bypassing the queue with these steps:

1. The “Region Switch” Trick:

   • * In the Battle.net launcher, click the Globe icon above the “Play” button.

     • Switch your region (e.g., from Americas to Asia).

     • Launch the game. If you get in, log out and switch back to your original region. This sometimes “clears” a stuck session.

2. Steam Launch Option (Steam Users Only):

   • * If you play on Steam, right-click Overwatch 2 > Properties.

     • In the Launch Options, paste: --BNetServer=kr.actual.battle.net:1119

     • This forces the game to use a different authentication node, which helped many players bypass the BN-564 error today.

3. BNet Language Refresh:

   • * Some users report that the launcher isn’t showing the “Breaking News” alert.

     • Go to Settings > App > Language and switch to English (UK). This can force the launcher to refresh its server manifest.

Also Read : HBL Error Code 503 | What the Error Means

---

## When will it be fixed?

Historically, these mid-day outages last between 2 to 4 hours. Since the issues peaked around 12:30 PM PT / 3:30 PM ET, servers are expected to stabilize by 5:00 PM – 6:00 PM ET.