Timesaver

Is WoW Forever Down? Mostly Back After the Nov 12 DDoS That Hit All Blizzard Games; Some Players Still Report Disconnects

Sam Okonkwo
Sam Okonkwo
WoW Forever launch login queue: Login Servers are Full, position in queue 1041, estimated time 4 minutes

Quick answer: Mostly back up, as of 04:05 UTC on Nov 12. A DDoS hit all Blizzard games from about 00:53 UTC; Blizzard Customer Support confirmed it at 01:23 UTC and said it was mitigating it. Vrakthris wrote: "we have been experiencing a DDOS for all games. We are in the process of mitigating it, so things should be improving." Players report getting back in from about 01:52 UTC (thread), and the big disconnect threads stopped getting new posts by about 02:30 UTC. A few players still report random disconnects at 03:46 UTC. Blizzard has posted no all-clear and no ETA. If you're stuck at "Logging in to game server", players say restarting the game or PC and retrying got them in, sometimes only after a few tries.

Last verified: Nov 12, 2026, 04:05 UTC. Every entry below is either a Blizzard source or labeled as a player report. We don't publish queue predictions or guessed fix times.

Game closing on you rather than failing to connect? That is a client crash, not an outage. See WoW Forever crash fixes: 0xC00000E5, loading-screen crashes and black screens.

All WoW Forever prices · How delivery works in WoW ForeverWoW Forever Power LevelingWoW Forever GoldWoW Forever PvP Rank & HonorWoW Forever Raids, Dungeons & Pre-Raid GearWoW Forever ProfessionsWoW Forever Reputation, Riding & Class QuestsWoW Forever account safety

WoW Forever prices today

  • Gold: from $8.75 (5 gold), within 30 minutes; $1.75 per gold, No account access, US, EU
  • Bags: from $2.84 (4 × Small Silk Pack, 10 slots), 2 hours (estimated), Piloted, US, EU
  • Power Leveling: from $509.28 (1–60), within 12 days; from $57.66 per level, Piloted / Self-play Remote, US, EU

all WoW Forever prices · gold price today (daily tracker)

Gold

WoW Forever - Gold

Get Gold

4.9· 2k+ ordersSee all options
Startingfrom $8.75 (5 gold)Buy now

