News

WoW Forever Beta Server Cap Rises Again After Queue Bug Fix

World of Warcraft: Forever cover art
The Completionist
The Completionist
Published
9/28/2026
Read Time
5 min

Blizzard has raised the World of Warcraft: Forever closed beta cap again after fixing a queue bug, but paid beta access keeps pressure on launch confidence.

World of Warcraft: Forever cover art

Image: IGDB

Blizzard opens the doors wider, but the pressure is still visible

Blizzard has raised the World of Warcraft: Forever closed beta population cap again, after executive producer Holly Longdale said on X that the team “had to increase the WoW: Forever Beta population cap again.” The immediate tension is clear: the beta is popular enough that Blizzard is expanding capacity for at least a second time, but the experience players are judging is still defined by queues, disconnects, and uncertainty about who gets in next.

MMOHuts reports that demand has continued to push the closed test’s server limits, with players running into queues and capacity restrictions as more invitees try to log in. Wowhead also reported Longdale’s post and tied it to Blizzard’s separate work on login queues. Polygon described the move as another adjustment to accommodate unusually high demand, noting that this had already happened once since the beta launched on September 17.

That makes the latest World of Warcraft Forever server cap increase a good sign and a warning sign at the same time. A capacity bump usually means more testers can play at once, giving Blizzard a broader read on quest flow, zone density, combat pacing, economy behavior, and the early progression curve. For an MMO, those systems are inseparable from server health. A class build that feels crisp in a stable zone can feel broken when latency spikes, mobs rubber-band, or a disconnect sends a player back to the login screen.

Blizzard has not announced another invite wave, a higher level cap, or an open beta date alongside the cap increase, according to MMOHuts. Bolverk Games also reports that there is still no word on those follow-up steps. For now, the confirmed change is narrower: Blizzard beta servers for Forever can hold more concurrent players than before, and one queue-related bug has been fixed. The broader access plan remains unannounced.

The queue bug fix matters because it changes the failure loop

The most practical improvement is not the cap increase by itself. It is Blizzard’s fix for a login issue tied to disconnects, because that problem turned ordinary beta congestion into a worse loop for affected players.

According to MMOHuts, some players were getting stuck in a queue after being kicked or dropped from the game. Blizzard later found a bug that was incorrectly filling the queue, and a fix has now been deployed. Wowhead quotes Blizzard’s forum response on the issue: “We looked into this, and found an issue that was causing the queue to fill, and we just fixed the issue. Thanks for testing with us!”

That distinction matters. A normal queue is frustrating, but it is at least understandable during a crowded MMO beta. A queue that refills incorrectly after disconnects is different. It punishes players twice: first by removing them from the session, then by making re-entry feel arbitrary. In a progression-heavy MMO, that can distort almost every kind of feedback. Testers who cannot stay connected long enough to finish a quest chain, compare talent choices, run a dungeon, or test profession loops are giving Blizzard data about access friction rather than about the game’s actual systems.

The fix should improve the experience for players who were being kicked and then forced back into an inflated line, but it does not mean WoW Forever queues are gone. The cap increase addresses how many people can be in at once. The bug fix addresses a faulty queue behavior. Those are related, but they are not the same problem. Players should expect capacity to remain a live issue while the closed beta is under load, especially because Blizzard is still using the test to find failure points before the full launch.

For anyone trying to play, the useful takeaway is simple: if you were mainly blocked by the disconnect-to-queue cycle, this fix is the specific change to watch. If you were blocked because the realm was genuinely full, the new cap may help, but Blizzard has not promised a queue-free beta.

Paid beta access raises the stakes for every outage

The paid access question is the part of this story that will follow Forever into launch. Eurogamer reports that the World of Warcraft: Forever beta requires players to pay £51.99, $59.99, or €59.99 for the Skyborne Epic pack. Timesaver.gg also reported beta access as being tied to paid bundles, naming the $59.99 Skyborne Epic Pack and the $79.99 Warcraft Forever Collection. Eurogamer adds that the full launch on November 4, 2026 is expected to use a monthly subscription as the cost of entry rather than the same one-time beta purchase.

That structure changes how players read instability. A free closed beta with long queues is often treated as a stress test first and a preview second. A paid beta still serves as a stress test, but the player expectation shifts. If someone paid for WoW Forever beta access, then a login queue that behaves incorrectly feels less like background noise and more like a failure of the product they bought into early.

PC Gamer’s coverage framed the cap increase through that tension, focusing on Blizzard’s decision to charge for access while needing to expand server size again. That is an interpretation, not a Blizzard statement, but it captures the obvious business pressure. Paid beta demand is a strong signal that the audience is deeply motivated. It also reduces the margin for messy communication, because every missing detail about invites, caps, and access windows lands in a more transactional context.

