1. Home
  2. Outages
  3. Blizzard Battle.net
  4. 17 Nov 2026

OutageTuesday 17 November 2026Ended 18 Nov, 01:36

Blizzard Battle.net outage on 17 November 2026

Problem reports about Blizzard Battle.net rose to outage level at 19:36 Central European time on Tuesday 17 November 2026 and stayed there for 6 h.

They peaked at 199 reports in 15 minutes at 00:09, about 40 times the usual level for that time of day, and 578 reports came in while the outage lasted.

Reports reached outage level in 2 countries, the US, Sweden.

12 other services had an outage spike at the same time.

Is Blizzard Battle.net down right now? 6 outages of Blizzard Battle.net

Started
19:36
Tue 17 Nov, Central European time
At outage level
6 h
Ended 01:36 on 18 Nov
Busiest 15 minutes
199
reports, at 00:09
Reports during the outage
578
Peak about 40× the usual level
Timeline

Reports from Tue 13:30 to Wed 06:45

One bar per 15 minutes, Central European time. Red bars are the outage; the dashed line is what a usual day sees at that time.

Problem reports about Blizzard Battle.net rose to outage level at 19:36 Central European time on Tuesday 17 November 2026 and stayed there for 6 h. They peaked at 199 reports in 15 minutes at 00:09, about 40 times the usual level for that time of day, and 578 reports came in while the outage lasted. Reports reached outage level in 2 countries, the US, Sweden. 12 other services had an outage spike at the same time.
Around the world

Where people reported it that day

Each country's reports on 17 November, against the usual level there. Outage means reports stayed at outage level for half an hour or more; above usual, for an hour or more.

CountryThat dayReports
The USOutage758
SwedenOutage78
The UKNormal77
GermanyNormal73
CanadaNormal56
FranceNormal40
The NetherlandsNormal30
SpainNormal25
AustraliaNormal21
DenmarkNormal20
FinlandNormal20
NorwayNormal17
Same time

Other services with an outage at the same time

Their reports also reached outage level while Blizzard Battle.net's did. Many services failing together can point to a shared cause, such as a network or cloud provider, but reports alone cannot show it.

More

Blizzard Battle.net: live status and other outages

Check whether Blizzard Battle.net is down right now: the live page shows the last 24 hours and fixes to try. This site keeps a page for each of Blizzard Battle.net's 6 outages since the archive began.

Earlier: 12 Nov 2026 November 2026 outage report All recent outages

Embed

Put this outage in an article

Copy a frame with the chart and numbers above, or an image of the same card for places that do not allow frames, such as newsletters. Both link back to this page. More for journalists.

Blizzard Battle.net outage on 17 November 2026: problem reports over time

<iframe src="https://isitdownrightnow.app/embed/battle-net/2026-11-17/" title="Blizzard Battle.net outage on 17 November 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/battle-net/outages/2026-11-17/">Blizzard Battle.net outage on 17 November 2026</a> from IsItDownRightNow.app</p>Frame: the chart and numbers, as a small card
<a href="https://isitdownrightnow.app/services/battle-net/outages/2026-11-17/"><img src="https://isitdownrightnow.app/share/battle-net/2026-11-17.png" alt="Blizzard Battle.net outage on 17 November 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture
[![Blizzard Battle.net outage on 17 November 2026](https://isitdownrightnow.app/share/battle-net/2026-11-17.png)](https://isitdownrightnow.app/services/battle-net/outages/2026-11-17/)Markdown: the image, for README files and forums

Where these numbers come from

The numbers are problem reports that users sent to a public outage-reporting service, counted in 15-minute windows and kept as this site's live page showed them. A spike counts as an outage when reports are more than twice the usual level and far above the day's average. Reports show that many people had trouble at the same time, not what caused it; the service's own status page is the place for that.