isitdownrightnow.app
  1. Home
  2. Services
  3. Blizzard Battle.net
Blizzard Battle.net blizzard.com

Is Blizzard Battle.net down right now? Live status and outage tracker

No, Blizzard Battle.net is up.

No widespread outage detected. 16 user reports in the last hour is within the normal range.

Live Last spike Data refreshes every 5 minutes
Not working for you?
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

191 reports in total, counted in 15-minute windows

In the last hour, 16 problem reports came in for Blizzard Battle.net, against about 16 at this time on a usual day. Over the last 24 hours there were 191 reports. Worldwide, most recent reports were about login (36%) and server connection (21%). The last spike in reports was 46 h ago and lasted 26 min. These are user reports from the US, where most people report Blizzard Battle.net problems.

Around the world right now: normal in 71 other countries. Most reports in the last hour: Sweden 4 · France 2 · Canada 2. By country

In the past 24 hours, 191 user reports came in for Blizzard Battle.net. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day. The busiest 15-minute window had 7 reports, about 10 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Reports, last hour
16
33% on the hour before
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
7
7 reports, 10 h ago
Last 24 hours

Blizzard Battle.net outages and problems

In the past 24 hours, 191 user reports came in for Blizzard Battle.net. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 7 reports, about 10 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Blizzard Battle.net stayed at their usual level the whole time.
This month

Blizzard Battle.net in November 2026

Problem reports in November
52
Outage spikes
0
Periods of elevated reports
0

Monthly report for November 2026

What went wrong

What people said was wrong in recent problem reports for Blizzard Battle.net worldwide.

  1. Login36%
  2. Server Connection21%
  3. Game Play18%
  4. Game Launch13%
  5. Downloads and updates10%
  6. Purchases3%

Share of 39 recent reports that said what was wrong, from every country listed below.

World map

Blizzard Battle.net reports around the world

In the last 24 hours, 407 problem reports about Blizzard Battle.net came in from 43 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
The US numbers above Normal 10190
Sweden Normal 46
France Normal 227
Canada Normal 224
The UK Normal 29
Spain Normal 26
Japan Normal 127
Brazil Normal 115
Germany Normal 114
Finland Normal 14
Norway Normal 13
Italy Normal 12

Each country's status compares its reports with the usual level there. 60 more countries had 80 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Blizzard Battle.net problem spikes, last 30 days

Since 5 October, Blizzard Battle.net had 6 outage spikes and 5 periods of elevated reports. The longest lasted 1 h 46 min, on 27 October.

  • Sat 3 Oct: no data
  • Sun 4 Oct: no data
  • Mon 5 Oct: 1 report
  • Tue 6 Oct: 3 reports
  • Wed 7 Oct: 2 reports
  • Thu 8 Oct: 4 reports
  • Fri 9 Oct: 3 reports
  • Sat 10 Oct: 2 reports
  • Sun 11 Oct: 2 reports
  • Mon 12 Oct: 1 report
  • Tue 13 Oct: 16 reports
  • Wed 14 Oct: 2 reports
  • Thu 15 Oct: 1 report
  • Fri 16 Oct: 4 reports
  • Sat 17 Oct: 4 reports
  • Sun 18 Oct: 1 report
  • Mon 19 Oct: 0 reports
  • Tue 20 Oct: 1 report
  • Wed 21 Oct: no data
  • Thu 22 Oct: 1 report
  • Fri 23 Oct: 3 reports
  • Sat 24 Oct: 2 reports
  • Sun 25 Oct: 2 reports
  • Mon 26 Oct: 4 reports
  • Tue 27 Oct: 15 reports (outage spike that day)
  • Wed 28 Oct: 58 reports (outage spike that day)
  • Thu 29 Oct: 451 reports (outage spike that day)
  • Fri 30 Oct: 217 reports (elevated reports that day)
  • Sat 31 Oct: 186 reports
  • Sun 1 Nov: 52 reports
  • Elevated reports
    Fri 30 Oct, 06:21–06:47
    Lasted 26 min
    10peak reports
  • Outage
    Thu 29 Oct, 19:43–20:09
    Lasted 26 min
    17peak reports
  • Elevated reports
    Thu 29 Oct, 04:40–04:57
    Lasted 17 min
    10peak reports
  • Elevated reports
    Thu 29 Oct, 02:57–03:12
    Lasted 15 min
    13peak reports
  • Outage
    Thu 29 Oct, 01:36–02:17
    Lasted 41 min
    169peak reports
  • Outage
    Wed 28 Oct, 10:34–11:00
    Lasted 26 min
    15peak reports
  • Elevated reports
    Wed 28 Oct, 07:20–07:49
    Lasted 29 min
    11peak reports
  • Elevated reports
    Wed 28 Oct, 00:47–01:02
    Lasted 15 min
    13peak reports

