Gaming Platformsbattle.net(opens in a new tab)
Battle.net is answering, but slowly.
Degraded
Since
3.9 s
From the latest check
100%
7 days 100% · 30 days 100%
every minute
Last check
The status at the top of this page is refreshed every time we check Battle.net. It says whether Battle.net is up, slow or down, and whether many people are reporting problems.
What our checks measured. Times are in UTC.
182 checks · 0 failed · average 3.9 s
If our checks pass but you cannot connect, the problem is probably on your side: try another network or device, and restart the app or browser. If our checks fail, or many people report problems at the same time, Battle.net itself has an issue.
Every minute, our servers request battle.net and measure how long it takes to answer. A failed check is repeated at once, and an outage is only declared after several failures in a row and after we confirm that our own connection is healthy.
Yes. When people report problems with Battle.net, the user reports section of this page shows the cities they report from. A city appears once at least 3 people reported from it in the last 24 hours, and positions are approximate. With no reports, the map stays empty.
Press “I have a problem” at the top of this page and choose what is wrong. It takes a few seconds, needs no account, and each person can report once every 10 minutes.
A failed check is retried at once. A service is only reported as down after repeated failures.
Outages of Battle.net, newest first. Each says whether our checks or its users found it.
No incidents recorded for Battle.net.
One bar per day. The colour is the worst status of that day.
100% uptime
No reports in the last 24 hours. If Battle.net is not working for you, use “I have a problem” to tell others.