TUNEDb710rel/engines-tools3 min read

Blizzard Put 70,480 CPU Cores and 251 TB of RAM Behind WoW Forever

Blizzard confirmed 3,924 VMs, 251,136 GB of RAM and 70,480 CPU cores for WoW Forever on Nov. 5, 2026 — capacity figures that reveal nothing about load, cost or hardware.

WoW Forever Ran on 70,480 CPU Cores, 3,924 VMs [2026]
WoW Forever Ran on 70,480 CPU Cores, 3,924 VMs [2026]cookieone / pixabay

Patch notes

  • Official WoW account disclosed 70,480 CPU cores, 3,924 VMs and 251,136 GB of RAM on Nov. 5, 2026.

  • Per-VM figures of 64 GB and ~18 cores are derived arithmetic, not a disclosed configuration.

  • Physical versus virtual core count is undisclosed; the real silicon total could differ by up to 2x.

  • Peak concurrent players, processor models, hosting provider and cost are all unconfirmed.

  • Coverage by Tom's Hardware, TweakTown and Mezha.net all trace to the single X post.

Blizzard Entertainment disclosed on November 5, 2026, that the World of Warcraft: Forever launch ran on 3,924 virtual machines, 251,136 GB of memory and 70,480 CPU cores, according to a post from the official World of Warcraft account on X. Tom's Hardware, TweakTown and Mezha.net republished the figures within days. Three numbers carry the entire story, and each describes provisioned capacity, not measured load.

What is actually confirmed?

The post remains the only on-record source. It supplies no peak concurrent player count, no processor models, no physical server count, no hosting provider and no cost.

  • 3,924 virtual machines — confirmed
  • 251,136 GB of memory — confirmed
  • 70,480 CPU cores — confirmed
  • Roughly 251 TB headline figure — a rounding conversion, not Blizzard wording
  • "Smoothest launch" framing — outlet characterization, not an official superlative

Capacity tells you what Blizzard reserved. It does not tell you how many players showed up.

Why 70,480 cores needs a caveat

The coverage never specifies physical versus virtual cores. On most virtualized platforms a virtual core maps to a hardware thread, and two threads often share one physical core. If the figure counts allocated vCPUs (virtual CPUs, the units a hypervisor assigns to guests), the physical silicon behind the launch could be roughly half the headline. If it counts dedicated cores, the footprint is larger. No cited source settles the question. Oversubscription — a host promising more virtual cores than it has hardware threads — is a standard bet that a launch day, when every guest runs hot simultaneously, tests hardest.

The per-VM arithmetic is not a spec sheet

Divide the totals by the machine count and a tidy picture appears:

  • Memory per VM: 251,136 / 3,924 = exactly 64.0 GB
  • Cores per VM: 70,480 / 3,924 = about 17.96
  • Memory per core: about 3.56 GB
  • Decimal conversion: 251.136 TB; binary conversion: 245.25 TiB

The clean 64 GB result is suspicious precisely because averages hide variety. A real fleet mixes memory-heavy database hosts, small gateway nodes and world servers in between. The 3.56 GB per core ratio is neither extremely memory-heavy nor lean, which suggests a balanced build — but a few large database machines plus thousands of small stateless nodes would produce the same average. Declaring 3,924 identical 64 GB, 18-core instances would be a guess dressed as a fact.

Why memory dominates a persistent-world launch

State lives in RAM in an online world: player positions, inventories, auction listings, instance state. Disk latency would surface as lag. Launch conditions stress memory specifically — character creation spikes, login queues drain in bursts, caches start cold and fill fast. Teams typically provision above steady-state need, absorb the first weekend, then scale down. Whether Blizzard plans to shrink this fleet appears in no source.

Market context and the missing economics

The numbers land in a market where memory supply is the choke point for large system builders. Server DRAM competes with AI buildouts for the same fab capacity. Seventy thousand cores also draw real electricity, but no source names processor models or a wattage, so no efficiency estimate is possible. Hosting provider and infrastructure cost are both undisclosed, which leaves the launch's economics entirely opaque.

Repetition creates false confirmation here. Three outlets repeating one post is one source, not three. Capacity counts also flatter the publisher: a big number signals investment and never has to be defended against a utilization chart, whereas a peak player count would invite the reverse question of how much of the fleet sat idle.

What to watch next

The open questions — concurrency, core type, hardware models, vendor, cost — now sit with Blizzard. With server DRAM costs rising and a major competitor launch scheduled for November 19, expect the next infrastructure disclosure to be measured directly against this fleet.

via shattered.io (Source)

Share this article:

More from James Calloway

James Calloway

Show full bio

Senior reporter covering money, funding and market shifts around video game industry at Game Dev Wire.

223 articles