Update log

  • Updated Nov 12, 04:05 UTC: a DDoS on all Blizzard games disconnects WoW Forever players from about 00:53 UTC; Blizzard Customer Support confirms it and says it is mitigating; players report getting back in from about 01:52 UTC. At 00:53 UTC US players opened "Disconnected and can't get back in" (106 posts by 02:27 UTC) and "DC'd again, 5th time in 4 days this has happened" (61 posts): disconnected mid-play, a login queue on reconnect, then stuck at "Logging in to game server". Retail players report the same in "Havin trouble logging into Forever and Retail today". From 01:23 UTC players in both big threads say the Battle.net app shows a warning that Blizzard is being DDoSed; we didn't see the banner ourselves. At 01:23 UTC Blizzard Customer Support's Vrakthris replied to a player: "we have been experiencing a DDOS for all games. We are in the process of mitigating it, so things should be improving." One player says they got back in at 01:52 UTC, another at 01:54 UTC wrote "it already let me back in" (thread). Earlier, at 01:10 UTC, one player in that thread said they restarted their PC, ran Scan and Repair, "had the issue a couple more times then finally got in". Both big threads stop getting new posts at 02:27 UTC. At 03:46 UTC two new one-post threads still report random disconnects (1, 2); we can't tell whether that is the attack or the disconnects players have reported all week. Blizzard ETA: no all-clear and no ETA from Blizzard as of 04:05 UTC. Lost items or gold: Kaivax's Nov 11 hotfix notes (posted 00:48 UTC Nov 12) say "The Item Restoration service has been disabled while we investigate and address a critical bug." At 02:11 UTC Vrakthris told a player who says the crash and rollback earlier this week cost them gold that support generally can't compensate or restore after a crash or rollback, and pointed them to the Forever Discussion forum to ask the developers (reply). Routing: the AU "Preferred Account Location" thread reached 173 posts at 03:58 UTC with no staff reply (thread).
  • Updated Nov 11, 05:10 UTC: some EU players still couldn't log in at 04:51 UTC after the maintenance; downloading the client update fixed it for one; Blizzard posts the Nov 10 hotfix notes. Our 03:12 UTC entry said EU was back up, and some players were in from 02:43 UTC, but not all of them. In "How long will the maintanance be?" (12 posts, 03:14 to 04:51 UTC) one player wrote at 03:37 UTC that they still couldn't log in and "it says no realm available", and a second answered "Yep, same." at 03:51 UTC. At 03:56 UTC another player said "It's up and running", but the first was still locked out at 03:58 UTC, and at 04:30 UTC the second wrote "It has been 2.5 hours of a 1 hour long shutdown, still waiting". At 04:44 UTC the first player said some friends were already in game. At 04:48 UTC the second player wrote: "I just logged in. Exit, download update, launch… profit." The first player said at 04:51 UTC they couldn't see an update and would restart their PC. That fits what Blizzard Customer Support told a US player at 23:52 UTC Nov 10: the "No realms" error WOW51900309 "sounds like" a missing client update (reply). Hotfix notes: at 03:27 UTC Kaivax added a November 10 section to the WoW: Forever hotfix thread. Under Auction House, "With realm restarts", it lowers the Auction House minimum deposit to 1 copper (was 1 silver), fixes unread mail all showing as from "Stormwind Auction House", and fixes some mail arriving in about 2 minutes instead of the intended 60. The notes also list class changes, among them Enhancement Shaman (Stormstrike to 100% weapon damage on an 8-second cooldown, was 150% and 6 seconds), Hunter pets corrected to 115% health (was 150% by mistake), and about 15% more health for the Imp, Voidwalker, Succubus and Incubus. At 04:43 UTC an EU player wrote that "the changes aren't live on the EU servers right now", still hitting with Stormstrike "on a 6 sec cd for 150% damage like twenty minutes ago" (thread); two other EU players said the same at 04:01 UTC (thread) and 04:32 UTC (thread), and Blizzard hasn't said when each region gets them. On the US forums the newest threads from 03:00 to 05:00 UTC are about class changes, faction balance and the PvP creation lock; we found no new outage threads, only single-post reports of group disconnects from Brazil (thread) and stutters (thread). An r/classicwow post at 04:59 UTC is titled "Cannot resurrect, spirit healer not present, and unstuck service stuck on loading" (post); Reddit didn't load from our checker, so we've only seen the title, and it's one report. The wrong-region routing thread (Preferred Account Location) has 121 posts, newest 04:57 UTC, and still no staff reply. No ETA from Blizzard for the routing issue or the rollback losses as of 05:10 UTC.
  • Updated Nov 11, 03:12 UTC: EU back up after the weekly maintenance (about 02:00 to 02:43 UTC), players report; US up; Blizzard restores shaman totems lost in the Nov 9 crash. EU players opened threads about downtime from 02:04 UTC ("Is this maintenance now?", "Impromptu daily maintenance for an hour or more is very unprofessional", 23 posts by 03:04 UTC). Players there say this one is the regular weekly maintenance, which in Europe starts at 3:00 a.m. CET on Wednesdays, and one says the Battle.net app notice gave "1 hours downtime". Several say they saw no notice; others say the app only shows EU maintenance banners with its language set to English (UK) rather than English (US), and one player who plays through GeForce NOW says the banners never showed there (thread). Many in these threads also complain about near-daily unannounced downtime in the EU evening during launch week. We found no Blizzard forum post about tonight's EU maintenance and no end time. At 02:43 UTC a player in the second thread wrote "P.S servers are up." and at 02:48 UTC "servers are back up so i am going to play" (thread). One player was still asking "When will the servers be up!!" at 03:04 UTC. At 01:10 UTC Kaivax replied in "Bugged/missing shaman totems since Monday's server chaos": "We have just deployed a fix for this to all regions. Shamans who lost a totem due to the crash should find it restored to their bag." Shamans online at the time need bag space and a logout to get them. It is the first Blizzard post we've seen that refers to the Nov 9 crash. It doesn't mention trained skills, gold or quest items lost in the rollback. On the US forums the newest threads from 23:00 UTC Nov 10 to 03:10 UTC Nov 11 are mostly about the Horde PvP creation lock, layering and dungeon XP; we found no new outage threads, only one player's report of heavy lag and characters running in place at 00:08 UTC (thread). We'll update if more EU players report trouble logging in.
  • Updated Nov 10, 21:05 UTC: up after the Tuesday maintenance; a morning disconnect wave and WOW51900309 logins afterwards, no Blizzard post. From 09:23 UTC US players reported a new wave of disconnects, hard lag and logins stuck on "Logging in to game server" ("And servers are down again", 27 posts; "Blizzard again"). Some say only they and a few others were hit while everyone else kept playing. At 09:41 UTC a player there wrote "It's back up, now"; one says cancelling the stuck login and trying again got them in, another had to log out of the Battle.net app and back in. Others were still stuck at 09:45 and 09:52 UTC. In "World server down - all my friends playing?" (11 posts, 09:59 to 11:22 UTC) players report a "character name already exists" error and then "world server is down" when relogging, and one reports error BLZ51914400. Maintenance: a player in Latin America posting on the US forums puts today's scheduled maintenance at 15:00 to 16:00 UTC (thread). At 15:58 UTC a player said there was "a giant banner on the launcher" and at 16:00 UTC another wrote "Server is back up" (thread); we couldn't see the launcher notice ourselves. After the maintenance: from 17:08 UTC players on the US forums (one on an Oceanic server) report "No realms are currently available" with error WOW51900309 while friends are online and the status page shows green (thread, 10 posts). At 19:16 and 19:22 UTC two players say closing the game client, restarting the PC and letting the Battle.net app download the update fixed it; at 20:53 UTC another says the update went through and the error stayed. A volunteer MVP there (not Blizzard staff) says a ticket is unlikely to help, since the server issue should clear first. One player reports about 2,400 ms latency and a hang before character select after the maintenance (thread). Kaivax wrote on Nov 6 that class tuning for Hunter pets, Warlock Voidwalkers, Affliction Warlocks and Enhancement Shamans was planned for Nov 10 (post); as of 21:05 UTC Blizzard hasn't posted that it is live, and the Blue Tracker's newest WoW: Forever post is still the Nov 9 hotfix section at 04:23 UTC. Blizzard has no post about the morning wave, the maintenance or the Nov 9 rollback, and no staff reply in these threads. From about 20:40 to 21:05 UTC the newest US WoW: Forever and EU forum threads include no new outage reports. No ETA from Blizzard for the rollback or the wrong-region routing as of 21:05 UTC.
  • Updated Nov 10, 06:15 UTC: still up after a short US disconnect wave around 00:40 UTC; Blizzard posted hotfixes but nothing about the rollback. From about 00:40 to 01:00 UTC US players opened several threads reporting disconnects, lag and logins stuck on "Logging in to game server" ("Why are the servers in worse shape NOW than launch?", 38 posts; "Disconnects happen often and cannot login at the moment"). From about 01:05 to 06:15 UTC the newest US and EU threads include no new outage or login-failure reports; they are about classes, PvP faction balance and quests. At 06:10 UTC one US player reported the game "again desyncing and lagging" ("Freezing and Desync"); we found no other reports yet. At 04:23 UTC community manager Kaivax added a November 9 section to the WoW: Forever hotfix thread: class fixes, the 50% dungeon kill experience increase, dungeon fixes (Blackfathom Deeps, Blackrock Depths, Stratholme and others) and, under World, "Lowered the population of players in various zones where there was significant congestion", with a developer note that the change is bigger on the PvP ruleset. At 02:05 UTC Kaivax also posted PvP Faction Balance Updates, saying it will become "increasingly difficult to create characters on the more populous faction in each region", currently Horde on North American PvP rulesets and Alliance on EU Roleplay-PvP. None of Blizzard's posts since the crash, including Kaivax's follow-up replies in the faction thread, mention the Nov 9 crash, the emergency maintenance or the rollback, and we found no staff reply in the rollback threads. Players are still adding to them: at 05:23 UTC a US player wrote in "Server reset rolled back my character skills but took my gold" that the rollback "completely cleaned me out", and at 05:36 UTC an EU player added to the EU skills thread. Smaller reports that players link to the restart, each from one or two forum threads so far: Hunter Arcane Shot and Aimed Shot no longer critting (EU) and a flickering minimap (US). The wrong-region ping problem is still open: the Preferred Account Location thread reached 87 posts with no staff reply, and at 06:03 UTC an NA-East player in a second thread says they were set to Australia without ever travelling. Reddit didn't load from our checker this run. No ETA from Blizzard for the rollback or the routing issue as of 06:15 UTC.
  • Updated Nov 10, 00:10 UTC: servers back up since about 22:42 UTC Nov 9; players report trained skills and gold lost in the rollback. At 22:42 UTC a US player opened "Game is back up!"; a minute later another player there was stuck on "Logging in to game server" and says relaunching the client cleared it, while one still saw the maintenance banner. EU players posted "And we are back" at 22:42 UTC in the 169-post EU thread, and the big US crash thread (252 posts) is now titled "{SERVERS BACK UP}". From 22:45 UTC to 00:03 UTC the newest US and EU forum threads include no new outage or login reports. Instead, players report what the rollback took, in both regions: in the EU thread "Rollback issue" (13 posts from 22:55 UTC) players say spells trained before the shutdown disappeared, some from their action bars, while the gold stayed spent, with losses of about 2 to 8 gold each; one says they re-trained, got rolled back a second time and weren't refunded. Others there say Blacksmithing and Tailoring skill-ups were reset along with the materials and the gold for recipes. The same reports appear in EU 641143, US 2408622 and US 2408568. A US player says the maintenance removed quest items looted one to two hours earlier, such as a Zul'Farrak quest dropping from 20/20 to 19/20 (thread). A player in the US crash thread describes the same split at 22:41 UTC: the materials he crafted with stayed used, but 35 profession skill points were gone. Single EU threads also report a rolled-back PvP honor rank (thread) and reset macros and graphics settings. Blizzard has no forum or Blue Tracker post about the shutdown, its cause or the rollback as of 00:10 UTC (newest WoW: Forever blue post is still Kaivax's Nov 8 dungeon XP hotfix), and no staff reply in these threads. Blizzard hasn't said whether lost gold, skills or items will be restored.
  • Updated Nov 9, 22:35 UTC: servers down for emergency maintenance in the US and EU, rollbacks reported, no ETA. At 21:30 UTC a US player opened "Perfect, another server crash" about being stuck on "Retrieving character list"; it passed 230 posts in about an hour. Players there were disconnected mid-quest, in dungeons and on flight paths from 21:31 UTC, while some guildmates stayed online at first. Some got "Character not found" or "A character with that name already exists" when logging back in (a volunteer in the thread explains that the second one means the server still thinks your character is online). At 21:49 UTC a player in that thread quoted the in-game message: "[SERVER] Sorry, we have to take the servers down briefly. A few mischievous murlocs have invaded the server room, and they're refusing to stop mrrglglgl-ing at everything." EU players report the same GM message. Players say a 15-minute shutdown countdown followed, and that the servers went down several minutes before it ended (one EU player says the disconnect came after 4 minutes). From 21:50 UTC players in both regions report an emergency maintenance notice in the Battle.net app. An EU player quotes it at 21:55 UTC (thread): "We will be performing emergency maintenance and the game will be unavailable during this time. Thank you for your patience and apologies for any inconvenience caused." We couldn't see the launcher notice ourselves. Rollback: from 21:48 UTC EU players report logging back in earlier in time ("Roll BACK!", 26 posts): one lost about 10 minutes of questing, others say they lost a dungeon's end boss loot and quest items, trained skills (several say the gold they paid stayed spent), and crafting materials spent on skill-ups. US threads report the same (1, 2). Blizzard hasn't said whether anything will be restored. One player says the realm status check has recently shown servers as up when they weren't (thread), though an EU player says it was later switched to offline. Players have read the murloc message as a sign of a hack; Blizzard hasn't said what caused the shutdown, and there's no evidence for that. One EU player says the maintenance is one hour; we found no Blizzard source for a duration. Progress as of 22:33 UTC: from 22:15 UTC players reach the ruleset screen, but every ruleset shows as "currently unavailable" (US, EU). Blizzard has no forum or Blue Tracker post about the shutdown as of 22:35 UTC (newest WoW: Forever blue post is still Kaivax's Nov 8 dungeon XP hotfix), and no staff reply in these threads. EU players ask whether the hotfix maintenance planned for the early hours of Nov 10 still goes ahead; Blizzard hasn't said. No ETA from Blizzard as of 22:35 UTC.
  • Updated Nov 9, 21:05 UTC: new evening disconnects in EU, lag spikes and disconnects in the US, no Blizzard post. At 19:42 UTC an EU player opened "Logging in to game server": kicked from the game, then unable to reach the servers, while some of their friends were "still online". Nine more replies followed by 19:47 UTC, most of them "same here", and a separate thread, "Kicked out of game and cant login", opened at 19:44 UTC. One player says it happened to them that morning in the Stockade too, first alone and then to the whole group. At 19:47 UTC a player wrote that after a minute on "retrieving character list" they got in. The thread then went quiet until one complaint at 20:59 UTC, and we found no new EU outage threads after 19:44 UTC. On the US forums, "Disconnects WoW Forever" (opened 14:40 UTC, 6 posts) reports sudden disconnects, and a second player says they can stay in for a few seconds at most; the opening player says disabling addons, reinstalling, removing the WTF and Interface folders and flushing DNS didn't help. At 17:24 UTC another player says latency spiked and they couldn't move, and at 17:38 UTC a player says they'd been stuck on "logging into game server" then disconnected since 7:00 a.m. PST (15:00 UTC). In the "weird latency" thread a player at 17:26 UTC describes the same pattern: fine for an hour, then a big latency spike and a disconnect, with chat still working. At 19:58 UTC a player opened "WoW Forever Disconnect and Can not login after" (disconnects while running, on flight paths and in combat, after removing addons and a scan and repair), and at 20:59 UTC another player in it says they've had lag-lock and disconnects since the day before. At 20:59 UTC a US PvP player opened "Huge lag spikes - chars running in place - NPCs hanging - delayed chats - Disconnects", saying it started about an hour earlier, comes in bursts and only clears for a while after fully closing the game. Each new US disconnect thread has 1 to 6 posts, so this looks like scattered disconnects rather than a full outage, and other players keep posting about classes and layers at the same time. Not everyone thinks it's the servers: a volunteer MVP in the first US thread says they're "not convinced it is a server issue", the 20:59 UTC poster in the disconnect thread thinks their issue is "client side", and the PvP poster says their latency is stable and suspects their local connection. Blizzard has no post about it as of 21:05 UTC: the newest WoW: Forever blue post on the US and EU Blue Tracker is still Kaivax's Nov 8 dungeon XP hotfix, and none of these threads has a staff reply. The wrong-region ping problem is still open: the Preferred Account Location thread reached 78 posts (newest 20:58 UTC) with no staff reply, and one player there says three support tickets got what read like automated answers telling them to change a setting that was already correct. In the latency thread one NA player says at 16:19 UTC that leaving their Oceanic guild, then logging into a new character and back to the old one, kept the old one on NA-East layers at 30 ms; another says the new-character trick didn't work for them. A r/wow post about disconnects on Tichondrius is about a Retail realm, not Forever. Reddit and Downdetector didn't load from our checker this run, and we couldn't check @BlizzardCS. No ETA from Blizzard as of 21:05 UTC.
  • Updated Nov 9, 09:43 UTC: Blizzard confirms the login issue is fixed. At 09:37 UTC Blizzard staff member Yryadorne replied in the EU thread "Can't log in": "We encountered some issues with our logins this morning, however it should have been resolved pretty quickly, and everything's back to normal (as of 40+ minutes ago)". For anyone still unable to log in, the reply links Blizzard's Connection Troubleshooting guide. This is the first Blizzard comment on the 07:46 UTC wave. It is a forum reply, not an outage post, and it doesn't appear on the Blue Tracker yet. Blizzard gave no ETA during the wave.
  • Updated Nov 9, 09:35 UTC: servers back up, the wave ended around 08:10 UTC. In the US WoW: Forever forum, players report getting back in from 08:06 UTC: "Just logged, seems to be alive" (thread), and at 08:10 UTC "I'm back in… dead, but in" (thread). At 08:13 UTC a player in a Retail General Discussion thread said the world server "went down. It's back up" with 22 ms ping (thread). The busiest US disconnect threads got their last replies between 08:08 and 08:14 UTC, and from then to 09:32 UTC the newest US and EU forum threads are about classes, layers and quests, not outages. The exception: an EU thread "Can't log in" (08:54 UTC) where two players are still stuck on "Connecting" at 09:32 UTC. One of them, stuck since about 08:00 UTC during the wave, says their friends are online, the Battle.net launcher shows their Forever account as "??" after clearing the cache, and Retail won't log in either; the other says their account doesn't show "??". If that's you, see "Is it my account or is WoW Forever down for everyone?" below. As of 09:35 UTC Blizzard had not posted about the 07:46 UTC wave: no outage post on the US or EU forums or the Blue Tracker, and no staff reply in these threads (Blizzard replied two minutes later, see the 09:43 entry). Its newest WoW: Forever blue post is still Kaivax's Nov 8 dungeon XP hotfix. We couldn't open Reddit from our checker this run.
  • Updated Nov 9, 08:05 UTC: disconnects and login failures in EU and US. At 07:46 UTC an EU player opened "WoW:Forever Lag!", and within 12 minutes it had 20 posts: players report being disconnected, then a full login queue, then getting stuck "logging in to server" until they're disconnected again. One player says their character was mid-craft when the disconnect hit. At 07:51 UTC one EU player says they're back online, but the "Login servers are full?" thread (07:49 UTC) says players get disconnected again after getting in, and at 08:00 UTC a new thread, "Servers off?", says a player is stuck on "Logging in to the game servers". The last EU outage post we saw was at 08:01 UTC. One EU player says Battle.net itself first showed a 500 error. A r/classicwow post titled "EU servers crashed rip" went up at 07:46 UTC. On the US forums, the "12.1.5 Server Connection issues" thread (opened 07:48 UTC, in Retail General Discussion) and eight more threads opened by 08:04 UTC report chain disconnects, with new reports still arriving at 08:04 UTC. A player from Australia says at 07:57 UTC the servers "went boom". Players say it hits PvP, PvE (Normal) and Roleplay-PvP rulesets. Two US players say they then couldn't log in to Retail either. Before disconnecting, one US player says NPCs and mobs vanished or stopped moving. Another thread title says Riverglades crashes clients on at least one layer; its replies only describe disconnects. As of 08:05 UTC Blizzard has no outage post on the US or EU forums or the Blue Tracker (newest WoW: Forever blue post is still Kaivax's Nov 8 dungeon XP hotfix), and no staff reply in any of these threads. We couldn't open Reddit or @BlizzardCS from our checker this run. No ETA from Blizzard as of 08:05 UTC.
  • Updated Nov 8, 21:10 UTC: still not down. Blizzard has no outage or maintenance post on the US or EU forums or the Blue Tracker, and neither forum's newest-topics list has an outage thread. One new WoW: Forever staff post: at 19:47 UTC Kaivax posted that "at about 11:05 PST today, we deployed a hotfix that increased kill experience in dungeons by 50%" (11:05 PST is 19:05 UTC). The post doesn't mention a restart. It doesn't mention latency either. The Known Issues thread is still unedited since 22:07 UTC Nov 5. The ping problem is still open and has widened, going by player reports: the Preferred Account Location thread went from 42 to 52 posts (newest 20:45 UTC), with no staff reply. At 16:41 UTC one player wrote they were "assigned to the right location" and still see about 190 ms World latency against 13 ms Home, and that "this wasn't the case as of yesterday". At 16:57 UTC the same player says Retail gives them 12 ms on both. At 16:42 UTC another player, defaulted correctly to US-East, reports Home latency 40 ms above World, the same on a new character. At 17:39 UTC an Oceanic player says they've been stuck at about 200 ms since launch on every character, after switching the setting to AU an hour after launch. At 18:45 UTC a player says their support ticket is "still open and pending". A new thread at 20:18 UTC from Florida (NA-East) reports World latency of 190-204 ms on every character, new ones included, with normal Home latency. In another thread, one player says at 16:56 UTC that World latency starts under 100 ms and climbs past 1,200 ms within minutes, with freezing. That's a single report. Reddit and Downdetector didn't load from our checker this run, so this entry uses Blizzard's forums only. No ETA from Blizzard as of 21:10 UTC.
  • Updated Nov 8, 08:10 UTC: still not down. Blizzard has no outage or maintenance post on the US or EU forums or the Blue Tracker (newest WoW: Forever staff post is still the Nov 6 hotfixes, 01:07 UTC Nov 7), and neither forum's newest-topics list has an outage thread. The wrong-region ping problem is still open and growing: the Preferred Account Location thread went from 22 to 42 posts since our last update (about 420 views, newest post 07:54 UTC), with no staff reply. What's new in it, all player reports: the setting fixes new characters, not existing ones. One player wrote at 03:47 UTC that changing Preferred Account Location "does work…for newly created characters", and existing ones stay "stuck". At 07:22 UTC another tested it: a new character landed on a US server while the old one stayed on the Australian one, and mail still works between them. Not everyone gets that result: at 07:09 UTC an Oceanic player says even new characters now get 220 ms. Leaving the guild worked again: at 06:48 UTC an NA-East player says ping dropped to about 50-60 ms after leaving a 100-member guild with a few members from Australia, New Zealand and Russia. Two players say a layer-info addon shows the server name with "AU" in it, such as "CAMWOWAU1Realm1PVE", which they read as a sign they're on an Australian server. One NA player says they never changed the setting (still NA-West) and still get about 300 ms more, starting the night before. An NA player locked to Oceanic says Battleground queues barely pop there. One player says they're rerolling, and others say they won't. No ETA from Blizzard as of 08:10 UTC.
  • Updated Nov 8, 01:10 UTC: not down. Blizzard has no outage or maintenance post on the US or EU forums or the Blue Tracker (newest WoW: Forever staff post: the Nov 6 hotfixes, 01:07 UTC Nov 7), and the Known Issues thread was last edited at 22:07 UTC Nov 5. outage.report showed 0 reports in 24 hours at 01:00 UTC. What players are posting about instead is high ping from wrong-region routing. New US forum threads: "NA East Account Stuck on OCE World Servers" (00:52 UTC), "Ping issue" (00:37 UTC) and "Created character while on Oceanic, now stuck with high latency" (22:34 UTC Nov 7, also posted on r/classicwow). The "weird latency" thread has 25 posts and the Preferred Account Location thread 22 posts, with Oceanic and North American players reporting it both ways up to 22:38 UTC. What players describe: open-world World latency of about 200 ms from NA-East, back to about 30 ms inside dungeons, and back under 70 ms while grouped with an NA friend. One NA player says it started after grouping with Australian players three days ago, and that a brand-new character has the same 200 ms. Another says it began after creating the character while travelling in Japan. On fixes: two players in another thread say leaving their guild fixed it (one says the guild's AU setting was overriding his own), one after quitting the game and waiting a few minutes. Others say they aren't in a guild, or that changing Preferred Account Location to US did nothing. A player on r/classicwow says the setting shows a note, "Subject to 1 day cooldown". We couldn't check that in game ourselves. A player in the Preferred Account Location thread says the setting's "Applies to all characters on this account" note isn't true for them. Players in Latin America report 190-334 ms too; a volunteer MVP (not Blizzard staff) notes there's no Latin American server they know of (thread). No Blizzard reply in any of these threads and no ETA as of 01:10 UTC.
  • Updated Nov 7, 16:05 UTC: Americas servers went down for maintenance on Saturday morning, US time. At 14:13 UTC a player opened "Servers offline every day" (about 165 posts by 15:35 UTC). By 15:00 UTC posts in that thread say the servers are down for about an hour, and at 15:02 UTC a player wrote that it's "scheduled maintenance to address AH issues", shown "on the launcher". At 15:11 UTC another player there says the notice calls it "scheduled" and about "AH disruptions". In a separate thread at 15:22 UTC a player says the Battle.net notice has it "down until 8am PST" (16:00 UTC). We couldn't see the launcher notice ourselves, so treat the reason and end time as player-reported. At 15:24 and 15:25 UTC players in that thread say Blizzard's server status page shows normal "but world server is down", and at 15:28 UTC a player in the first thread reports "world server down" at login. Some players call it unscheduled, since there was no forum post in advance. Blizzard has no post about it on the US or EU forums or the Blue Tracker (newest Forever staff post: the Nov 6 hotfixes at 01:07 UTC). The same morning, many US and EU forum threads say zones became overcrowded after the Nov 6 layer change. That's a separate issue, covered on our layering page. Separately, a player in the latency thread says at 15:08 UTC that switching from Oceanic to US East didn't fix their high home latency. Back up: at 15:37 UTC a player in the first thread wrote "Oh they really are up now", a "World is up" thread opened at 15:46 UTC, and at 15:42 UTC a player said it was "down for less than an hour". At 15:21 UTC a player quoted the login screen alert: "…this maintenance will address intermittent Auction House disruptions." Whether the Auction House errors are fixed isn't confirmed yet. New player reports after it came back (single threads, no staff reply): a shaman lost trained spells and the gold spent on them in the reset, a disconnect on the boat to Booty Bay, and global chat channels (LFG, World) not working. No Blizzard post about the maintenance as of 16:05 UTC.
  • Updated Nov 7, 05:35 UTC: EU servers had a short maintenance. At 04:18 UTC an EU player opened "Any word on why servers are down?" (16 posts, about 500 views by 05:31 UTC). At 04:21 UTC a player in that thread said it's "a 1 hour scheduled maintenance", and at 04:25 UTC explained it shows in the Battle.net launcher, but only when the launcher language is set to English (UK) instead of English (US). We couldn't check the launcher notice ourselves. Another player in a separate thread also says "It's posted on the launcher." That thread opened at 03:57 UTC and a player in another thread said at 04:36 UTC the maintenance was "like an hour ago", so it may have started before our 04:10 UTC check, which saw no EU outage threads. Blizzard has no post about it on the US or EU forums or Blue Tracker as of 05:35 UTC. At 04:28 UTC a player could reach the character screen again, and at 04:33 UTC the same player who reported the maintenance wrote "The server is back up and running". Between 04:26 and 04:39 UTC, EU players in two threads (1, 2) report "World Server Is Down" after the loading screen, including on the EU PvP ruleset. At 04:32 UTC one of them says it now works, and at 04:47 UTC another player says servers were up 5 minutes earlier and that you "need to update" the game. That update advice is one player's report. At 04:37 UTC one EU player says the slow Auction House "seems" fixed for them, and some EU players say layers changed about two hours before 04:23 UTC (thread). Blizzard hasn't said what changed. The US forums show no outage threads between 04:13 and 05:35 UTC. The latency thread got one new post at 04:26 UTC from a volunteer Tech MVP (not Blizzard staff), asking whether affected players are in guilds with the preferred server location set to OCE. No Blizzard reply. Reddit didn't load from our checker this run, so this entry uses Blizzard's forums only. No ETA from Blizzard as of 05:35 UTC.
  • Updated Nov 7, 04:10 UTC: still not down. No outage or maintenance post from Blizzard on the US or EU forums or Blue Tracker, and no new WoW: Forever staff post after the 01:07 UTC hotfix reply. New player reports since 02:03 UTC: at 03:36 UTC a player in the US forum thread "Thank you for tweaking the layering" wrote that "whatever happened 3 minutes ago made the game near unplayable", with Westfall and Redridge holding "more players than mobs". Another poster in the same thread says it's fine and "quite well balanced" for them. At 03:36 UTC a player on r/classicwow posted "I was unable to quest and the whole layer is lagging". Blizzard hasn't said whether it changed layering. The Preferred Account Location thread now has NA-East players defaulted to AU (240-260 ms) and AU players defaulted to NA, with new posts up to 03:58 UTC. One poster says characters made before they changed the setting stay on the wrong servers, and one has a ticket open with no reply. In an older thread, one player says at 04:01 UTC that their guild had an Oceanic preferred location and their ping went back to normal after they left it. That's one report, not confirmed. New rollback reports: players report skill-ups rolled back while the materials stayed used (1, 03:57 UTC), and trainer skills bought just before the Nov 6 restart were lost but the gold stayed spent (2, one player says their ticket was closed by an automated reply with no gold returned). An EU player still reports the Auction House not working at 04:03 UTC. No ETA from Blizzard as of 04:10 UTC.
  • Updated Nov 7, 02:03 UTC: not down. No outage or maintenance post from Blizzard on the US or EU forums or Blue Tracker, and no outage threads on either forum's latest list. The Nov 6 Americas restart is over: at 15:41 UTC players in the "They're up" thread wrote "World Server is up now" and logged in. New since then: from 22:57 UTC EU players report "The item was not found" when buying single items such as gear on the Auction House (stacks like reagents and potions still buy, players say) (1, 2, 3), and a US player calls the AH "still broken" at 01:45 UTC. No staff reply in those threads. Some players report high world latency, which players in the thread think means they were routed to Oceanic servers (thread, 6 posts, no staff reply). WoW: Forever posts from Blizzard staff since our last update: Kaivax's Class Tuning Incoming - November 10 at 21:11 UTC, and at 01:07 UTC a new reply in the hotfix thread with the Nov 6 hotfixes, which say the "Vorsha the Lasher" quest issue is resolved and list "improvements to the visibility of other players and their targets across relatively large distances". Neither mentions the Auction House or server stability. No ETA from Blizzard as of 02:03 UTC.
  • Updated Nov 6, 15:40 UTC: Americas servers went down on the morning of Nov 6, US time. From about 15:00 UTC players on r/classicwow report a server shutdown partway through Blackfathom Deeps, and another thread at 15:25 UTC says the server is down. On Blizzard's forums at 15:23 UTC, one player says in-game [SERVER] messages about 20 minutes earlier (around 15:03 UTC) said Roleplay ruleset servers would shut down. At 15:20 UTC another thread says the launcher called it scheduled maintenance only after the servers were offline. Players in that thread argue over whether that counts as scheduled. Two threads (1, 2) say Blizzard's server status page showed rulesets as up while the game showed none. At 15:30 UTC a "They're up" thread opened, but by 15:32 UTC the poster said logging in gives "World Server Down" on the character screen. At 15:35 UTC a Roleplay player reports the same error on every character. At 15:39 and 15:40 UTC two more threads (1, 2) report "World Server Down" on the Horde PvP ruleset. Blizzard's last WoW: Forever staff post was the Nov 5 hotfix notes (posted 02:34 UTC Nov 6). Nothing about the restart on the US or EU Blue Tracker as of 15:40 UTC. The EU forums show no outage threads in that window, though that alone doesn't prove EU is unaffected. No ETA from Blizzard as of 15:40 UTC.
  • Updated Nov 5, 21:10 UTC: Blizzard posted five times since our last update. At 06:35 UTC Aggrend wrote that Blizzard is "aware of some issues with certain areas not feeling as populated as they should" and "will be tweaking some numbers tomorrow" (06:35 UTC is 10:35 p.m. PST on Nov 4, so "tomorrow" may mean Nov 5 Pacific time). From about 16:50 UTC some players on r/classicwow report busier layers and more competition for mobs, while other forum posts, from 17:29 UTC up to 21:04 UTC, still describe empty zones. Blizzard hasn't said whether a change is live. At 06:39 UTC he said boats and zeppelins can get "lost in the maelstrom", so Blizzard spawned portals near most docks and inside zeppelin towers. At 15:42 UTC Kaivax opened a new Known Issues thread, last edited 18:26 UTC (at 15:22 UTC he also posted Bug Report forum guidelines). At 15:51 UTC Kaivax asked players in a group-phasing thread whether the "Refresh Now" button puts them with their party. New player reports: rollbacks after disconnects (one player posted a Game Master reply saying lost skill or gold can't be compensated), WOW51900319 disconnects on EU in the evening, mailboxes that won't open in some cities, and a 50-post thread asking for an official answer on the Horde PvP faction lock, with no staff reply by 21:06 UTC. One EU player reports "World server is down" at 75% of the loading screen. No outage. No ETA.
  • Updated Nov 5, 06:10 UTC: Blizzard posted one fix. At 02:43 UTC community manager Kaivax announced a hotfix for Invite-A-Friend players who couldn't level past 10, group, trade, join guilds or use some chat channels. Blizzard's advice: log out and back in. New player reports since 02:10 UTC: layering is now the biggest forum topic (the "Less Layers!" thread has 27 posts by 06:06 UTC), Oceanic players placed on US servers, keybinds lost after a disconnect, error WOW51900327, a 1 silver minimum Auction House deposit, and "faction unavailable" still blocking Horde PvP creation at 05:30 UTC. Isolated reports of a character stuck with "world server down" and error BLZBNTBGS80000011. No outage reports. Known Issues list still empty at 06:05 UTC. No ETA.
  • Updated Nov 5, 02:10 UTC: new player reports since 00:40 UTC. A disconnect wave around 01:17 UTC, with 19 posts in one forum thread by 01:36 UTC. Grouped friends stuck in different phases (one player says both logging out and back in fixed it, another says it didn't). Characters made on Normal or PvP found on a different ruleset (PvP, Roleplay or Roleplay-PvP) after playing. "Throttled" creation still reported at 01:46 UTC. An "internal auction error" when posting at the Auction House. Several new forum threads in the same window describe a smooth launch. Blizzard's Known Issues list is still empty at 02:05 UTC and there are no staff replies in these threads. No ETA.
  • Updated Nov 5, 00:40 UTC: many players are in. New player reports since 23:20 UTC: repeated disconnects, "throttled" character creation on busy rulesets, error BLZ51901016 at login, the Skyborne first quest not showing, the "Sit near the campfire" step not completing, missing boats and zeppelins, and reserved characters missing or on the wrong ruleset. Blizzard posted its Info & Known Issues thread at 23:21 UTC, but its known-issues list is empty. No @BlizzardCS post since 20:00 UTC. No ETA.
  • Updated Nov 4, 23:20 UTC: page published. Login queues plus "all rulesets unavailable" in the first minutes of launch, with more than 20 new threads about it on Blizzard's US forums by 23:05 UTC. From about 23:10 UTC, players on r/classicwow report that relogging makes the rulesets selectable. No staff post or @BlizzardCS post yet. Blizzard's forums, including the Blue Tracker, answer "Server is currently experiencing high load" at times.

We refresh this page while the launch is hot. Specific errors get their own pages, linked from here.

Is WoW Forever down right now?

Mostly back, as of 04:05 UTC on Nov 12. A DDoS hit all Blizzard games, WoW Forever and Retail included, from about 00:53 UTC. Blizzard Customer Support confirmed it at 01:23 UTC and said it was mitigating it. Players report getting back in from about 01:52 UTC (thread); the big disconnect threads went quiet after 02:27 UTC, and two players still reported random disconnects at 03:46 UTC. No all-clear from Blizzard yet. Before the DDoS, on Nov 11:

No, as of 05:10 UTC on Nov 11. US: up. EU: up, but after the maintenance some EU players still got "no realm available" at least until 04:51 UTC; at 04:48 UTC one got in after exiting the game and downloading the client update, while another was still stuck at 04:51 UTC (thread). Blizzard hasn't posted about it. Before that, as of 03:12 UTC on Nov 11: EU servers went down for the weekly maintenance at about 02:00 UTC (03:00 CET), and players report them back up by 02:43 UTC (thread); Blizzard posted nothing about it on its forums. US: up. Before that, as of 21:05 UTC on Nov 10: the servers came back from Tuesday maintenance at about 16:00 UTC, players report (thread). Since then some players on the US forums get "No realms are currently available" (WOW51900309); see the fix in the FAQ below. Earlier, from about 09:23 UTC to about 11:23 UTC, US players reported disconnects and logins stuck on "Logging in to game server" (thread). Before that, as of 06:15 UTC on Nov 10: Players report the servers back up from about 22:42 UTC on Nov 9. US players reported another short wave of disconnects and stuck logins from about 00:40 to 01:00 UTC on Nov 10 (thread); we found no new outage threads after about 01:05 UTC, apart from one lag and desync report at 06:10 UTC. Blizzard posted Nov 9 hotfix notes at 04:23 UTC, which don't mention the crash or the rollback. The open problem is the rollback: players report trained spells, profession skill-ups, quest items and crafting materials lost, with the gold still spent (see the 00:10 UTC entry in the update log above). Before that, WoW Forever was in emergency maintenance in both the US and EU after a crash at about 21:30 UTC. Players quote an in-game [SERVER] shutdown message at 21:49 UTC and an emergency maintenance notice in the Battle.net app from about 21:50 UTC, and many report a rollback of the last minutes of play. At 22:33 UTC players reaching the ruleset screen still saw every ruleset unavailable. Blizzard posted nothing on its forums and gave no ETA (see the 22:35 UTC entry in the update log above). Before that, earlier in the evening, players reported scattered disconnects: At 19:42 UTC EU players reported being kicked out and stuck on "Logging in to game server" for a few minutes while others stayed online, and from about 14:40 UTC to 21:00 UTC US players report sudden disconnects, lag spikes and characters running in place, in small threads of 1 to 6 posts. Blizzard has not posted about it and gave no ETA (see the 21:05 UTC entry in the update log above). Earlier, from 07:46 UTC, EU and then US players reported mass disconnects and logins that hung on "Logging in to game server", and players report it was over by about 08:10 UTC (see the Nov 9 entries in the update log above). A couple of EU players were still stuck on "Connecting" at 09:32 UTC, which looks account-specific. At 09:37 UTC Blizzard staff confirmed in an EU forum reply that the login issues were resolved and "everything's back to normal"; there was no separate outage post. Before this, through 21:10 UTC on Nov 8, the problem players reported was high ping from wrong-region routing (NA players placed on Oceanic servers), not downtime. Blizzard's latest WoW: Forever change is a hotfix at about 19:05 UTC on Nov 8 that raised dungeon kill experience by 50%, per Kaivax's forum post. Details are in the update log above and under wrong-region servers below. On Nov 7, going by player reports: Americas servers went down for maintenance around 15:00 UTC on Nov 7, and players report them back up by about 15:37 UTC. A player quoting the login screen alert says the maintenance "will address intermittent Auction House disruptions". Blizzard has no forum or Blue Tracker post about it. Earlier on Nov 7, EU servers went down for a short maintenance by 04:18 UTC (players say the Battle.net launcher called it scheduled; Blizzard posted nothing on its forums), then some EU players got "World Server Is Down" until about 04:47 UTC. Some players report lag and overcrowded layers from about 03:33 UTC (see the update log above). The day before, Americas servers had a similar restart on Nov 6: from about 15:00 UTC players reported a shutdown, then "World Server Down", and at 15:41 UTC players said the world server was up again (details in the update log above). Since launch, forum and Reddit posts describe many players online and levelling, alongside the disconnects, Auction House errors and other bugs below. Here is what is observed, in order, from 23:00 UTC:

Time (UTC, Nov 4 to 5)SourceWhat we saw
23:00Blizzard, launch scheduleLaunch time. The Nov 4 maintenance (Blizzard Support schedule) ran 18:00 to about 23:00 UTC.
23:00Player report, Blizzard forumsBlizzard's WoW Forever server status page is now in the game version dropdown.
23:02Player report, r/classicwowLogin screen reads "Login Servers are Full", position 1041, estimated 4 min (screenshot above).
23:02 to 23:05Player reports, Blizzard forumsAfter the queue, every ruleset shows "temporarily unavailable". Separate threads: Ruleset unavailable, Gameplay rulesets not available, Queue pop, can't select a rule set.
23:03 to 23:05Player reports, Blizzard forumsQueue positions posted between about 660 and 2,000, with estimates of a few minutes. Some players report "You have been disconnected" and landing back in the queue.
23:04Player report, Blizzard forumsAfter the queue, the game asks for an authenticator code and the Battle.net app keeps spinning on "Connecting". One report so far.
23:06Blizzard forumsThe Blue Tracker and the EU forum index return "Server is currently experiencing high load".
23:06Player reports, r/classicwowTop new thread: "all rulesets are greyed-off" after getting through the queue.
23:09Player reports, Blizzard forumsPlayers who reserved names last week also land on the greyed-out ruleset screen instead of their character list.
23:10 to 23:13Player reports, r/classicwow (1, 2, 3)Players say relogging works: after a new queue the rulesets are selectable, and some reach character creation. Others in the same threads say the greyed screen never refreshed while they waited on it.
23:14 to 23:17Player reports, Blizzard forums and r/classicwowPlayers are getting into the world. Others reach the character list and get disconnected back into the queue. Two forum threads say Roleplay-PvP is still closed while other rulesets work. Some report the faction population lock ("throttled").
23:20@BlizzardCS on XNo post about queues or rulesets. Its latest post, at 20:00 UTC, was about regional launch times.
23:21Blizzard, Info & Known IssuesCommunity manager Vrakthris posts the launch info thread. Its "Known Issues" heading has no entries under it (still empty at 00:38 UTC).
23:22 to 00:32Player reports, Blizzard forumsPlayers who reserved names find the names still taken but the characters missing. Some found them on Roleplay-PvP after choosing PvP during reservation week. Others checked every ruleset and found nothing.
23:38Player reports, Blizzard forumsError BLZ51901016 at login, on both Forever and Retail. 10 posts by 00:34 UTC.
23:40 to 00:30Player reports, r/classicwow and Blizzard forums (1, 2)Boats and zeppelins between continents don't arrive. One player hears the boat bell with no boat there.
23:51 to 00:34Player reports, Blizzard forums"Creation of that type of character is currently throttled" on busy ruleset and faction pairs, mostly Horde on PvP. One thread title says 50 minutes of throttle. Details on our faction unavailable page.
23:54 to 00:34Player reports, Blizzard forums and r/classicwowNew Skyborne characters see no first quest. 17 posts in the forum thread by 00:34 UTC. One player says a Human character on the same account sees quests right away.
23:56 to 00:34Player reports, Blizzard forumsThe Skyborne quest The Great Outdoors doesn't complete its "Sit near the campfire" step.
00:09 to 00:34Player reports, r/classicwow and Blizzard forums (1, 2)Repeated disconnects, some "every minute". In the same Reddit thread, other players say they have no problems.
00:14Player report, Blizzard forumsOne player still can't pick a ruleset: they're no longer grey but won't accept a choice.
00:35@BlizzardCS on XStill no post since 20:00 UTC.
00:47 to 01:57Player reports, Blizzard forums (1, 2, 3)Characters created on Normal or PvP during name reservation turn up on a different ruleset: Normal to PvP in one thread, others on Roleplay or Roleplay-PvP. Some players only notice after hours of play. One player who caught it early deleted and recreated.
00:50 to 01:56Player reports, Blizzard forums (1, 2) and r/classicwowGrouped friends see a "different phase" marker and can't see each other, even standing side by side. Some see their partner as level 0 in the party.
01:17 to 01:36Player reports, Blizzard forumsA wave of disconnects mid-play, then players stuck at "Retrieving character list" or "Logging in to game server". 19 posts in the thread by 01:36 UTC.
01:38 to 01:46Player reports, Blizzard forums (1, 2)"Throttled" character creation is still reported. One player says it lasted 1.5 hours after a 5-minute queue.
01:47 to 01:55Player reports, Blizzard forums"Internal auction error" when posting items at the Auction House. Two players in the thread.
01:00 to 02:00Blizzard forums and r/classicwowSeveral new threads in this hour describe a smooth launch ("Smooth launch, near 0 issues", "Excellent Launch", "No Que at All").
02:05Blizzard, Info & Known IssuesStill one post, Known Issues list still empty. No staff replies in the threads above. We could not load a current @BlizzardCS timeline at 02:05 UTC, so we can't confirm whether it has posted since 20:00 UTC on Nov 4.
02:43Blizzard, Kaivax on the US forums (also EU)"With a hotfix that is now live, we've fixed an issue where players who joined WoW Forever by using an Invite-a-Friend Code were unexpectedly restricted from using certain chat channels, leveling past 10, participating in guilds, forming parties, or trading items with other players." Blizzard suggests logging out and back in. Details: Invite-A-Friend page.
02:50 to 06:06Player reports, Blizzard forums (1, 2, 3) and r/classicwowLayering becomes the biggest topic. Players describe starting zones packed and the zones after them nearly empty, quiet cities and chat that only reaches your own layer. Many of the same posters call the launch smooth. Others reply that the low numbers are just late night in the US.
03:01 to 04:37Player reports, Blizzard forums (1, 2) and r/classicwowOceanic players report 150-300 ms and say they're placed on US servers. Others in Australia report 2-14 ms, and one says there are Oceanic data servers.
03:51 to 03:56Player reports, Blizzard forumsSome players still disconnect, one "almost every 5 minutes", with 5 to 10 minutes to get back in. One player in the thread says only they are affected, not the people they know.
03:56Player reports, Blizzard forumsKeybinds and UI settings reset after a disconnect.
03:58 to 04:59Player reports, Blizzard forums"Your World of Warcraft subscription has expired" (WOW51900327) when creating a Forever character, from players with active game time. 9 posts by 05:06 UTC.
04:23 to 05:58Player reports, Blizzard forums and r/classicwowAuction House deposit shows 1 silver minimum on cheap items. One player in the thread also reports sold enchanting materials not going through.
04:43 to 05:39Player reports, r/classicwow (1, 2)Boats and zeppelins still reported missing, including on Roleplay-PvP.
05:30Player reports, Blizzard forums"This faction is currently unavailable" still blocks new Horde characters on PvP rulesets.
05:35Player report, Blizzard forumsOne character that can't log in ("world server down") after the player tried to leave Zephras Isle. Single report.
05:58Player reports, Blizzard forumsError BLZBNTBGS80000011, can't log in at all. One thread, 2 posts.
06:05Blizzard, Info & Known Issues and Blue TrackerKnown Issues list still empty. The Blue Tracker shows no Forever staff post after Kaivax's 02:43 UTC hotfix.
06:35Blizzard, Aggrend on the US forums"We are aware of some issues with certain areas not feeling as populated as they should. We will be tweaking some numbers tomorrow to help things feel a bit more lively."
06:39Blizzard, Aggrend on the US forumsBoats and zeppelins can be "lost in the maelstrom for extended periods of time". As a temporary fix, Blizzard spawned portals near most transport docks and inside zeppelin towers.
13:47 to 15:50Player reports, EU forumsAfter a disconnect, players log back in 15-20 minutes earlier, losing XP, profession skill and materials. One player says they lost 2 hours over 7-9 rollbacks. 8 posts.
15:40 to 21:06Player reports, US forums (1, 2)Horde still can't be created on PvP rulesets. "Horde PvP is full" reaches 79 posts. A thread asking for an official response reaches 50 posts by 20:41 UTC, with no staff reply.
15:42Blizzard, Known Issues - WoW ForeverKaivax opens a Known Issues thread (edited 18:26 UTC, then again at 22:07 UTC). Full list below.
15:42 to 20:48Player reports, US forumsSome mailboxes do nothing when clicked (Stormwind Trade District, Ironforge bank, Bloodhoof Village, Kharanos inn). Other mailboxes in the same city work.
15:51Blizzard, Kaivax on the US forumsIn a group-phasing thread, Kaivax asks players whether the blue message after joining a party offers a "Refresh Now" button, and whether it puts them with their party.
16:50 to 21:04Player reports, r/classicwow and US forums (1, 2)Players disagree on layers. Some say zones are now crowded with too few mob respawns. Others still report empty zones. Blizzard hasn't said whether its promised change is live.
19:28 to 20:09Player reports, EU forums and r/classicwowRepeated disconnects with WOW51900319, often stuck at "Logging in to game server" afterwards. 13 posts. At 20:09 UTC one player says it stopped for them.
20:40Player report, EU forumsOne EU PvP player gets "World server is down" at 75% of the loading bar. A second player in the thread gets "temporarily unavailable" at character creation.
21:05Blizzard Blue Tracker (US and EU)No new Forever staff post after 15:51 UTC. We couldn't load the @BlizzardCS timeline (rate limited), so we can't confirm its latest post.

WoW Forever Choose Your Gameplay Ruleset screen with Normal, PvP, Roleplay and Roleplay-PvP all greyed out at launch

What is on Blizzard's WoW Forever Known Issues list?

Blizzard's Known Issues - WoW Forever thread lists issues the team calls "notable, impactful, and already tracked with plans to fix in the future". Blizzard says it is "not a comprehensive list" and will be updated. The thread was edited again at 22:07 UTC on Nov 5, and the Nov 6 hotfixes say the "Vorsha the Lasher" quest issue is resolved. As of its 18:26 UTC edit on Nov 5:

  • PvP vendors are temporarily unavailable in all locations (Orgrimmar, Stormwind and Dalaran).
  • "Vorsha the Lasher" in Ashenvale is disabled until a bug causing a crash is fixed.
  • Razorfen Kraul: players can fall into a cauldron near Roogug and get stuck.
  • Gamepad: an error when deleting more than one rare or epic item, and push-to-talk keyboard instructions showing when joining a voice channel.
  • Bank: bank pages display with the tabs listed outside the frame.
  • Stormwind Keep: the entrance may show flashing textures.

The list doesn't include layering, disconnects, rollbacks, mailboxes or the faction lock. Blizzard addressed layering and transports in separate posts (below). For other bugs, Kaivax posted Bug Report Forum Guidelines at 15:22 UTC, asking for clear reproduction steps.

What other WoW Forever problems are players reporting?

These are the problems players report since the first hour, with the workaround players say worked. Blizzard sources are marked. Everything else is unconfirmed.

  • Lag and overcrowded layers (Nov 7, from about 03:33 UTC). Players report a sudden change: zones like Westfall and Redridge with "more players than mobs", and one Reddit thread title says "the whole layer is lagging". Others in the same forum thread say their layer is fine. One player reports being moved to a new layer mid-fight after becoming party leader (r/classicwow, post title). Blizzard hasn't said whether it changed layering. (Source: US forums, r/classicwow, player reports.)
  • Auction House "The item was not found". One EU player still calls the AH broken at 04:03 UTC on Nov 7 (EU forums). Reported on the EU forums from 22:57 UTC on Nov 6: buying single items such as gear fails with "The item was not found", while items sold in stacks, such as reagents and potions, still work, players say. One player reports their own auctions vanishing. One player says changing layer fixed it once. Another thinks the AH is showing outdated listings. A US player calls the AH "still broken" at 01:45 UTC on Nov 7. At 04:37 UTC on Nov 7, after the EU maintenance, one EU player says the slow AH "seems" fixed for them (EU forums). That's one report. On Nov 7 around 15:00 UTC the Americas servers went down for maintenance that players say the Battle.net app notice ties to Auction House issues (see the update log). Blizzard hasn't posted what the fix changes. No staff reply in the AH threads as of 16:05 UTC. (Source: EU forums 1, 2, 3; US forums 4; player reports.)
  • "No realms are currently available" (WOW51900309), Nov 10 after maintenance. Logins fail with this error while friends play and the status page is green. Two players say a full PC restart plus letting the Battle.net app install the update fixed it; one says it didn't. At 23:52 UTC Nov 10 Blizzard Customer Support replied that you "just need to pick up the latest client update": restart the Battle.net desktop app (or your PC) and update to version 1.60.1.70888. One player says that still hadn't worked at 02:52 UTC Nov 11. (Source: US forums)
  • Disconnects with WOW51900319 (Europe, evening). "You have been disconnected from the server (WOW51900319)", then stuck at "Logging in to game server". One player turned off all addons and still got it. At 20:09 UTC one player said it had stopped for them. No Blizzard comment. (Source: EU forums, r/classicwow, player reports.)
  • Rollback after a disconnect. Players log back in where they were 15-20 minutes earlier, without the XP, skill points or materials they gained. One player posted the reply from an in-game Game Master: rollbacks "can happen whenever a player disconnects from the game, the server crashes or when a player logs out with ALT+F4", and "we are not able to compensate lost skill or gold". The GM's advice: log out normally, don't Alt-F4. Newer reports on the US forums: a disconnect rolled back blacksmithing skill-ups while the materials stayed used up, and trainer skills bought just before the Nov 6 restart were lost but the gold stayed spent. One of those players says their ticket was closed by an automated reply without the gold. (Source: EU forums, player-posted GM reply; US forums 1, 2.)
  • Horde can't be created on PvP rulesets. This is faction balancing, not an outage. It's one of the most-discussed issues on the US forums on Nov 5, and Blizzard hasn't replied in those threads. Players' options: Alliance on PvP, Horde on Roleplay-PvP or another ruleset, or wait. Details: faction unavailable guide.
  • Mailbox won't open. Some mailboxes do nothing when clicked while another in the same town works. Players' fixes: use a different mailbox (one says the canal mailbox in Stormwind works), or leave the zone and come back. (Source: US forums, player reports.)
  • Invite-A-Friend guests stuck at level 10, can't group or trade. Blizzard says it's fixed. Kaivax posted at 02:43 UTC that a live hotfix resolves it: "you may wish to log out and back into WoW Forever." One player replied at 03:24 UTC that their friends still had the issue after logging out and back in. More on our Invite-A-Friend page.
  • Empty zones and cities (layering). The biggest forum topic since 02:50 UTC. Players say they're placed in layers where they see almost nobody past the starting area, and that chat only reaches their own layer. One poster on the "Less Layers!" thread wrote: "you can very easily get dumped into a dead layer." This is a design and tuning question, not an outage. Blizzard update, 06:35 UTC Nov 5: Aggrend said Blizzard is aware some areas don't feel "as populated as they should" and will be "tweaking some numbers tomorrow". By the evening, players disagree: some report crowded zones and slow mob respawns, others still see empty ones, and Blizzard hasn't confirmed a change is live. Full explainer: WoW Forever layering. Two players on the "Less Layers!" thread say logging out and back in put them on a busier layer. (Source: Blizzard forums 1, 2, player reports.)
  • Wrong-region servers (high ping), both ways. Still open on Nov 9. Since Nov 5, Oceanic players report 150-300 ms on US servers, and North American players report the open world putting them on Oceanic (Australian) servers at about 200-260 ms. New threads were still opening at 20:18 UTC on Nov 8 (1, 2, 3; older: 4). Since about 16:40 UTC on Nov 8, some players whose Preferred Account Location is set to their own region report the same pattern: World latency around 190-200 ms while Home latency stays normal. Players say ping drops back to normal inside dungeons and while grouped with players from their own region, then rises again in the open world. The main thread reached 52 posts by 20:45 UTC on Nov 8. No Blizzard staff reply in these threads as of 21:05 UTC on Nov 9, when the Preferred Account Location thread had 78 posts. What players say works, most-confirmed first:
  • Set Preferred Account Location to your own region. In game: Options > System > Languages and Social > Preferred Account Location (AU if you're in Oceania, your NA location if you're in North America), then log out and back in. Blizzard's Language and Social Settings post asks everyone to check that panel and relog, but doesn't mention routing. Players report mixed results. Two players on Nov 8 say it fixes characters you create afterwards, while existing characters stay on the old region (thread, posts from 03:47 and 07:22 UTC on Nov 8). One Oceanic player says even new characters still get 220 ms. One says it reverts to NA-West on relog, and a player on r/classicwow says the setting shows "Subject to 1 day cooldown", so it may take a day to apply.
  • Leave a guild whose preferred location is the other region. One player says the guild's location overrode theirs even when playing solo. Two players in this thread say leaving the guild fixed it (one also quit the game and waited a few minutes), and on Nov 8 an NA-East player in a 100-member guild with a few overseas members says their ping "slowly went back down" to about 50-60 ms after leaving. Others say they're stuck without being in a guild.
  • Group with players from your region while you play. Players say it lowers ping while the group lasts.

To check which region you're on, two players say a layer-info addon shows the server name, with "AU" in it on Australian servers and "US" on US ones. If none of these work, one player says they're rerolling a new character, and others are waiting for a Blizzard fix. Blizzard hasn't said whether existing characters will be moved. An NA player stuck on Oceanic says Battleground queues barely pop there. It's likely not your home connection: one NA player says their Home latency stayed about 30 ms while World latency sat at 200 ms. Players are opening tickets, and one says theirs has had no reply. Players in Latin America also report 190-334 ms; a volunteer MVP says there's no Latin American server they know of. (Source: Blizzard US forums and r/classicwow, player reports.)

  • Keybinds and settings gone after a disconnect. Players say settings only save when you log out through the game menu, so a disconnect, Alt-F4 or closing the window loses them. Set up your bars, then log out once through the menu to save them. (Source: Blizzard forums, player reports.)
  • WOW51900327, "subscription has expired" with active game time. The player who found the cause says the launcher was logging them into a second WoW account they didn't know they had. Check the account dropdown in the Battle.net app before anything else. (Source: Blizzard forums, player reports.) More fixes: login errors guide.
  • Auction House deposit of 1 silver minimum. Players listing cheap items see a 1 silver deposit, and one says they sold leather to a vendor to afford it. Players disagree on whether it's a bug or an old intended rule. Blizzard hasn't posted about it on the forums. (Source: Blizzard forums.)
  • Disconnects every minute. Reported on r/classicwow and the forums from 00:09 UTC, with a bigger wave around 01:17 UTC: players disconnected mid-play, then stuck at "Retrieving character list" or "Logging in to game server" (forum thread, 19 posts by 01:36 UTC). It doesn't hit everyone: in the 00:09 Reddit thread, other players say they're fine. One player says it stopped for them after a while. Another reports a disconnect at the "prove you're not a robot" check, before login. No confirmed fix yet. If it's only you, try our login errors guide first.
  • Error BLZ51901016 at login. It hits Retail too. The player who opened the thread says turning off their VPN (ExitLag, a game network tool) fixed it, and a second player confirms. A third player fixed it the opposite way, by turning the VPN on and then off. One player without a VPN says repair and cache deletion didn't help. (Source: Blizzard forums, player reports.)
  • "Creation of that type of character is currently throttled." This is the population limit on a busy ruleset and faction, not an outage. Some players get through after a few tries. See the faction unavailable and throttled guide.
  • No first quest for a new Skyborne character. Players say clearing map filters and reloading doesn't help, and no workaround is reported yet. Two affected players say they bought the $29.99 Heroic Pack for the race, but nobody has shown that's the cause. Some are starting an alt of another race until a fix. Background on the race: Skyborne starting zone guide.
  • "Sit near the campfire" won't complete (The Great Outdoors). One player's fix: type /sit, then type /sit again while sitting. (Source: Blizzard forums, single report.)
  • Boats and zeppelins don't arrive. Blizzard confirmed it. At 06:39 UTC Aggrend wrote that transports can be "lost in the maelstrom for extended periods of time" and that, as a temporary fix, Blizzard spawned portals near most transport docks or inside the zeppelin towers to move between continents. Aggrend added: "We have a proper fix going out in the morning, and once we've verified that's in and working, we'll be removing those portals." Blizzard hasn't said whether that fix is live yet. Until it does, if your boat doesn't come, look for the portal nearby.
  • Grouped friends stuck in different phases. Party members show a "different phase" marker and can't see each other, sometimes shown as level 0 in the party. A fix posted on r/classicwow: after joining, the invited player clicks the blue "the world around you will change" message (lower right in Kaivax's screenshot; one poster says left side) and then Refresh Now, which moves them to the inviter's layer. Players disagree on who sees the button: one player in Kaivax's thread says the friend who invited them got the message and clicking it worked, so whoever sees it should try it. Blizzard's Kaivax asked players at 15:51 UTC whether that button shows up and whether it works. Blizzard hasn't posted a fix. Logging out and back in worked for some players earlier, not for others. (Source: Blizzard forums 1, 2, player reports.) How grouping is meant to work: rulesets and playing with friends.
  • Character on the wrong ruleset. Players who made characters on Normal or PvP during name reservation find them on a different ruleset (PvP, Roleplay or Roleplay-PvP), some only after hours of play. Check the ruleset on the character screen before you level. One player who caught it early deleted and recreated. If you've already played, that's a ticket for Blizzard Support. (Source: Blizzard forums 1, 2, player reports.)
  • "Internal auction error" at the Auction House. Two players report it when posting items from about 01:47 UTC. No workaround reported. (Source: Blizzard forums.)
  • Reserved characters missing. First check every ruleset. A forum player recalls a reservation-week bug that sent some PvP picks to Roleplay-PvP, and players in that thread found their characters there. Others checked every ruleset and found nothing, which is a ticket for Blizzard Support.

What does "This ruleset is temporarily unavailable" mean at launch?

It means the game isn't letting you into any ruleset right now. Forever has no realm list. You pick one of four rulesets (Normal, PvP, Roleplay, Roleplay-PvP) and the game matches you by language (how rulesets work). When all four are grey for everyone at the same moment, the problem is on Blizzard's side.

This also happened at the start of Early Name Reservation. In Europe on Oct 27, rulesets stayed grey until Blizzard's Yryadorne posted: "World of Warcraft: Forever Name Reservations are delayed while we resolve some final technical issues." Players in that thread reported getting in at about 19:45 UTC, roughly 2 hours 45 minutes after the scheduled 17:00 UTC start. That is history, not a forecast for tonight.

If only one ruleset is grey for you while others work, or only your account fails, it's a different problem. Our WoW Forever login errors guide covers the account, language and region causes.

What should I do while rulesets are unavailable?

This was the main problem from 23:02 to about 23:15 UTC. By 00:40 UTC we only see one new forum report of it. Fixes ranked by how often players confirm them, with the source for each:

  • Relog if the rulesets are still grey. This was the main fix in the first hour, and it is still the first thing to try. From about 23:10 UTC, several players on r/classicwow report that exiting and queueing again worked: the rulesets were selectable on the second try, and some reached character creation (one, two, three). Players who waited on the grey screen say it never refreshed. One player says it was the same at the start of name reservation: you had to reconnect for the rulesets to light up. The cost is a new login queue. Early relogs reported 7 to 9 minutes, but by 23:14 UTC one player said the estimate was over an hour. (Player reports.)
  • If you get disconnected, log straight back in. Disconnected players say they went back into the login queue with a short wait. (Source: Blizzard forums and r/classicwow, player reports.)
  • Check the official status page, not third-party sites. Blizzard's Forever server status page is the official list. Blizzard's text on that page: "If your server is listed as down, rest assured that we're aware of it and working diligently to bring it back online as quickly as possible." Our live WoW Forever server status tool collects the same sources in one place.
  • Don't reinstall or run Scan and Repair for this. It's server-side. During the Normal ruleset outage in reservation week, players said reinstalls and repairs changed nothing (details).

Blizzard hasn't confirmed the relog workaround or posted about the problem. We'll add any staff post here, with the time.

Why is there a login queue in WoW Forever?

"Login Servers are Full" is the login queue in front of the ruleset screen. Players ask why there's a queue before you even choose a ruleset. Blizzard hasn't explained it. The queue numbers players posted in the first five minutes ranged from about 660 to 2,000, with estimated waits of a few minutes. Those are single screenshots, not an official figure. Blizzard has not published queue sizes or limits.

We'll cover queues in detail on a dedicated WoW Forever queue times page once there's enough observed data. No guesses here.

Is it my account or is WoW Forever down for everyone?

Quick check:

  • Everyone on the forums and r/classicwow reports the same thing at the same time (at launch: greyed rulesets): it's Blizzard, not you. Relog once, then wait. If only you and a few others disconnect while your friends play on, it's not a full outage. On Nov 5, players in the WOW51900319 thread said they were the only one in their group being disconnected.
  • "Access to this realm requires an account with a valid access license" (WOW51900337): Blizzard's @BlizzardCS said at 14:00 UTC: "Seeing error WOW51900337 when trying to log into #WoWForever? This is expected, as the game is not live yet." After 23:00 UTC it usually means the account you picked has no active subscription or Game Time. See WOW51900337 fixes.
  • The game asks for an authenticator code after the queue and the Battle.net app hangs on "Connecting": one player reports this (thread). It's a Battle.net authentication problem, not an outage. Restart the Battle.net app and try again.
  • Stuck on "Connecting" while friends play, and the Battle.net launcher shows your Forever account as "??": an EU player reports this on Nov 9, still stuck after the morning disconnect wave ended for most players (thread). That looks account-side, not a server outage. At 09:37 UTC Blizzard staff replied in that thread that logins are back to normal and pointed anyone still stuck to the Connection Troubleshooting guide. If that doesn't help, open a Blizzard Support ticket.
  • "This faction is currently unavailable": that's Blizzard's population lock, not an outage. See our faction unavailable guide.
  • Invite-A-Friend guest can't log in: launch codes run Nov 4 to 11. See Invite-A-Friend launch codes.

When will WoW Forever be back up?

Nov 12 DDoS: players are mostly back in since about 01:52 UTC. Blizzard said at 01:23 UTC it was mitigating the attack and "things should be improving" (reply), but gave no end time: no ETA from Blizzard as of 04:05 UTC. Earlier, on Nov 11:

EU: back up. Some players still couldn't log in at 04:51 UTC; at 04:48 UTC one got in after "Exit, download update, launch" (thread). No end time from Blizzard as of 05:10 UTC. Earlier: the weekly maintenance started at about 02:00 UTC on Nov 11 and a player wrote "servers are up" at 02:43 UTC (thread). Blizzard gave no end time on its forums; one EU player says the Battle.net app notice gave "1 hours downtime" (thread). US: up. Before that, as of 21:05 UTC on Nov 10: the Nov 10 maintenance ran from about 15:00 to 16:00 UTC, one player reports; Blizzard posted nothing about it on its forums. For the 09:23 UTC disconnect wave Blizzard gave no ETA; one player called the servers back up at 09:41 UTC, but disconnect reports went on until about 11:23 UTC. For the WOW51900309 "No realms" error after the maintenance there is no ETA from Blizzard as of 21:05 UTC. The Nov 9 emergency maintenance (from about 21:50 UTC, US and EU) is over: players report the servers back from about 22:42 UTC. Blizzard never gave an ETA for it, and the Battle.net notice players quoted gave no end time. For restoring what the rollback took (trained skills, gold, quest items) there is no ETA or answer from Blizzard as of 21:05 UTC on Nov 10; its Nov 9 hotfix notes, posted at 04:23 UTC, don't mention it. For the earlier evening disconnects and lag spikes (EU from 19:42 UTC, US through 21:00 UTC) there was no ETA either. The morning disconnects and login failures (from 07:46 UTC) ended around 08:10 UTC, players report. Blizzard gave no ETA; at 09:37 UTC a staff member confirmed in an EU forum reply that everything was back to normal. For the high ping from wrong-region routing there is no ETA from Blizzard as of 21:05 UTC on Nov 10, and no staff reply. Americas servers came back from the Nov 7 maintenance (around 15:00 UTC) by about 15:37 UTC, players report. A player quoting the Battle.net app says the notice gave 8:00 a.m. PST (16:00 UTC) as the end time, so it finished early. Blizzard posted no ETA on its forums. EU servers came back from the earlier Nov 7 maintenance (by 04:18 UTC) by about 04:47 UTC, players report, and Blizzard gave no ETA for it on its forums. The Nov 6 Americas restart ended within the hour (players report the world server back up at 15:41 UTC), and Blizzard never posted an ETA for it. For the layer crowding there is no ETA from Blizzard as of 21:05 UTC on Nov 9, and Blizzard hasn't confirmed whether the Auction House errors are fixed, and no staff reply. Through Nov 5, Blizzard fixed one bug overnight (Invite-A-Friend restrictions, hotfix at 02:43 UTC), put portals at the docks for broken boats and zeppelins (with a "proper fix" promised "in the morning"), said it would be "tweaking some numbers" so areas feel more populated, and published a Known Issues list that says the listed bugs have "plans to fix in the future", without dates. For disconnects, rollbacks and the Horde PvP faction lock there is no ETA from Blizzard as of 00:10 UTC on Nov 10. When Blizzard posts, it goes at the top of the update log with the time and source.

How do I check WoW Forever server status myself?

Four official places, fastest first:

  • @BlizzardCS on X (and @BlizzardCSEU_EN for Europe). Outage acknowledgements usually land here first.
  • The Battle.net app, on the World of Warcraft tab with "World of Warcraft: Forever" selected in the game version menu. Banners about maintenance show there. EU players say the app shows EU maintenance banners only with its language set to English (UK); with English (US) they saw none (thread).
  • Blizzard's Forever server status page, added at launch.
  • The Forever forums and the Blue Tracker, for staff replies. Expect "high load" errors on launch night.

r/classicwow and Downdetector show whether other players see the same thing, but they aren't official. Our earlier reservation-week status log has every Blizzard status post from Oct 27 to Nov 3.

What changed on Nov 12?

  • Nov 12, 00:48 UTC: Kaivax posts the Nov 11 hotfix notes. Among class, quest and bag changes: "The Item Restoration service has been disabled while we investigate and address a critical bug."
  • Nov 12, about 00:53 UTC: mass disconnects on WoW Forever and Retail; players stuck at "Logging in to game server" (1, 2, 3).
  • Nov 12, 01:23 UTC: Blizzard Customer Support's Vrakthris confirms "a DDOS for all games" and says Blizzard is mitigating it. Players say the Battle.net app shows a DDoS warning.
  • Nov 12, 01:52 to 01:54 UTC: players report getting back in (thread). The two biggest threads get their last posts at 02:27 UTC.
  • Nov 12, 02:11 UTC: Vrakthris tells a player support generally can't restore gold lost in a crash or rollback (reply).
  • Nov 12, 03:46 UTC: two new one-post threads still report random disconnects (1, 2). No all-clear from Blizzard as of 04:05 UTC.
Bags

WoW Forever - Bags

Get Bags

4.9· 2k+ ordersSee all options
Startingfrom $2.84 (4 × Small Silk Pack, 10 slots)Buy now

What changed on Nov 11?

  • Nov 11, 01:10 UTC: Kaivax posts that a fix for shaman totems lost in the Nov 9 crash is live in all regions; totems return to your bag (relog with free bag space if you were online). First Blizzard post we've seen that refers to the crash; nothing on lost skills or gold.
  • Nov 11, about 02:00 UTC (03:00 CET): EU servers go down for the weekly Wednesday maintenance, players report (1, 2). One player says the Battle.net app notice gave "1 hours downtime". No Blizzard forum post, no end time.
  • Nov 11, 02:43 UTC: EU back up, players report: "P.S servers are up." (thread); at 02:48 UTC the same player says "servers are back up". One player was still asking when the servers would be up at 03:04 UTC. US up with no new outage threads.
  • Nov 11, 03:27 UTC: Kaivax posts the Nov 10 hotfix notes: "with realm restarts", Auction House minimum deposit 1 copper (was 1 silver) and two mail fixes; it also lists class changes including the Enhancement Shaman Stormstrike change. At 04:43 UTC an EU player says the Enhancement changes aren't live in EU yet (thread).
  • Nov 11, 03:37 to 04:51 UTC: some EU players still get "no realm available" after the maintenance (thread); at 04:48 UTC one logs in after exiting and downloading the update.
  • Nov 10, 23:52 UTC (added Nov 11): Blizzard Customer Support replies to one player that WOW51900309 "No realms" "sounds like" a missing client update (version 1.60.1.70888).

What changed on Nov 10?

  • Nov 10, about 00:40 to 01:00 UTC: US players report a new wave of disconnects and logins stuck on "Logging in to game server" (thread).
  • Nov 10, 01:05 to 06:15 UTC: no new outage or login-failure threads on the US or EU forums; at 06:10 UTC one US player reported the game "again desyncing and lagging" (thread). Players keep reporting rollback losses (skills and gold) with no staff reply.
  • Nov 10, 02:05 UTC: Blizzard posts PvP Faction Balance Updates: character creation on the more populous faction in each region gets harder, currently Horde on NA PvP and Alliance on EU Roleplay-PvP.
  • Nov 10, 04:23 UTC: Blizzard adds the November 9 section to the WoW: Forever hotfix notes, including lower player populations in congested zones (a bigger change on PvP). No mention of the crash or the rollback.
  • Nov 10, 06:15 UTC: servers up, no Blizzard ETA for rollback losses or wrong-region routing.
  • Nov 10, about 09:23 to 11:23 UTC: US players report a new disconnect wave and logins stuck on "Logging in to game server" (thread); some relog into "world server is down" (thread).
  • Nov 10, about 15:00 to 16:00 UTC: scheduled maintenance, shown as a Battle.net app banner, players report (1, 2). No Blizzard forum post.
  • Nov 10, from 17:08 UTC: "No realms are currently available" (WOW51900309) for some players on the US forums (one on an Oceanic server); restarting the PC and letting the launcher update fixed it for two players (thread).
  • Nov 10, 21:05 UTC: servers up. Blizzard hasn't posted that the class tuning planned for Nov 10 is live, and still no word on the Nov 9 rollback.

What changed on Nov 9?

  • Nov 9, 07:46 UTC: EU players report mass disconnects, full login queues and logins hanging on "Logging in to game server" (EU forum thread, r/classicwow).
  • Nov 9, 07:48 to 08:02 UTC: US players on PvP, PvE and Roleplay-PvP rulesets report chain disconnects in nine new US forum threads opened from 07:48 to 08:04 UTC, plus one player in Australia. Two players say Retail login failed for them too.
  • Nov 9, 08:05 UTC: US reports still arriving, EU forum quieter since 08:01 UTC. No outage post from Blizzard on the US or EU forums or the Blue Tracker, no staff reply in the threads, no ETA.
  • Nov 9, 08:06 to 08:10 UTC: players in the US WoW: Forever threads report getting back in ("I'm back in… dead, but in" at 08:10 UTC).
  • Nov 9, 09:35 UTC: no new outage threads since about 08:14 UTC. Two EU players are still stuck on "Connecting" in one thread, which looks account-specific. Blizzard had not posted about the wave.
  • Nov 9, 09:37 UTC: Blizzard staff confirm in an EU forum reply that the login issues are resolved and link the Connection Troubleshooting guide.
  • Nov 9, 14:40 to 17:38 UTC: US players report sudden disconnects and logins stuck on "logging into game server" (thread, 6 posts).
  • Nov 9, 19:42 to 19:47 UTC: EU players report being kicked and stuck on "Logging in to game server" while friends stay online; one gets back in at 19:47 UTC (EU thread).
  • Nov 9, 21:30 UTC: US players (and, from 21:48 UTC, EU players) report being disconnected and stuck on "Retrieving character list" (US thread).
  • Nov 9, 21:48 UTC: players report a rollback after logging back in, losing loot, quest items, skills and crafting materials (EU thread).
  • Nov 9, 21:49 UTC: in-game [SERVER] message, quoted by players: "Sorry, we have to take the servers down briefly. A few mischievous murlocs have invaded the server room". A 15-minute shutdown countdown follows; players say servers went down early.
  • Nov 9, 21:50 to 21:56 UTC: players report an emergency maintenance notice in the Battle.net app in both regions.
  • Nov 9, 22:15 to 22:33 UTC: players reach the ruleset screen, but every ruleset is unavailable. No Blizzard forum post and no ETA as of 22:35 UTC.
  • Nov 9, about 22:42 UTC: players report the servers back up in the US and EU; some needed a client relaunch. Blizzard posted nothing.
  • Nov 9, 22:55 UTC to Nov 10, 00:03 UTC: players in both regions report trained spells and profession skill-ups lost in the rollback with the gold still spent, plus missing quest items. No Blizzard reply as of 00:10 UTC.
  • Nov 9, 19:58 to 20:59 UTC: new US threads report random disconnects and, on the PvP ruleset, lag spikes with characters running in place (1, 2). No Blizzard post or ETA as of 21:05 UTC.

What changed on Nov 8?

  • Nov 7, 21:41 to 22:38 UTC: four more players post in the Preferred Account Location thread: Oceanic players stuck on US servers and a US player stuck on Australian servers. One says changing the setting "doesn't do anything".
  • Nov 7, 22:34 to Nov 8, 00:52 UTC: new US forum threads from NA players stuck on Oceanic servers at about 200 ms, plus a matching r/classicwow post. A player there says Preferred Account Location shows "Subject to 1 day cooldown".
  • Nov 8, 01:10 UTC: no outage or maintenance post from Blizzard, no outage threads on the US forums' newest-topics list, 0 reports in 24 hours on outage.report at 01:00 UTC. No staff reply on routing and no ETA.
  • Nov 8, 01:37 to 07:54 UTC: the Preferred Account Location thread grows from 22 to 42 posts. Players report the setting only fixes newly created characters, one says leaving their guild brought ping back to about 50-60 ms, and one says they'll reroll.
  • Nov 8, 08:10 UTC: still no outage or maintenance post from Blizzard on the US or EU forums or the Blue Tracker, no outage threads on either forum's newest-topics list, and no staff reply on routing. No ETA.
  • Nov 8, 16:41 to 20:50 UTC: the Preferred Account Location thread reaches 52 posts. Players whose Preferred Account Location is set to their own region now report about 190-200 ms World latency with normal Home latency, and a new NA-East thread says new characters are affected too. No staff reply.
  • Nov 8, 19:05 UTC: Blizzard deploys a hotfix raising dungeon kill experience by 50% (Kaivax, posted 19:47 UTC).
  • Nov 8, 21:10 UTC: still no outage or maintenance post from Blizzard, no outage threads on either forum's newest-topics list, no staff reply on routing. No ETA.

What changed on Nov 7?

  • Nov 6, 15:41 UTC: players in the "They're up" thread say the world server is up after the Americas restart.
  • Nov 6, 21:11 UTC: Kaivax posts Class Tuning Incoming - November 10. It's balance, not stability.
  • Nov 6, 22:57 UTC onward: EU players report "The item was not found" on Auction House purchases of single items. A US player reports the AH "still broken" at 01:45 UTC. No staff reply.
  • Nov 7, 01:07 UTC: Kaivax adds the Nov 6 hotfixes, including a fix for the "Vorsha the Lasher" quest and better visibility of distant players. The Known Issues thread, last edited 22:07 UTC Nov 5, still lists Vorsha as disabled.
  • Nov 7, 02:03 UTC: no outage or maintenance post from Blizzard, no outage threads on the US or EU forums. No ETA for the Auction House errors.
  • Nov 7, 03:33 to 03:58 UTC: players report lag and overcrowded layers, NA characters routed to Australian servers, and rollbacks where used materials or spent gold weren't returned. No staff reply.
  • Nov 7, 04:10 UTC: still no outage or maintenance post, and no WoW: Forever staff post after 01:07 UTC. EU players still report the Auction House not working at 04:03 UTC. No ETA.
  • Nov 7, by 04:18 to about 04:47 UTC: EU servers down for a short maintenance that players say was announced only in the Battle.net launcher, then "World Server Is Down" for some EU players. Back up, players say. No Blizzard forum post, no ETA.
  • Nov 7, around 15:00 UTC: Americas servers down for maintenance, the second morning in a row. Players say the Battle.net app notice cites Auction House issues and runs until 8:00 a.m. PST (16:00 UTC). "World Server Down" at login while the status page showed normal. No Blizzard forum or Blue Tracker post. Back up by about 15:37 UTC, players report. A player quotes the login screen alert: the maintenance "will address intermittent Auction House disruptions". After it, single reports of lost trained spells and gold, a boat disconnect and global chat channels not working.

What changed on Nov 6?

  • 02:34 UTC: Blizzard posts the Nov 5 hotfix notes (including an NPC respawn fix and a Druid trainer fix). They don't mention server stability.
  • About 15:00 UTC: Americas players report a server shutdown mid-session, some partway through a dungeon. One player says in-game [SERVER] messages announced the Roleplay ruleset shutdown around 15:03 UTC.
  • 15:19 to 15:23 UTC: players say Blizzard's server status page shows rulesets as up while the game shows none, and that the launcher called it scheduled maintenance only after the servers went offline.
  • 15:30 to 15:40 UTC: some players get back to the character list, then "World Server Down" when entering the world, reported on the Roleplay and Horde PvP rulesets. No Blizzard post. No ETA as of 15:40 UTC.

What changed on Nov 5?

  • 00:09 UTC onward: reports of repeated disconnects, for some players only.
  • By 00:40 UTC: many players are in the world, going by player reports. Open player-reported problems: "throttled" creation, BLZ51901016, the missing Skyborne first quest, the campfire quest step, boats and zeppelins, and missing reserved characters. Blizzard's Known Issues list is empty and @BlizzardCS has not posted since 20:00 UTC on Nov 4.
  • 00:47 to 02:00 UTC: new player reports of characters moved to a different ruleset, grouped friends in different phases, a disconnect wave around 01:17 UTC and an Auction House "internal auction error". Throttling is still reported at 01:46 UTC. Several new forum threads in the same hour call the launch smooth. Known Issues list still empty at 02:05 UTC.
  • 02:43 UTC: Blizzard hotfixes the Invite-A-Friend restrictions (level 10 cap, no groups, trades, guilds or some chat channels).
  • 02:50 to 06:06 UTC: layering complaints take over the forums. New player reports of Oceanic players on US servers, keybinds lost after disconnects, WOW51900327 errors and a 1 silver Auction House deposit. "Faction unavailable" for Horde on PvP still reported at 05:30 UTC. No outage reports. Known Issues list still empty at 06:05 UTC.
  • 06:35 to 06:39 UTC: Blizzard's Aggrend says Blizzard will be "tweaking some numbers tomorrow" so areas feel more populated, and that portals now stand near docks and in zeppelin towers because transports get stuck.
  • 13:47 UTC onward: players report rollbacks of 15-20 minutes after disconnects. One player posts a Game Master reply saying lost skill or gold can't be compensated.
  • 15:42 UTC: Blizzard opens a new Known Issues thread (PvP vendors unavailable, Vorsha the Lasher disabled, a Razorfen Kraul cauldron, gamepad, bank and Stormwind Keep bugs).
  • 15:40 to 21:06 UTC: the Horde PvP faction lock spreads across several large forum threads. No staff reply.
  • 19:28 to 20:09 UTC: a wave of WOW51900319 disconnects on EU. No outage. No ETA.

What changed on Nov 4?

  • 18:00 to about 23:00 UTC: launch maintenance, listed on Blizzard's support schedule as "Game unavailable during this time."
  • 23:00 UTC: WoW Forever launched. Login opened with a queue.
  • 23:02 UTC onward: all rulesets greyed out for players who got through the queue.
  • About 23:10 UTC onward: players report that relogging makes the rulesets selectable. No Blizzard statement as of 23:20 UTC.
  • 23:21 UTC: Blizzard posts its Info & Known Issues thread, with no known issues listed.

What should I do once I'm in?

Have a plan for your first hour. Our WoW Forever beginner guide covers what to do on day 1. If you're worried about falling behind the launch crowd, WoW Forever power leveling is played by hand on the quest route, at whatever pace you choose. On a fresh economy, early gold also goes far: training, your first mount at 40 and respecs. That's where WoW Forever gold helps.

FAQ

Did WoW Forever roll back my character on Nov 9? Many players say yes: after the 21:30 UTC crash they logged back in a few minutes earlier, and loot, quest items, trained skills or crafting materials spent in that window were gone. After the servers came back at about 22:42 UTC, players in both regions report the same pattern: spells and profession skill-ups trained shortly before the crash are gone, but the gold is still spent. Blizzard hasn't said whether it will restore anything as of 06:15 UTC on Nov 10, and its Nov 9 hotfix notes (posted 04:23 UTC Nov 10) don't mention the rollback. If you lost a rare item, note the time and item and open a Blizzard Support ticket; earlier this week one player posted a Game Master reply saying lost skill or gold can't be compensated.

Did Blizzard say anything about the Nov 9 crash or rollback? Only about shaman totems, as of 03:12 UTC on Nov 11. At 01:10 UTC Kaivax posted that shamans who lost a totem "due to the crash" get it back in their bags (fix live in all regions). Blizzard still hasn't said anything about trained skills, gold or quest items lost in the rollback. Earlier, as of 06:15 UTC on Nov 10: Blizzard's main posts since the crash are the Nov 9 hotfix notes (posted 04:23 UTC Nov 10) and a PvP faction balance update (02:05 UTC). None of Blizzard's posts since the crash, including Kaivax's follow-up replies in the faction thread, mention the crash, the emergency maintenance or the rollback, and we found no staff reply in the US or EU rollback threads. The hotfix notes lower player populations in congested zones; they don't address the rollback.

What is error WOW51900309 "No realms are currently available" in WoW Forever? Players on the US forums (one on an Oceanic server) report it from 17:08 UTC on Nov 10, after the 15:00 to 16:00 UTC maintenance: the login fails with "No realms are currently available" while friends are online and the status page shows green (thread). Two players say this fixed it: close the game, restart the PC, then let the Battle.net app download the WoW Forever update before launching. One says forcing the update in the launcher without a restart didn't work, because the launcher still thought the game was running, and one more says the error stayed after updating. At 23:52 UTC Nov 10 Blizzard Customer Support agent Vrakthris replied: "it sounds like you just need to pick up the latest client update. Try restarting your Desktop app, then you should be prompted to update." He adds that you should be on version 1.60.1.70888. At 02:52 UTC Nov 11 a player there says restarts haven't helped and their client is still on an older version. On Nov 11 EU players reported a similar "no realm available" message from 03:37 to 04:51 UTC, after the weekly maintenance, and at 04:48 UTC one got in after "Exit, download update, launch" (thread).

Is WoW Forever down right now? Mostly back, as of 04:05 UTC on Nov 12. A DDoS hit all Blizzard games from about 00:53 UTC; Blizzard Customer Support confirmed it at 01:23 UTC and said it was mitigating it. Players report getting back in from about 01:52 UTC, and a few still reported random disconnects at 03:46 UTC. Blizzard hasn't posted an all-clear or an ETA.

Was WoW Forever DDoSed on Nov 12? Yes, Blizzard says so. At 01:23 UTC Customer Support's Vrakthris wrote "we have been experiencing a DDOS for all games. We are in the process of mitigating it" (reply). Retail players were disconnected too. Blizzard hasn't said who was behind it; claims on the forums about who did it are guesses.

Can Blizzard restore items or gold I lost in a disconnect or crash? Not right now. Blizzard's Nov 11 hotfix notes say the Item Restoration service "has been disabled while we investigate and address a critical bug", and on Nov 12 Blizzard Customer Support told a player it generally can't compensate or restore after a crash or rollback (reply). It pointed players to the Forever Discussion forum if they think the game developers should make up for it.

Why didn't I see the EU maintenance notice in the Battle.net app? EU players say the app only shows EU maintenance banners when its language is set to English (UK); with English (US) they saw none (thread). One player who plays through GeForce NOW says the banners never showed there (thread). Blizzard hasn't commented. The weekly EU maintenance starts at 3:00 a.m. CET on Wednesdays, players there say.

Why does WoW Forever say "World Server Is Down"? Players see it after the loading screen: the character screen works, but entering the world fails. Blizzard hasn't said why. Players saw it right after restarts: on Nov 6 after the Americas restart, and on Nov 7 for EU players after the maintenance that started by 04:18 UTC. Both times players say it cleared within an hour (about 15-20 minutes on Nov 7). One EU player advised: "U need to update forever". That's one player's tip, not confirmed by Blizzard. Blizzard hasn't posted about the error.

Why does the WoW Forever Auction House say "The item was not found"? Blizzard hasn't said. EU players report it from 22:57 UTC on Nov 6 when buying single items such as gear, while stacks of reagents and potions still buy. One player says changing layer fixed it once. One EU player says at 04:37 UTC on Nov 7 it seems fixed for them. Players say the Americas maintenance around 15:00 UTC on Nov 7 was announced in the Battle.net app as addressing Auction House issues. Blizzard hasn't confirmed on its forums what was fixed, as of 16:05 UTC on Nov 7.

Why is my WoW Forever ping 200 ms in North America? Players report the open world placing NA characters on Oceanic (Australian) servers since Nov 5, still reported on Nov 8. Players say ping drops back inside dungeons or while grouped with NA players. Players' fixes: set Options > System > Languages and Social > Preferred Account Location to your region and relog (a player says it's "Subject to 1 day cooldown"), or leave a guild with Oceanic members or an Oceanic preferred location, which one player says brought them back to about 50-60 ms on Nov 8. Players report the setting only moves characters created afterwards, so existing characters can stay on Oceanic servers. Since about 16:40 UTC on Nov 8, some players whose Preferred Account Location is set to their own region also report about 190-200 ms World latency with normal Home latency, so a wrong setting isn't the only cause players describe. Blizzard hasn't replied or given an ETA as of 21:10 UTC on Nov 8.

