WoW Forever Bug Reports: What's Fixed, What's Known, and the 200 ms Ping Problem
Published 2026-11-09 by Jon Alden, Alden Tech
WoW: Forever launched November 4, and Blizzard has shipped hotfixes on November 5, 6 and 8. Here's what they fixed, what's on the official Known Issues list, and what players are still reporting, led by the wrong-region ping problem.
World of Warcraft: Forever launched on November 4, and the first days have been busy on the bug front. Blizzard has pushed hotfixes dated November 5 and 6, plus a November 8 change that raised kill experience in dungeons by 50%, and it keeps a Known Issues list for the game. Some launch problems are already fixed. One problem that's still open isn't on that list at all: players are being routed to the wrong region's servers and playing at around 200 ms. Here's where things stood on November 8, 2026.
The short version
Fixed: a long list of class, quest and dungeon bugs, including a Maraudon progression blocker and the "Vorsha the Lasher" quest that was lashing everyone in the zone (Blizzard's hotfix post). Officially tracked: PvP vendors are temporarily unavailable everywhere, plus a stuck spot in Razorfen Kraul and a few UI and gamepad bugs (Known Issues). Still open as of November 8, all player-reported: the wrong-region ping problem (Blizzard forums), overcrowded layers (Blizzard forums), Auction House "item was not found" errors, and disconnects that roll back progress (2nd Shift's launch guide).
What the November 5 and 6 hotfixes fixed
The full list is on Blizzard's hotfix post. The highlights:
Classes. Druid's Bloom now correctly heals its target, the Cooldown Manager shows crowd control durations correctly even when diminishing returns apply, and the Warlock's Voidwalker got about 40 more base health at all levels. A Soul Siphon bug that made Wrack increase its own damage is fixed, and Mages no longer learn a "Research" spell that was never supposed to exist.
Dungeons. Zaetar's Spirit now spawns after Princess Theradras in Maraudon, the instance portal into The Drowned City works, and creatures in Blackmaw Hold and The Drowned City no longer disengage when they shouldn't.
Blizzard's November 6 notes say the "Vorsha the Lasher" bug is resolved. The quest had been disabled on the Known Issues list over a crash bug, and the hotfix notes say it was "rudely lashing everyone in the zone." As of November 8, the Known Issues list, last updated November 5, still showed it as disabled. The escort in "The Sleeper Has Awakened" also falls asleep less often now, and players start with the Horn of Awakening to wake him up.
Races and world. Night Elf Druids no longer get Ravage and Pounce out of Shadowmeld, Orc Command no longer over-buffs some Warlock pet abilities, and respawn rates that were too fast in Dun Morogh and Dustwallow Marsh, and too slow for Yarrog Baneshadow in Durotar, are corrected. The Leatherworking Tanning Rack requirement dropped from 140 to 125 so it stops blocking patterns.
One more fix worth knowing: Invite-a-Friend players who were stuck at level 10 got a hotfix on November 5, according to 2nd Shift's launch guide, citing Master of Warcraft's report of a post by community manager Kaivax. If that's still you, they say logging out and back in picks the fix up.
Class tuning is next: on November 6, community manager Kaivax said Blizzard plans class hotfixes for Tuesday, November 10 (Blizzard forums).
What Blizzard says is still broken
Blizzard's Known Issues list, last updated November 5, is short and specific. The team says it isn't a comprehensive list, and that it'll be updated regularly.
PvP vendors are temporarily unavailable in all locations: Orgrimmar, Stormwind and Dalaran.
In Razorfen Kraul, there's a cauldron near Roogug that players can fall into and get stuck in.
On gamepad, an error may be generated when deleting more than one rare or epic item, and push-to-talk instructions may show up when joining a voice channel.
Bank tabs show up outside the bank window.
The entrance of Stormwind Keep may not look as intended, including unintended flashing textures. Stormwind guards also direct players to the wrong name for the transmogrification NPC.
The 200 ms problem
Since launch, North American players report the open world putting them on Oceanic (Australian) servers at about 200 ms, and Oceanic players report the reverse, in a Blizzard forum thread on the Preferred Account Location setting and others like it. On November 8, a player in Florida with the setting already on NA-East reported World latency of 189 to 204 ms with normal Home latency, even on a brand-new character with no guild (Blizzard forums).
The Preferred Account Location thread had 64 posts by the night of November 8 (US time), and no Blizzard staff had replied in it or in the other latency threads linked here. There's no ETA (Blizzard forums).
It's on Reddit too, in an r/classicwow post titled "I'm being connected to Oceanic servers on US".
What players say helps: set Options, then System, then Languages and Social, then Preferred Account Location to your own region. In the forum thread, players say that only fixes characters created afterwards, while existing characters stay stuck. Players in Blizzard's Language and Social Settings thread say changes there come with a 24-hour cooldown, so set it carefully. A forum volunteer suggested a guild's preferred location can pull you to the other region, but players who aren't in a guild are stuck too, and one player says grouping with friends from their own region lowered their ping while the group lasted (Blizzard forums). None of that is a Blizzard-confirmed fix.
Other issues players are reporting
Auction House. Since the evening of November 6, players have reported "The item was not found" when buying single items (2nd Shift, Blizzard forums). Players quoted the November 7 Americas maintenance notice as saying it would address intermittent Auction House disruptions, and some EU players said it improved afterwards, but Blizzard hasn't announced a fix (2nd Shift).
Rollbacks. Players report disconnects (error WOW51900319) that cost them 15 to 20 minutes of progress, including trained skills and profession skill-ups, while the gold or materials stayed spent. One player shared a Game Master reply saying these losses can't be compensated, and Blizzard hasn't listed rollbacks as a known issue (2nd Shift).
Layers. Starting late on November 6 (US time), players in a Blizzard forum thread reported a sudden change, with one saying Westfall and Redridge had "more players than mobs", while others said their layer was fine. An r/classicwow post is titled "I was unable to quest and the whole layer is lagging".
Maintenance rhythm. The Americas servers went down for about an hour at 7 AM PST on both November 6 and November 7, and returned early both days. EU servers had their own maintenance on November 7, with an update of about 322 MB (2nd Shift). Players saw "World server down" and error BLZ51934200 during those windows, so if either shows up around that hour, check the Battle.net app for a maintenance notice before troubleshooting your PC.
The hardware side
The open problems above, routing, layering, the Auction House and rollbacks, are on Blizzard's side, going by these reports. If the game runs fine on your machine, there's nothing to fix on your end for them. If you're speccing a PC for the raid openings on December 9 and want a second set of eyes on the build, that's a hardware conversation we're happy to have.
Sources, checked November 8, 2026: Blizzard forums: WoW: Forever Hotfixes, November 6, 2026; Known Issues, WoW Forever, updated November 5; Dungeon Enemy XP Increased, November 8; Class Tuning Incoming, November 10; Preferred Account Location routing thread; WoW Forever weird latency; NA-East account stuck on ~200 ms; Language and Social Settings; Thank you for tweaking the layering; Auction house bug (EU). Also 2nd Shift, WoW Forever Not Working? Queue and Ruleset Fixes; r/classicwow, "I'm being connected to Oceanic servers on US" and "I was unable to quest and the whole layer is lagging".