3 earlier spikes in this period.

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • The US881
  • Japan172
  • France101
  • Canada92
  • Germany66
  • Brazil59
  • Australia49
  • The UK43

Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services

Troubleshooting

How to fix Blizzard Battle.net not working

Blizzard Battle.net is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach blizzard.com over your own connection, right now. Nothing is sent to us or stored.

  1. Read the live numbers before anything else

    You searched 'is Blizzard Battle.net down right now', so start at the top of this page. Status reads operational, uptime sits at 100.00% across the past 24 hours, and players filed 191 reports in that window. Trust the spike. When reports climb into the hundreds while status still says operational, Blizzard's monitoring lags behind what players feel, and the honest answer is patience rather than a reinstall.

  2. Launcher stuck on 'Connecting' or a blank login

    Kill Agent.exe in Task Manager first, because a frozen Agent blocks the launcher before the login screen ever appears. Then close the app, delete the Cache folder at C:/ProgramData/Blizzard Entertainment/Battle.net, and start it again; the launcher rebuilds that folder clean on the next boot. Sync your Windows clock as well. Battle.net rejects your login token whenever system time drifts more than a few minutes, which looks identical to a server outage from your side of the screen. These two steps clear most 'Blizzard Battle.net not working today' complaints that had nothing to do with Blizzard.

  3. Check your connection and DNS

    Open Command Prompt and run ipconfig /flushdns, then switch your DNS to 1.1.1.1 or 8.8.8.8 if logins keep timing out. Disable your VPN and any proxy too, because the Battle.net client refuses to authenticate through a half-configured proxy and throws a BLZBNTBNA login error that reads like downtime. Routers hold stale routes. Reboot yours, and if the client still hangs, check the Blizzard Battle.net network status page, since regional ISPs break the path to Blizzard login servers while every other site loads fine.

  4. Cross-check regions and third-party trackers

    Flip your region from Americas to Europe in the launcher settings before you assume 'Blizzard Battle.net down' means everyone is down. Regions fail independently. Blizzard runs separate login hardware per region, so this ten-second test tells you whether the problem sits on their side or yours. Compare our chart against the Blizzard Battle.net down detector page too; 'Blizzard Battle.net outage today 2026' searches spike the moment both trackers agree, and the last confirmed incident here was more than 24 hours ago. For per-game detail, the official Blizzard Battle.net server status page lists WoW, Overwatch 2, Diablo IV, and Hearthstone separately. Open it when your only question is 'is Blizzard Battle.net working' for your game tonight.

While Blizzard Battle.net is down: what to use instead

  • Offline mode in the desktop app If the app logged you in recently, some games such as Diablo II: Resurrected can still load offline characters, though anything that needs the servers stays locked until login works again.
  • The website in a browser When only the desktop launcher hangs, the account pages on the website may still open for password changes and security settings.
  • Discord Your group can keep talking on Discord while the friends list and in-game chat are down.
  • Steam or Epic Games Store Good for playing something else while you wait.
Your device

Fix Blizzard Battle.net on Windows, Mac, Android and iPhone

Blizzard Battle.net on Windows

Fix
To fix Blizzard Battle.net on Windows, close the app completely via Task Manager, delete the Battle.net Cache folder in ProgramData, and relaunch it as administrator. Setting up an exception in your Windows Defender Firewall can also resolve connection blocks.
Check
You can tell Blizzard Battle.net is down on Windows if the launcher fails to connect, displays error codes like BLZBNTBGS, or shows a queue prompt. You can also check the official Blizzard CS Twitter/X account for live server status updates.
Command Prompt
ping blizzard.comTest whether Blizzard Battle.net's servers reply
nslookup blizzard.comCheck that Blizzard Battle.net's DNS resolves
tracert blizzard.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Blizzard Battle.net on Mac

Fix
If Blizzard Battle.net is not working on macOS, delete the Battle.net files in the Shared directory and restart the client. Ensure the application has the necessary permissions under System Settings > Privacy & Security.
Check
Confirm if Blizzard Battle.net is down on your Mac by checking if the client gets stuck on the 'Connecting' screen or fails to load your game library. The 'Breaking News' alert in the launcher will also announce active server outages.
Terminal
ping -c 4 blizzard.comTest whether Blizzard Battle.net's servers reply
nslookup blizzard.comCheck that Blizzard Battle.net's DNS resolves
traceroute blizzard.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Blizzard Battle.net on Android