Why is WoW Forever lagging? From about 03:33 UTC on Nov 7, players report lag and zones with "more players than mobs", while others say their layer is fine. Blizzard hasn't said whether it changed layering. If your ping is much higher than usual, check Options > System > Languages and Social > Preferred Account Location and set it to your own region: players report NA characters routed to AU and the reverse.

Why is WoW Forever so empty? Players blame layering. Blizzard's Aggrend said at 06:35 UTC on Nov 5 that some areas don't feel "as populated as they should" and that Blizzard would be "tweaking some numbers tomorrow". By the evening some players report crowded zones and others still report empty ones. Blizzard hasn't confirmed the change is live.

What is on the WoW Forever Known Issues list? As of its 18:26 UTC edit on Nov 5 (the thread was edited again at 22:07 UTC): PvP vendors temporarily unavailable, the quest "Vorsha the Lasher" disabled over a crash, a Razorfen Kraul cauldron you can get stuck in, two gamepad bugs, bank tabs outside the frame and flashing textures at Stormwind Keep. Blizzard says the list isn't complete.

Why did I lose progress after a disconnect in WoW Forever? That's a rollback: you log back in where you were 15-20 minutes earlier, players report. A Game Master told one player lost skill or gold can't be compensated and advised logging out normally rather than with Alt-F4.

