The Forever Beta Auction House Has Been Down for Days on Some Realms, and Blizzard Has Not Said a Word About It
Two weeks before the beta closes and three weeks before name reservation opens, the WoW: Forever beta has developed a problem that is more interesting than any single bug: a chunk of its infrastructure has been quietly broken for days, and Blizzard has not acknowledged it. Since around October 4, testers on at least one beta realm ID have been unable to use the Auction House at all — the client returns a permanent "The auction house is closed at the moment. Please try again later." — and the outage has spilled into delayed mail, delayed chat and latency complaints. The only official communication in that window is a short realm-restart notice that never mentions the Auction House.

Original editorial illustration by RealmList, generated for this article. This is artwork, not game footage or official promotional material.
What is actually broken
The core thread, Auction House Unavailable?, opened on October 4 and has grown steadily since. Three details in it matter more than the volume of complaints:
- It is realm-scoped, not global. Testers on the PvP ruleset report the AH, and in some reports mail and whispers, failing on specific realm IDs (4613 and 6413, both "Beta PvP 2"), while friends on neighboring realm IDs — one poster cites 4619 — use the Auction House normally. The working theory in the thread is that one realm has drifted out of sync with the shared services backend, and one poster's suggested fix is blunt: "Resync Realm ID 4613 with the Services Server (AH, Mail, Whispers)."
- It has outlived the restart. A companion thread titled "AH, mail delay, chat delay and latency Issues 10/4/2026" appeared the same day. By the time of the October 5 maintenance, posters in both threads were reporting 35+ hours and "2 days" without an Auction House.
- The response has been silence. Blizzard has posted extensively this week — the October 5 realm restart, warrior updates, the podcast thread — but nothing that names the Auction House. That is a deliberate contrast with smaller bugs like Gnomeregan breaking on October 4, which got a same-day "Who broke it?! Gnomes, of course. But earlier this afternoon, we fixed it."
The October 5 restart, and what it did not say
Kaivax's Brief Realm Maintenance - October 5 is three sentences long: realm restarts "in a few minutes, to apply some fixes that should improve the quality of the game service," countdown messages in-game, and the beta reopening a few minutes after it goes offline. No patch notes, no change list, no mention of the Auction House.
The replies are the telling part. Players immediately assumed the restart was aimed at the outage — "I HOPE that fixing the AH is considered 'Quality of the game service'" — and at least one asked directly whether it would fix "the broken AH on realm 6413 wow pvp2 that has been down for two days." Whether the restart actually resolved the issue on the affected realm IDs is not established in any official source; as of our check on October 6, the thread was still collecting fresh "still broken" reports without a confirming counter-report we could verify.
Why the pattern matters more than the bug
On its own, a broken Auction House in a beta that wipes on October 21 would be a footnote. What makes this one worth tracking is how it differs from every other beta incident so far:
| Incident | Date | Blizzard response |
|---|---|---|
| "Realm is full" queue bug | September 27 | Acknowledged and fixed same day |
| Login-blocking service issue | October 1 | Acknowledged within hours ("working to address") |
| Australian dialog bug | October 1–3 | Acknowledged, fixed, confirmed fixed |
| Gnomeregan outage | October 4 | Acknowledged and fixed same day, with a joke |
| Auction House / mail / chat outage | October 4 – present | No acknowledgement as of October 6 |
Every previous incident was a global failure that Blizzard owned publicly and quickly. This one is partial — most testers can still trade — which is precisely the kind of failure that slips past a "the game is up" health check. A beta exists to find exactly this class of problem before launch, and in that sense the outage is doing its job. The uncomfortable part is the communication gap: with 15 days of beta left and a November 4 launch that Blizzard has promised will be "the wildest ride" of demand, a services-backend desync that takes days to notice and longer to acknowledge is the specific failure mode that launch night cannot afford.
One practical note for testers in the meantime: a player in the thread points out that trade chat during an AH outage fills with gold-for-item deals, and they are simply not trading anything until it is resolved — sensible, given that the beta's RMT rules do not carve out an exception for "the AH was down." Our RMT crackdown coverage covers exactly how strictly Blizzard has drawn that line.
::note The outage description here is built entirely from player reports in Blizzard's own beta forum threads, cross-checked against Blue Tracker's archive of official posts; Blizzard has not published anything about this issue as of October 6, so the affected realm IDs, the start date and the services-backend theory are player-reported, not confirmed. Whether the October 5 restart fixed it could not be verified from official sources either way. Beta closes October 21 and launch is November 4, 2026. ::
Sources and further reading
External references used to verify or expand this article.