Fix
Fix the Blizzard Battle.net mobile app on Android by clearing its cache and data in your device's App settings, or reinstalling it from the Google Play Store. Disabling battery optimization for the app can also prevent connection drops.
Check
Determine if Blizzard Battle.net is down on Android if the app fails to load your friends list, or if authenticator approvals do not push through. You can also check for connection timeout errors on the login screen.

Blizzard Battle.net on iPhone and iPad

Fix
To resolve Blizzard Battle.net issues on iOS, force close the app and restart your iPhone, or reinstall it from the App Store. Switching from Wi-Fi to cellular data can also bypass local network routing issues.
Check
You can tell Blizzard Battle.net is down on iOS if you experience infinite loading wheels or fail to receive login verification prompts. Check the App Store for any pending updates if the app refuses to connect.
Ranked by peak

Biggest Blizzard Battle.net problems so far

  1. 1
    OutageLasted 41 min
    169reports in 15 min
  2. 2
    OutageLasted 1 h 13 min
    33reports in 15 min
  3. 3
    OutageLasted 1 h 46 min
    18reports in 15 min

Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.

Same time

Problems at the same time as Blizzard Battle.net

Since 5 October, 10 of Blizzard Battle.net's 11 spikes in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

Most often at the same time

How many of Blizzard Battle.net's spikes overlapped one of theirs.

During the latest spike

Blizzard Battle.net: Fri 30 Oct, 06:21 to 06:47

14 more services. Red dot: outage. Amber dot: elevated reports.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report Blizzard Battle.net problems

The busiest hour for reports about Blizzard Battle.net is 01:00 to 02:00 Central European time, and the busiest day is Thursday.

By hour of the day

  • 00:00 to 01:00: 1.8 reports on an average day
  • 01:00 to 02:00: 2.9 reports on an average day
  • 02:00 to 03:00: 2.1 reports on an average day
  • 03:00 to 04:00: 2.6 reports on an average day
  • 04:00 to 05:00: 1.5 reports on an average day
  • 05:00 to 06:00: 1.5 reports on an average day
  • 06:00 to 07:00: 0.74 reports on an average day
  • 07:00 to 08:00: 0.83 reports on an average day
  • 08:00 to 09:00: 0.27 reports on an average day
  • 09:00 to 10:00: 0.54 reports on an average day
  • 10:00 to 11:00: 0.49 reports on an average day
  • 11:00 to 12:00: 0.18 reports on an average day
  • 12:00 to 13:00: 0.51 reports on an average day
  • 13:00 to 14:00: 0.39 reports on an average day
  • 14:00 to 15:00: 0.92 reports on an average day
  • 15:00 to 16:00: 0.98 reports on an average day
  • 16:00 to 17:00: 0.93 reports on an average day
  • 17:00 to 18:00: 0.97 reports on an average day
  • 18:00 to 19:00: 2.3 reports on an average day
  • 19:00 to 20:00: 1.8 reports on an average day
  • 20:00 to 21:00: 1.8 reports on an average day
  • 21:00 to 22:00: 2.2 reports on an average day
  • 22:00 to 23:00: 2.1 reports on an average day
  • 23:00 to 00:00: 1.9 reports on an average day

By day of the week

  • Monday: 1.8 reports on an average Monday
  • Tuesday: 7.5 reports on an average Tuesday
  • Wednesday: 21 reports on an average Wednesday
  • Thursday: 76 reports on an average Thursday
  • Friday: 55 reports on an average Friday
  • Saturday: 49 reports on an average Saturday
  • Sunday: 18 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when Blizzard Battle.net goes down

Blizzard Battle.net runs the launcher, store, friends list, and matchmaking behind World of Warcraft, Overwatch, Diablo, and Call of Duty. One failed login server strands you.

When Blizzard Battle.net goes down, the app hangs on 'Connecting', your friends list empties, the store refuses to load, and games like Diablo IV boot you to the login screen mid-session because the saves sit server-side. That hurts. 191 outage reports came in over the last 24 hours, and the last outage spike was more than 24 hours ago, so check the chart above before you reinstall anything.

Servers and network

Blizzard Battle.net IP address, servers and network

IPv4 addresses
108.132.68.161
Show all 2
  • 54.171.109.242