What is error WOW51900319 in WoW Forever? It's the "disconnected from the server" error players report in the European evening on Nov 5, often followed by "Logging in to game server". Disabling addons didn't help one player. Blizzard hasn't commented. Try logging in again after a few minutes.

Where did the WoW Forever boats go? Blizzard says boats and zeppelins can get "lost in the maelstrom". It spawned portals near most docks and inside zeppelin towers as a temporary fix. Blizzard says a proper fix was due "in the morning", after which the portals will be removed. It hasn't confirmed that fix is live.

Is WoW Forever server status up today? Mostly, as of 21:05 UTC on Nov 9: players are getting in and posting about gameplay, but EU players reported a few minutes of disconnects and stuck logins from 19:42 UTC, and some US players report disconnects and lag spikes, with no Blizzard post. From 07:46 UTC EU and US players reported mass disconnects and login failures for about 25 minutes, and one EU player says the status page showed no problem during it. At 09:37 UTC Blizzard staff confirmed in an EU forum reply that the login issues were resolved. Blizzard's Forever server status page is the official list, and Blizzard has no outage or maintenance post on its US or EU forums. For Europe, the Nov 7 maintenance showed up as player reports in an EU forum thread, and Blizzard posted nothing about it. Through Nov 8, the main problem players reported was wrong-region routing and high ping, not downtime.

