Live - 300+ check locations
Is Battle.net down right now?
HostTracker's monitoring network reached battle.net and completed a full check without errors. It has been up for 15h 33m.
Stop finding out from a search - HostTracker's website monitoring checks the services you depend on from 300+ locations and alerts you the moment one changes.
Up
for 15h 33m
- Last check
- just now
- Next check
- -
- HTTP
- OK
Checking battle.net right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
How Battle.net has behaved
Every figure here comes from HostTracker's own checks of battle.net, not from the vendor's status page.
Response time
2646ms avg · 3458ms peak
What we check
-
HTTP2708 ms average, every 10 minutesOK
-
Ping11 ms average, every 10 minutesOK
-
Page Speed4058 ms average, every 15 minutesOK
90-day uptime
100.000% over 2 measured days · 0 incidents
- Operational
- Degraded
- Down
- No data
Incident history
Last 90 daysNo incidents recorded in the last 90 days.
About Battle.net outages
Written by the HostTracker monitoring team · updated from live probe data.
Battle.net is Blizzard's launcher, account and storefront layer beneath World of Warcraft, Overwatch 2, Diablo IV, Hearthstone, StarCraft and the Blizzard-linked Call of Duty titles, and it sits on top of each game's own separate server infrastructure rather than being one single system. A Battle.net login or launcher problem can leave every Blizzard game unreachable at once, since sign-in happens through the same account layer, but a single game being unreachable - one World of Warcraft realm offline, for instance, while others in the same region stay up - is that game's own server issue and does not mean Battle.net itself is down. Scheduled maintenance windows, especially World of Warcraft's regular weekly maintenance, are a frequent and expected cause of a game looking offline while the launcher and account services work fine.
Common causes of Battle.net downtime
Not sure whether it's Battle.net or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Battle.net login or launcher failures that block access to every Blizzard game at once, since they share the same account layer
A single World of Warcraft realm going offline while other realms in the same region stay up, which is that realm's own issue rather than a Battle.net-wide outage
Scheduled weekly maintenance, particularly for World of Warcraft, which takes specific realms or regions offline for a known window
Game-specific server incidents in one title, such as Overwatch 2 or Diablo IV, that leave the Battle.net launcher and other games unaffected
Patch-day deployment issues that block updating or launching a specific game while account sign-in itself keeps working
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests battle.net from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Battle.net being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
No - as of the most recent check, battle.net is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
No - as of the most recent check, battle.net is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
No - as of the most recent check, battle.net is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
No - as of the most recent check, battle.net is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
Probably not as a whole. Battle.net's launcher and account sign-in are shared across Blizzard's games, but each title runs its own separate server infrastructure underneath, so a single game can be unreachable while the launcher, your account and every other Blizzard game work normally. That points at a game-specific incident rather than a Battle.net-wide outage.
That's expected behavior, not a sign of a wider problem. World of Warcraft runs many separate realms, and an issue, or scheduled maintenance, affecting one realm does not affect others in the same region. Checking whether other realms are also affected is the quickest way to tell an isolated realm issue from a genuine region-wide incident.
No, it's the shared launcher, account and storefront for all of Blizzard's games, including Overwatch 2, Diablo IV, Hearthstone, StarCraft and the Call of Duty titles linked to a Blizzard account. An outage in the Battle.net account or launcher layer itself can affect all of them at once, which is different from an incident in one specific game's own servers.
That's scheduled weekly maintenance, not an outage. Blizzard takes World of Warcraft's realms down on a regular, predictable schedule for updates and upkeep, and the game reliably comes back once the window ends. It looks identical to an unplanned outage from a player's perspective, but it is expected and does not indicate anything is actually broken.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.
- Trusted since 2004
- 500,000+ websites monitored
- 300+ checkpoints worldwide