Is Battle.net (Blizzard) down?
Operationalchecked 1 minute ago
We reached Battle.net (Blizzard) from all 10 regions we check.
As of Oct 5, 2026, 8:16 PM UTC, Battle.net (Blizzard) answered RealUptime's probes in all 10 regions that returned a reading.
No outage recorded in the 46 days we have measured Battle.net (Blizzard) (since Aug 20, 2026).
Email me the next time we see Battle.net (Blizzard) go down
Battle.net (Blizzard) publishes no status feed we can read, so the only independent reading here is ours on the left.
Battle.net (Blizzard) response time, by region
Is it Battle.net (Blizzard), or is it you?
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Battle.net (Blizzard) -- it cannot diagnose Battle.net (Blizzard)'s own systems.
What we measured, function by function
Battle.net (Blizzard) answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
- AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 1136msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Battle.net (Blizzard) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestOperationallatency: 722msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Battle.net (Blizzard) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralOperationallatency: 263msstatus code: 200checked: Oct 5, 2026, 8:14 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Battle.net (Blizzard) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaOperationallatency: 840msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Battle.net (Blizzard) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaOperationallatency: 1120msstatus code: 200checked: Oct 5, 2026, 8:16 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Battle.net (Blizzard) normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 278msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Battle.net (Blizzard) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKOperationallatency: 449msstatus code: 200checked: Oct 5, 2026, 8:07 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Battle.net (Blizzard) normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 934msstatus code: 200checked: Oct 5, 2026, 8:15 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Battle.net (Blizzard) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaOperationallatency: 909msstatus code: 200checked: Oct 5, 2026, 8:15 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Battle.net (Blizzard) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaOperationallatency: 1601msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Battle.net (Blizzard) normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Battle.net (Blizzard), counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Battle.net (Blizzard) yet, which is not evidence that nothing is wrong.
Recent outages
No outages on record yet for Battle.net (Blizzard).
measured entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Battle.net (Blizzard) since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Battle.net (Blizzard) covering any window you pick, with our measurements and Battle.net (Blizzard)'s own claim at the time, side by side.
Full availability history for Battle.net (Blizzard): 90-day availability by region, month-by-month uptime, and every incident on record.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/battle-net)<a href="https://realuptime.io/outages/battle-net"><img src="https://realuptime.io/outages/battle-net/badge.svg?days=30" alt="Battle.net (Blizzard) uptime measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What Battle.net (Blizzard)'s SLA implies, from our measurement
At or above your target
We measured none of downtime for Battle.net (Blizzard) over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.
By our measurement there is no shortfall to claim for this period.
This is computed from our own probe measurements, not from Battle.net (Blizzard)'s SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.