IPv6
Not offered
Network
AS16509 · Amazon.com, Inc., registered in the United States
Served through
Amazon Web Services
DNS hosted by
Amazon Route 53
HTTPS certificate
Issued by Amazon, valid until 25 Mar 2027 (143 days)
HTTP/3
Not advertised
Our check
Answered in 383 ms

Checked from our server in Frankfurt, Germany, 31 h ago, for www.blizzard.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from www.blizzard.com. Fastest from Tokyo (50 ms), slowest from São Paulo (423 ms). The answers came through 2 networks: Amazon.com, Inc. (AS16509) and Amazon.com, Inc. (AS14618).

LocationResultTimeAddress reached
FrankfurtGermanyUp · HTTP 30781 ms54.171.109.242Amazon.com, Inc.
ViennaAustriaUp · HTTP 307117 ms108.132.68.161Amazon.com, Inc.
MilanItalyUp · HTTP 307116 ms108.132.68.161Amazon.com, Inc.
ParisFranceUp · HTTP 30783 ms108.132.68.161Amazon.com, Inc.
AmsterdamNetherlandsUp · HTTP 307143 ms108.132.68.161Amazon.com, Inc.
MadridSpainUp · HTTP 307127 ms54.171.109.242Amazon.com, Inc.
WarsawPolandUp · HTTP 307174 ms108.132.68.161Amazon.com, Inc.
Los AngelesUSAUp · HTTP 307210 ms52.70.105.143Amazon.com, Inc.
São PauloBrazilUp · HTTP 307423 ms52.70.105.143Amazon.com, Inc.
SingaporeSingaporeUp · HTTP 307233 ms54.249.64.31Amazon.com, Inc.
TokyoJapanUp · HTTP 30750 ms52.194.69.102Amazon.com, Inc.

Checked with check-host.net from its servers in these cities 31 h ago, for www.blizzard.com. Time is how long each server took to load the page.

Questions

Blizzard Battle.net FAQ

Is Blizzard Battle.net down right now?
Right now the answer is operational. This page runs on live crowd-sourced reports: over the past 24 hours it logged 191 of them from players who could not log in, launch a game, open the store, or see their friends list. A sudden wave of those reports means Blizzard's login cluster is failing for everyone, while one report from you alone points back at your own connection. The last confirmed drop was more than 24 hours ago.

What is the Blizzard Battle.net server status?
Current reading: operational. Blizzard runs Battle.net as separate clusters for logins, the games themselves, the store, and the desktop app, so World of Warcraft can drop while the store still loads, which sends people chasing router fixes they never needed. Last full outage ended more than 24 hours ago.

Why is Blizzard Battle.net not working today?
Most Battle.net outages trace back to one of four culprits. Scheduled maintenance comes first: Blizzard takes the whole platform offline on Tuesdays and publishes the window in advance, so check the calendar before you panic. Patch days come second. A big Overwatch or World of Warcraft update swamps the login queues even while the servers stay healthy, and the jam clears once the rush thins out. DDoS attacks form the third group because they have frozen the launcher for hours in past years, and regional failures take fourth place by knocking out Europe while North America keeps playing. Our feed shows 191 reports in the last day, so weigh your symptom against that count before you blame your internet.

How do I check if Blizzard Battle.net is down?
Start with the badge at the top of this page: it reads operational. We built this site as a Blizzard Battle.net down detector: the 191 counter and the report graph update themselves whenever a login fails anywhere. Cross-check Blizzard's official server status page, then look at what players post on X and Reddit, since complaints there surface about ten minutes before any official notice. That's why people who search 'is Blizzard Battle.net working' or 'Blizzard Battle.net outage today 2026' tend to land here first. Before you reinstall the client, compare your symptom against the graph.
For your site

Put the Blizzard Battle.net status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

Blizzard Battle.net status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/battle-net/"><img src="https://isitdownrightnow.app/badge/battle-net.svg" alt="Blizzard Battle.net status" height="20"></a>
Markdown, for README files
[![Blizzard Battle.net status](https://isitdownrightnow.app/badge/battle-net.svg)](https://isitdownrightnow.app/services/battle-net/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Blizzard Battle.net

The status on this page comes from user-submitted problem reports for Blizzard Battle.net, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Blizzard Battle.net, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Blizzard Battle.net doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.

Elsewhere

Check other services

See all 500+ services

Problems elsewhere right now

Strips: user reports, last 6 hours, 15 minutes a segment.