1. Home
  2. Outages
  3. World of Warcraft
  4. 4 Nov 2026

OutageWednesday 4 November 2026Ended 5 Nov, 02:37

World of Warcraft outage on 4 November 2026

Problem reports about World of Warcraft rose to outage level at 22:07 Central European time on Wednesday 4 November 2026 and stayed there for 4 h 30 min.

They peaked at 376 reports in 15 minutes at 00:03, about 188 times the usual level for that time of day, and 810 reports came in while the outage lasted.

Reports reached outage level in the US.

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

Is World of Warcraft down right now? 4 outages of World of Warcraft

Started
22:07
Wed 4 Nov, Central European time
At outage level
4 h 30 min
Ended 02:37 on 5 Nov
Busiest 15 minutes
376
reports, at 00:03
Reports during the outage
810
Peak about 188× the usual level
Timeline

Reports from Wed 16:00 to Thu 06:00

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 World of Warcraft rose to outage level at 22:07 Central European time on Wednesday 4 November 2026 and stayed there for 4 h 30 min. They peaked at 376 reports in 15 minutes at 00:03, about 188 times the usual level for that time of day, and 810 reports came in while the outage lasted. Reports reached outage level in the US. 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 4 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 USOutage311
The UKNormal38
CanadaNormal35
NorwayNormal35
GermanyNormal32
SwedenNormal24
DenmarkNormal23
AustraliaNormal19
The NetherlandsNormal19
FranceNormal11
PolandNormal9
CzechiaNormal8
Same time

Other services with an outage at the same time

Their reports also reached outage level while World of Warcraft'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

World of Warcraft: live status and other outages

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

Earlier: 29 Oct 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.

World of Warcraft outage on 4 November 2026: problem reports over time

<iframe src="https://isitdownrightnow.app/embed/world-of-warcraft/2026-11-04/" title="World of Warcraft outage on 4 November 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/world-of-warcraft/outages/2026-11-04/">World of Warcraft outage on 4 November 2026</a> from IsItDownRightNow.app</p>Frame: the chart and numbers, as a small card
<a href="https://isitdownrightnow.app/services/world-of-warcraft/outages/2026-11-04/"><img src="https://isitdownrightnow.app/share/world-of-warcraft/2026-11-04.png" alt="World of Warcraft outage on 4 November 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture
[![World of Warcraft outage on 4 November 2026](https://isitdownrightnow.app/share/world-of-warcraft/2026-11-04.png)](https://isitdownrightnow.app/services/world-of-warcraft/outages/2026-11-04/)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.