My WoW Forever character is stuck on Oceanic servers. Can I move it? There's no way to pick a server, going by player reports as of 21:05 UTC on Nov 9. Two players say changing Preferred Account Location only moves characters created afterwards. The only fix players report for an existing character is leaving a guild with members or a preferred location in the other region, and players who aren't in a guild report no fix. Blizzard hasn't said whether it will move affected characters, and two players say tickets haven't helped.

How do I get Oceanic servers in WoW Forever? There's no server list. Players say to set Options > System > Languages and Social > Preferred Account Location to AU and relog. A player says the setting shows "Subject to 1 day cooldown", so give it a day. Players report it only affects characters created afterwards, and for some it reverts. Grouping with US players can also put you on US servers, and one player says leaving a guild set to a different region fixed their ping. NA players defaulted to AU report the same problem the other way round.

Why did my WoW Forever keybinds reset? Players say settings only save when you log out through the game menu. A disconnect or Alt-F4 loses unsaved changes, so log out once through the menu after setting up.

Why do I keep disconnecting in WoW Forever? Blizzard hasn't said. Players began reporting disconnects every minute or so at about 00:09 UTC, with a larger wave around 01:17 UTC, but other players say they have no problems, and no confirmed fix exists yet. If it's only your account, check the login errors guide.

How do I fix error BLZ51901016? In the forum thread, the most-confirmed fix is turning off a VPN or game network tool such as ExitLag and logging in again. One player fixed it by turning the VPN on and back off. This is player-reported, not a Blizzard fix.

Why doesn't my Skyborne character have a first quest? It's a bug many players report at launch, with no fix or Blizzard reply as of 21:10 UTC on Nov 5. Some players are levelling a different race until it's fixed.

Should I wait on the grey ruleset screen or relog? Relog. Players who waited say the screen never refreshed. Players who exited and queued again report selectable rulesets and character creation. You'll sit through another login queue.

Is the WoW Forever problem on my end? If everyone reports greyed rulesets, no. Reinstalling or Scan and Repair won't fix a server-side outage. If only your account fails, check that you picked the WoW account with an active subscription.

Why can't I see my friend in my WoW Forever group? You're probably on different layers. The invited player should click the blue "the world around you will change" message (lower right in Kaivax's screenshot; one poster says left side) and then Refresh Now, players report. Blizzard's Kaivax asked players on Nov 5 whether that button works, and Blizzard hasn't posted a fix.

My WoW Forever character is on the wrong ruleset. What happened? Players report characters made on Normal or PvP during name reservation now sitting on a different ruleset (PvP, Roleplay or Roleplay-PvP). Blizzard hasn't commented. Check the ruleset before you level, and open a ticket with Blizzard Support if you've already played.

What does "World Server Down" mean in WoW Forever? It means the game got you through login but couldn't put your character into the world. The message alone doesn't tell you the cause or when it will clear. On Nov 6 from 15:32 UTC players saw it right after the Americas restart, and one Roleplay player reported it on every character at 15:35 UTC. It's a server-side message, so wait and retry, and check the update log above.

Was the Nov 7 WoW Forever maintenance scheduled? Players quoting the Battle.net app say the notice calls it scheduled maintenance to address Auction House issues, and one says it was set to run until 8:00 a.m. PST (16:00 UTC). Others in the forum thread call it unscheduled because nothing was posted in advance on the forums. Blizzard hasn't posted about it on the forums or Blue Tracker as of 16:05 UTC.

Why is WoW Forever down every morning? It has happened on two mornings in a row for Americas players, both around 15:00 UTC (7:00 a.m. PST): a restart on Nov 6 and Auction House maintenance on Nov 7. Some players in the forum thread say these restarts have been short, around 30 to 40 minutes. Blizzard hasn't said whether there will be more, so check the Battle.net app before you log in.

Was the Nov 6 WoW Forever downtime scheduled? Players say the launcher showed a scheduled maintenance notice only after the servers went offline, and one player says they saw in-game [SERVER] messages around 15:03 UTC that Roleplay ruleset servers would shut down. Blizzard hasn't explained it on the forums as of 15:40 UTC.

When will Blizzard fix WoW Forever servers? The servers came back from the Nov 9 emergency maintenance at about 22:42 UTC, players report, without a Blizzard ETA. For the rollback losses there is no Blizzard answer as of 06:15 UTC on Nov 10. Blizzard gave no ETA for the Nov 9 evening disconnects and lag spikes either. The Nov 9 morning disconnects and login failures that started at 07:46 UTC ended around 08:10 UTC, players report, without an ETA; Blizzard staff confirmed the fix in an EU forum reply at 09:37 UTC. Through 21:10 UTC on Nov 8 servers were up. On Nov 7 they came back from Americas maintenance for Auction House disruptions that ended by about 15:37 UTC, players report. Blizzard hasn't confirmed on its forums whether the Auction House errors are fixed. Blizzard hasn't given an ETA for layer crowding, wrong-region routing, disconnects, rollbacks or the faction lock as of 21:05 UTC on Nov 9. Its only dated item is class tuning hotfixes planned for Nov 10. On Nov 8 it raised dungeon kill experience by 50% with a hotfix at about 19:05 UTC. We'll post the time and source here as soon as Blizzard gives one.

Where is the official WoW Forever server status page? On worldofwarcraft.blizzard.com, under Forever, Server Status. Players spotted it in the game version dropdown right at launch. @BlizzardCS on X usually posts first about outages. Players also say short maintenance notices show in the Battle.net launcher, and on Nov 7 one EU player could only see one with the launcher language set to English (UK).

Did WoW Forever launch on time? Yes. The login service opened at 23:00 UTC (3:00 p.m. PST) as scheduled. The problem was the ruleset step after the login queue.

Lost progress to a rollback? Get it back faster. timesaver.gg covers the WoW Forever grind:

Gold

WoW Forever Gold

4.9· from $8.75 (5 gold)

Buy now

You may also like