- Home
- Outages
- World of Warcraft
- 9 Nov 2026
OutageMonday 9 November 2026Ended 10 Nov, 04:24
World of Warcraft outage on 9 November 2026
Problem reports about World of Warcraft rose to outage level at 08:27 Central European time on Monday 9 November 2026, in 3 separate spikes over 19 h 57 min (8 h 44 min at outage level in all).
They peaked at 4,310 reports in 15 minutes at 22:32, about 2,155 times the usual level for that time of day, and 12,322 reports came in while the outage lasted.
Reports reached outage level in 24 countries, the US, Germany, the UK, Sweden and more.
12 other services had an outage spike at the same time.
Is World of Warcraft down right now? 10 outages of World of Warcraft
Reports from Mon 02:15 to Tue 10:30
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.
- Outage
08:27–10:18Lasted 1 h 51 min708peak reports
- Outage
20:34–21:17Lasted 43 min1,087peak reports
- Outage
22:14–04:24Lasted 6 h 10 min4,310peak reports
Where people reported it that day
Each country's reports on 9 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.
| Country | That day | Reports |
|---|---|---|
| The US | Outage | 11,620 |
| Germany | Outage | 6,591 |
| The UK | Outage | 5,525 |
| Sweden | Outage | 2,814 |
| France | Outage | 2,659 |
| The Netherlands | Outage | 1,765 |
| Norway | Outage | 1,652 |
| Poland | Outage | 1,529 |
| Canada | Outage | 1,426 |
| Denmark | Outage | 1,411 |
| Czechia | Outage | 1,078 |
| Belgium | Outage | 691 |
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.
- Outage
09:52–21:434,734peak reports
- Outage
16:38–Tue 04:033,713peak reports
- Outage
10:20–14:382,438peak reports
- Outage
15:53–20:221,274peak reports
- Outage
15:14–Tue 01:051,160peak reports
- Outage
18:54–19:371,111peak reports
- Outage
17:58–23:57994peak reports
- Outage
20:46–23:36691peak reports
- Outage
09:35–11:14619peak reports
- Outage
12:19–19:29565peak reports
- Outage
20:34–21:12469peak reports
- Outage
Tue 00:12–Tue 01:01438peak reports
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 10 outages since the archive began.
Earlier: 8 Nov 2026 Later: 10 Nov 2026 November 2026 outage report All recent outages
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.

<iframe src="https://isitdownrightnow.app/embed/world-of-warcraft/2026-11-09/" title="World of Warcraft outage on 9 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-09/">World of Warcraft outage on 9 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-09/"><img src="https://isitdownrightnow.app/share/world-of-warcraft/2026-11-09.png" alt="World of Warcraft outage on 9 November 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture[](https://isitdownrightnow.app/services/world-of-warcraft/outages/2026-11-09/)Markdown: the image, for README files and forumsWhere 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.