Battle.net

Is Battle.net down?

No problems detected

If you are having issues, please submit a report below.

Battle.net is an online gaming platform operated by Blizzard Entertainment. Is enables online game-play for games including World of Warcraft, Starcraft, Diablo, Hearthstone and Heroes of the Storm.

Problems in the last 24 hours

The graph below depicts the number of Battle.net reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Battle.net Outage Chart 03/31/2026 06:30

At the moment, we haven't detected any problems at Battle.net. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by Battle.net users through our website.

  1. Sign in (73%)

    Sign in (73%)

  2. Online Play (14%)

    Online Play (14%)

  3. Game Crash (6%)

    Game Crash (6%)

  4. Matchmaking (4%)

    Matchmaking (4%)

  5. Glitches (4%)

    Glitches (4%)

Live Outage Map

The most recent Battle.net outage reports came from the following cities:

Loading map, please wait...
City Problem Type Report Time
United StatesBerwick Sign in
SpainValencia Sign in
United StatesSunrise Sign in
United StatesFlippin Online Play
SpainRota Game Crash
FranceAulnay-sous-Bois Sign in
Map Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Battle.net Issues Reports

Latest outage, problems and issue reports in social media:

  • MageStealth Stealth Mage (@MageStealth) reported

    @BlizzardCS Would be nice if you could at least let us know what the issue is so we don’t just keep hoping it’s up every hour to find out extended again

  • 3nfy 3nfy (@3nfy) reported

    @BlizzardCS Back in wrath servers were down for 24 hours because of a mail issue so you babies can stfu lol

  • pandears ANVIL (@pandears) reported

    @Vultorus @BlizzardCS It’s on the forums dude. Regardless of if you’re paying for a service, what gives you or anyone the right to treat these people like trash?

  • WeightDarkness The Weight of Darkness (@WeightDarkness) reported

    @BlizzardCS Make the servers live I don't give a **** what ur trying to fix I wanna play the game I pay a ******* sub to play

  • charity_gage Charity Gage (@charity_gage) reported

    @Kevin22961446 @BlizzardCS This maintenance is most likely trying to fix that bug, you do realize…?

  • Jakehare17 Jakehare (@Jakehare17) reported

    @BlizzardCS FIX THE ******* SERVERS WHAT ********!!!!

  • NightOfMistra Shawn M (@NightOfMistra) reported

    @BlizzardCS @BriMac0518 Take some responsibility and tell your customers why the subscription based service we pay for MONTHLY is down for 5+ hours. If you goofs would just make an official statement people wouldn't be left wondering.

  • TexasRedLFC Texas Red (@TexasRedLFC) reported

    @BlizzardCS Classic Mongoose Effect due to not pre-testing. Intro a something like Mage fix into the code...creates way more bad things in the environment. Because darn those mages for using their talents you gave them. Darn Capitalist mages. #BadMagesBad

  • JustenMacray Justen MacRay (@JustenMacray) reported

    @BlizzardCS are bunch of morons. Worse customer service out of any tech company. **** you and **** your bosses.

  • BernieOrBust10 JimR (@BernieOrBust10) reported

    @_NC_Vet_ @BlizzardCS Not the way it works at all since "Classic" isn't the same client, etc from back then... This was a fix (end) to boosting and exp boost. The boosting killshot fked something up.

  • YCantYouHurtMe WhyCantYouHurtMe (@YCantYouHurtMe) reported

    @DjKiXX @BigE2315 @BlizzardCS thats bullshit, they "fixed boosting" while the servers were up... so they need to shut servers down to change a bit of coding? thats a crock.

  • Devious_Pansexy 🌈🍖🔞🦦fruity english muffin🦦🔞 (@Devious_Pansexy) reported

    @Genji71660714 @SuckrToe @BlizzardCS No. It’s just so they have time to work on it, fix bugs, etc. I’m sure they’ll do something in overwatch 2

  • ItsAFingaPuppet Flying_Shithawks (@ItsAFingaPuppet) reported

    @BlizzardCS @BenTurman15 Out of curiosity...if yesterday's patch caused so many issues...why not just roll back to the prior patch version and hammer out this issue and re-deploy yesterday's patch when it's fixed? Seems backwards to prevent everyone from playing and you don't have a solution?

  • BernieOrBust10 JimR (@BernieOrBust10) reported

    @BlizzardCS If the issue is just PvE, just open the servers for pvpers aka the skilled players to do our thing and let the 🥱 PvE get fixed whenever...

  • BenjaminWallac3 Benjamin Wallace (@BenjaminWallac3) reported

    @BlizzardCS @karma12gaming WHAT ARE YOU WORKING ON? WHY ARE THE SERVERS DOWN FOR 7 HOURS? UNSCHEDULED?

  • Kevin22961446 Kevin (@Kevin22961446) reported

    @charity_gage @BlizzardCS It’s actually not… it’s about the character clone service lol chances are now the ZA bug won’t even be fixed let alone peoples lockouts that got burned.

  • pastasauce55 Alfredo Nunez (@pastasauce55) reported

    @BumblebeeFuming @BlizzardCS Blizzard doesn't understand customer service, even after so many years.

  • hyu_720 Connecting (@hyu_720) reported

    @BlizzardCS I mean, until a certain time means that should be your deadline. If you guys are not confident to fix it by the deadline, why not just start with a later time rather than extending 1 hour every hour?

  • BenjaminWallac3 Benjamin Wallace (@BenjaminWallac3) reported

    @BlizzardCS Today’s maintenance was scheduled to finalize the deprecation of the Classic Character Clone service that was announced back in May 7. Unfortunately, some technical issues were identified during these changes, which have caused us to extend our original estimates for maintenance

  • JacobSa74831883 Jacob Sandoval (@JacobSa74831883) reported

    @BlizzardCS I better get this time Refunded to my Account. This is beyond horrible service if not.

  • bratman6970 steve mcgil (@bratman6970) reported

    @BlizzardCS so we cannot play due to an error on your part to fix something that should have been fixed years ago

  • WeightDarkness The Weight of Darkness (@WeightDarkness) reported

    @BlizzardCS I don't care how broken your game is still #letusplay

  • wildstye Catbred (@wildstye) reported

    @BlizzardCS @karma12gaming BlizzCS: Okay we'll say 11:00, but it better be done on time. I'm sick of being roasted. BCS: Hello?? Are the servers ready? 12:00? You're sure??? Fine, I'll post 12:00. BCS: It's 1:30, I'm not posting anything anymore, the trust is broken.

  • BigChrisU Chris Ulland (@BigChrisU) reported

    @BlizzardCS @BlizzardCS if your gonna waste, goin on 7 hrs now of maintenance to fix ur screw up you might as well squeeze the prepatch in to. Or did u alrdy mark ur calander for another 8hrs to do that later?

  • Mwharrie95 Matt Wharrie (@Mwharrie95) reported

    @Arch1991 @Anthony81495375 @BlizzardCS 6hrs to fix a few dungeons only blizzard lmao

  • Oraclesdemise Daniel Watson (@Oraclesdemise) reported

    @BlizzardCS When people say we want transparency, this is the perfect time to practice it, not "sorry for the disruption, just keep waiting" actually tell us what the problem is and you wouldn't be flooded with angry comments because you refuse to tell us what happened.

  • WeightDarkness The Weight of Darkness (@WeightDarkness) reported

    @BlizzardCS You need to fire some people after this and get someone who can fix this **** twice as fast or lower the sub fee

  • joshmar38389362 KLGC ChiefnTV (@joshmar38389362) reported

    @BlizzardCS @uereh yeah 15 min before you guys shut the server down it was scheduled then 3 extensions 🤡

  • albatorwow Albatorwow (@albatorwow) reported

    @BlizzardCS ETA until you blame DDoS attacks?

  • Epicbeing_15 Epicbeing15 (@Epicbeing_15) reported

    @Mad_Tytan @zeroproofs @BlizzardCS Cry about it. That’ll fix it