There is a fairer way to read it too. The beta is doing what a beta should do: exposing capacity limits, queue faults, and infrastructure assumptions before November. The frustration comes from the fact that this test is also a paid on-ramp into a highly anticipated version of World of Warcraft. Blizzard can benefit from that demand only if players believe the rough edges are being diagnosed and resolved, not simply endured.

Forever’s demand is rooted in Classic, but the audience is larger than a nostalgia lane

World of Warcraft: Forever is being discussed across outlets as Blizzard’s Classic-rooted project, with Polygon describing it in simple terms as a “Classic plus” version of the MMO. Polygon also places it alongside retail World of Warcraft, which receives the latest expansions, and Classic, which revisits the game’s older expansion path over time. MMOHuts similarly describes Forever as a Classic-rooted MMO ahead of its planned November 4, 2026 launch.

That context helps explain why capacity pressure arrived so quickly. Eurogamer reports that longtime World of Warcraft: Classic developer Josh Greenfield said shortly after the beta went live that it had produced “the craziest numbers I’ve seen in 17 years working at Blizzard and almost 8 years on classic.” Polygon also cited Greenfield’s comment as evidence that the response is extreme even by World of Warcraft standards.

Eurogamer adds useful historical perspective: 17 years earlier, World of Warcraft was in the Wrath of the Lich King era, about a year before Blizzard announced 12 million paying subscribers worldwide. Eurogamer notes that Blizzard and Microsoft have since been less open with subscriber figures, while the period around 16 to 18 years ago is widely believed to be the game’s peak.

For an RPG audience, the draw is easy to understand without turning it into hype. Classic’s appeal has always been partly mechanical: slower leveling, meaningful route choices, class identity that develops over time, and a world where travel, professions, group play, and danger have weight. A “Classic plus” approach suggests a version of Azeroth where that older progression language can be extended rather than simply replayed. The server pressure does not prove Forever will satisfy that audience, but it does show that many players are willing to fight queues for the chance to test Blizzard’s answer.

Capacity growth is a launch confidence signal, but not a launch guarantee

The latest WoW Forever beta server cap increase gives Blizzard more room to test, and that should improve the quality of its launch preparation. More concurrent players mean more stress on realm services, login systems, zone spawns, chat, grouping, dungeons, and the small interactions that only break when thousands of people are trying to do them at once. For an MMO, those are not peripheral details. They are the foundations under every build guide, leveling route, guild plan, and raid ambition.

Still, capacity growth is not the same as launch readiness. The confirmed facts are that Blizzard raised the population cap again, fixed a bug that incorrectly filled the queue, and has not announced a new invite wave, open beta date, or further access expansion. Bolverk Games reports that the beta runs through October 21 ahead of the November 4, 2026 full launch, which leaves Blizzard a narrow but meaningful window to turn beta findings into production changes.

The paid beta also complicates the confidence read. Strong demand despite paid access suggests a large audience may be waiting for launch, especially if Eurogamer is right that the full release will lower the immediate cost of entry to a monthly subscription model rather than the current beta pack. That could mean launch demand is even higher than the beta’s. It could also mean the beta is providing exactly the stress data Blizzard needs to avoid a rougher November.

The unanswered question is scale. Blizzard has shown it can raise the cap during the test, but the sources do not say how much the cap increased, how many players are currently in the beta, how many are waiting, or what concurrency target Blizzard expects for launch. Without those numbers, the safest reading is cautious optimism. The game is drawing serious interest, and Blizzard is actively fixing issues, but the public evidence does not yet prove that launch-day queues will be solved.

Guidance for players deciding whether to buy in or wait

If you already have WoW Forever beta access, the newest development is worth checking directly. The queue bug fix should make disconnect recovery less punishing, while the server cap increase should allow more players into the test at the same time. If your main problem was being dropped and then trapped in a strange queue cycle, Blizzard’s forum-posted fix is the relevant change. If your main problem was simple capacity, the improvement depends on how much Blizzard raised the cap, a figure the company has not publicly provided in the cited reports.

If you do not have access yet, the decision is different. Eurogamer reports that beta access requires the Skyborne Epic pack at £51.99, $59.99, or €59.99, while Timesaver.gg reported another paid collection option. Blizzard has not announced an open beta date, and MMOHuts reports that there is no word yet on another invite wave. That means paying for access is still a bet on participating in an unstable test, not a purchase of a polished early launch.

Players who mainly want to evaluate class feel, quest pacing, leveling routes, and the shape of Forever’s Classic-plus design may find value in entering now, provided they accept queues and periodic instability as part of the test. Players who want a stable character journey from the first login may be better served waiting for Blizzard to clarify access plans or for the November 4 launch.

For launch confidence, the best sign is not that the beta was crowded. Crowded betas can still lead to rough launches. The best sign is that Blizzard has identified a specific queue failure, fixed it, and increased capacity again while the test is still active. The concern is that paid access has made every queue and disconnect feel higher stakes. Forever’s first real progression check is not a dungeon boss or a talent breakpoint. It is whether Blizzard can turn this messy demand into a stable road to November.

Share: